MailBot by Tavel — email accounts creator, checker and unlocker

MailBot has been updated to version 18.35.

Web.de/GMX.de

Implemented:

• optional application password generation for accessing an account via IMAP/POP/SMTP. The app password at Web.de/GMX.de looks like this: XM4ZE2SNJDH7GZZEHXJY
• recovery email verification for Web.de accounts

Fixed:

• recovery email verification for GMX.de accounts
• frequent failures when changing account passwords (checker function “Change account passwords”)
• unlocking accounts by changing the password (for accounts that are locked by a password change request)
• frequent threads freezing for a long time after successfully solving a CAPTCHA when activating mail protocols
• persistent EAccountExists error for any usernames in the Web.de creator
• an Invalid CORS request error in checkers when checking some locked accounts
• ECheckerError in checkers
• detection of invalid accounts in checkers
• Web.de has removed Austrian phone numbers from its list of permitted numbers:

  

Mail.com/GMX.com

Implemented:

• a password change function for Mail.com accounts
• handling of HTTP errors 502 Bad Gateway and 503 Service Unavailable when requesting a CAPTCHA configuration

Fixed:

• detection of valid accounts by checkers
• {"error":{"status-code":"403","message":"blocked","request-id":"..."}} error in the GMX.com and GMX Europe creators
• the percentage of GMX.com accounts that were created and immediately blocked has been significantly reduced
• ECheckerError in checkers

Important! GMX.com/GMX Europe accounts are currently created valid, but are only saved as “partially created”. This issue is being fixed.

Outlook

Implemented:

• handling (skipping) of the new form “Setting up your passkey…”:

  

• two radio buttons have been added to the “Email features” tab: “IMAP/POP/SMTP” and “MS Graph API”, which allow you to select the scope when generating an OAuth refresh token:

  

• support for the “Are you trying to sign in to Thunderbird?” form when generating an OAuth refresh token:

  

Fixed:

• solving invisible Human CAPTCHA via EzCaptcha API
• a rare invalid_grant error when generating an OAuth refresh token

Yahoo

Fixed detection of invalid accounts that return errors like “Sorry, we don’t recognize this account.”

WP.pl/O2.pl

Implemented:

• handling of the error {"data":{"status":"SMS_VERIFY_REQUIRED","challengeId":"..."}} after signup request
• creators now change the account’s recovery email to the next one from the list when receiving the SMS_VERIFY_REQUIRED error

Onet.pl

The detection of valid accounts, as well as profile filling and IMAP/POP/SMTP activation (may require re-launching the checker) are fixed in the checker.

Inbox.lv

Implemented:

• the detection as locked of accounts with such a form:

  

• error handling for incorrectly solved CAPTCHA when logging into an account
• the checker can now complete forms for setting up a profile name, avatar, birthday/gender

Fixed:

• persistent ETokenNotFound error in the creator
• EAccountCreate error in the creator after verifying the recovery email
• an EAccountCreate error that frequently occurred when creating accounts without recovery email verification
• the Unable to check account ... error in the account checker for accounts blocked by the requirement to set a profile name

UKR.net

Implemented handling of invalid_recaptcha and limit_reached errors.

Fixed:

• the checker has been switched to reCAPTCHA v2
• infinite recaptcha_required in checker

Also implemented in MailBot 18.35:

• the log window has been moved to the right side of the main application window
• added buttons for copying log text to the clipboard and saving it to a file
• a counter of accounts created locked has been added to the “Statistics” tab
• a new setting “Pass the proxy for Turnstile” is now available when editing a CAPTCHA solving service account
• support for the Hero-SMS service, replacing the discontinued SMS-Activate
• the Web.de service code has been added to the Anosim API
• support for the maxPrice parameter in the Anosim API
• handling of the errors Not enough credit-amount for order and There aren't that many SIM cards available anymore in the Anosim API
• support for the smscenter.pro domain in the VAK-SMS API
• support for reCAPTCHA and FunCAPTCHA in the CaptchaRun API
• support for the sid and cts fields for Human CAPTCHA in the Captcha88 API
• passing of the string “1:1:1:1” as a proxy address if proxy passing is disabled in the Captcha88 API
• {"status":"failed","result":{"token":"","duration":4.195,"reason":"CAPTCHA FAILED","data":""}} error handling in the Captcha88 API
• parsing and use of Human CAPTCHA cookies if the Mg-Captcha API returned them immediately upon creating the task
• handling of the WRONG_RESULT error for the MultiBot CAPTCHA solving service
• parsing and use of the user agent value returned by the service along with the CAPTCHA token in the CapSolver API
• handling of the Cloudflare_PROXY_ACCESS_ERROR error in the EzCaptcha API
• the Thordata API tab now supports both the old format (API token + API key) and the new one — with just an API token (the “API key” field can be left blank). In the second case, the API token must be in this format: 2c7811b09684a9bf605c4c9061851808
• added Google Chrome 141-145 fingerprints

Fixed:

• an EAccessViolation error when launching the creator/checker with the Hero-SMS service selected
• service codes for SMSBower in SMS-Activate API

автор tavel \\ теги: Anosim, CapSolver, Captcha88, CaptchaRun, EzCaptcha, GMX Europe, GMX.com, GMX.de, Hero-SMS, Human CAPTCHA, IMAP, inbox.lv, Mail.com, MailBot, Mg-Captcha, MultiBot, O2.pl, OAuth2, Onet.pl, Outlook, POP3, RazorCap, SMSBower, smscenter, SMSPool, SMTP, Thordata, UKR.NET, VAK-SMS, Web.de, WP.pl, Yahoo, creator, unlocker, app password, пассчейнджер, recovery email, stats, checker