MailBot by Tavel — email accounts creator, checker and unlocker

MailBot has been updated to version 16.72.

The long-awaited functionality of selecting a specific phone number operator for SMS activation services has been implemented:

So far, operator selection has only been implemented for SMS activation services that provide a list of operators via API:

• SMS-Activate
• VAK-SMS
• 5SIM

When you click on a country in the “Phone numbers country” list, a list of available operators will be loaded for it via the selected API. If you check the “Any” box, Read more »

tavel \\ 5SIM, api-sms-pro, Mail.ru, MailBot, MNO, onlinesim, Outlook, PVA, SMS-Activate, SMSPool, VAK-SMS

MailBot has been updated to version 16.67.

Due to numerous customer complaints about manual and slow updating of the list of available countries of phone numbers for various phone verification providers, dynamic loading of this list via API has been implemented in MailBot.
To date, this method is available and implemented for the following APIs:

• SMS-Activate
• VAK-SMS
• 5SIM
• SMSAcktiwator (SMSI.VIP)

Outlook

Fixed:

• Unknown signup error with code 100 error in creator
• Unable to verify account error in checker/unlocker, which occurred due to unsuccessful processing of “We’re updating our terms” form
• error with code 6002 when verifying recovery email in unlocker

Yahoo/AOL.com

Fixed Unable to check account error in the checker.

GMX.com/Mail.com

An optional Read more »

tavel \\ 5SIM, AOL, API, CapBypass, GMX.com, Hotmail, inbox.lv, Mail.com, Mail.ru, MailBot, Outlook, Runbox, sms-acktiwator, SMS-Activate, VAK-SMS, Yahoo, unlocker, checker, Yandex

MailBot has been updated to version 16.57.

This article is a continuation of the previous one, about adapting MailBot to mandatory authentication via OAuth2 for Outlook mail servers.

A new setting “Generate OAuth2 refresh token” has been added to the “Email Features” tab:

This setting currently only works for the Outlook/Hotmail module. If the checkbox is checked, the Outlook creator will generate OAuth2 tokens for accessing mail protocols after successfully creating an account, and the checker will generate them after successfully logging into an existing account.

Attention! All OAuth2 tokens are generated for ClientId 9e5f94bc-e8a4-4e73-b8be-63364c29d753, which is the ClientId of the Mozilla ThunderBird IMAP client in Outlook.

After successfully receiving OAuth2 tokens, MailBot will append a refresh token string to the end of the account string, and will also additionally save all parameters received from the OAuth2 server to a JSON file in the “oauth2” folder inside the “Accounts” folder. The file name will match the account email address. Example of the contents Read more »

tavel \\ AOL, GMX.com, Hotmail, IMAP, Mail.ru, MailBot, OAuth2, OTPTextnow, Outlook, POP3, PVA, VAK-SMS, creator, recovery email

MailBot has been updated to version 16.54.

Since September 20, 2024, Microsoft has almost completely disabled authentication via regular password (PLAIN method) on its IMAP, SMTP and POP3 servers, leaving only the OAuth2 option (XOAUTH2 method). As of today, only a few servers remain unpatched, and it is almost impossible to authenticate with a regular password on Outlook mail servers.

If you try to authenticate with a regular password, for example, the Outlook SMTP server will respond with this error:

535 5.7.139 Authentication unsuccessful, basic authentication is disabled.

and the Outlook IMAP server will respond with this one:

001 NO AUTHENTICATE failed.

To some extent, this also affected MailBot, since the verification of recovery emails in the program is carried out via the IMAP protocol.

In connection with this, a new setting “Authentication” appeared in the recovery email source settings window in MailBot, which is a list with two values:

• Plain password
• OAuth2

When connecting Outlook accounts as recovery emails, you now need to select only OAuth2, and the format of the recovery emails in the file should look like Read more »

tavel \\ AOL, IMAP, Mail.ru, MailBot, O2.pl, OAuth2, Outlook, POP3, SMTP, Turnstile, VAK-SMS, WP.pl, Yahoo, recovery email, Yandex

Update from 07/31/2024: Passing a proxy to solve FunCAPTCHA on Outlook is required again, if Telegram bot answers {"status":"UPDATING"}!

Update from 06/19/2024: Passing a proxy to solve FunCAPTCHA on Outlook is no longer required!

Many users have already noticed that, starting from Thursday, May 23, the percentage of incorrectly solved FunCAPTCHAs for Outlook began to grow rapidly across all CAPTCHA solving services, gradually increasing from ~40% to 100%. Over the weekend, the administrations of three of the four up-to-date FunCAPTCHA solution services for Outlook came to the conclusion that it is no longer possible to obtain valid solutions without passing the proxy, which is used to register an account, to the API of the CAPTCHA solution service. It is now necessary to transfer a proxy so that the IP address from which the FunCAPTCHA was solved on the service matches the IP address from which the registration request originates. This is not a new requirement, it has already been encountered before and MailBot has had a setting for this for a long time. It is located in the CAPTCHA service account settings on the “CAPTCHA” tab and is called “Pass the proxy for Arkose Labs (FunCAPTCHA)”:

However, do not rush to turn it on and complain that nothing works. Each provider (both proxy and CAPTCHA solver) now has many important nuances, without understanding which, unfortunately, it will not be possible to continue working.

First, there are a couple of side effects of Read more »

tavel \\ CapSolver, EzCaptcha, funcaptcha, Hard Captcha, MailBot, Outlook, RockCaptcha, Underdog, creator, proxy