MailBot by Tavel — email accounts creator, checker and unlocker

MailBot has been updated to version 17.98.

Starting around October 8th, Outlook disabled POP/IMAP activation for all new accounts at the administrator level of the Microsoft Exchange server that hosts Outlook email!

Important! This restriction expires two days after account creation.

You won’t be able to activate POP/IMAP in a newly created Outlook account, even if you create it manually in a browser, confirm your recovery email, and enable the “POP” and “IMAP” switches in the “Forwarding and IMAP” section of your account settings:

The switches will be drawn as enabled, but any HTTP requests that are sent will receive a 500 Internal Server Error response from the server with the following error JSON:

{
  "Body": {
    "ErrorCode": 500,
    "ExceptionName": "OwaInvalidOperationException",
    "FaultMessage": null,
    "IsTransient": false,
    "ResponseCode": "ErrorInternalServerError"
  }
}

You won’t see any error in the Outlook web interface. The IsTransient field, set to false, indicates that the error isn’t temporary, but caused by a configuration (policy restriction). In simple terms, this means Read more »

tavel \\ 5SIM, Anosim, CAPTCHA, Captcha88, CaptchaRun, CheapSMS, EzCaptcha, GMX.com, GMX.de, Graph API, Human CAPTCHA, IMAP, MailBot, Meta.ua, Mg-Captcha, OAuth2, Onet.pl, Outlook, POP3, RemProxy, SMTP, Thordata, TIGER SMS, Turnstile, UKR.NET, Web.de, Yahoo, creator, checker, Yandex

MailBot has been updated to version 17.75.

In addition to exporting text account data and its cookies to the user’s server, export of created account aliases has also been implemented. The list of aliases is passed in the aliases parameter and is a Base64-encoded list of strings separated by a line feed character:

so08ua4s4@gmx.com:tazpRk62v25:v6fxsd0v1@gmx.com
so08ua4s4@gmx.com:tazpRk62v25:ful6df4mc@gmx.com
so08ua4s4@gmx.com:tazpRk62v25:ptl69c0z@gmx.com

An updated example of a server script that accepts a POST request from MailBot can be downloaded from this link. Also, this link, called “Server Example”, has been added to the “Export” tab in the program.

Outlook

Implemented:

• invisible Human CAPTCHA solution to unlock accounts blocked by SMS verification requirement
• handling “Sign in faster with your face, fingerprint, or PIN” form:

  

• ClientId for OAuth refresh token is now parsed from Read more »

tavel \\ Captcha88, GMX Europe, GMX.de, Human CAPTCHA, IMAP, Meta.ua, Mg-Captcha, OAuth2, Outlook, PeyVodka, RazorCap, Runbox, Web.de, creator, unlocker, aliases, recovery email, резервный код, checker, экспорт

MailBot has been updated to version 17.21.

It is a well-known fact that for access via IMAP/POP3/SMTP to Yahoo/AOL accounts, you have long been required to create an application password, and for new accounts this function is disabled by Yahoo until 14 days have passed since the account was created. Even if you try to create such a password manually in the browser on an account less than 14 days old, you will get the error “Sorry, this feature is not available right now!”.

Of course, you can create an application password with the MailBot checker after 14 days, but this creates great inconvenience. But a solution has been found, and it is OAuth. Using the OAuth refresh token, which can now be generated by the Yahoo creator and checker in MailBot, you can access Yahoo accounts via IMAP/POP3/SMTP immediately after creating an account!

Everything works the same as for Outlook, just the “Generate OAuth2 refresh token” checkbox on the “Email features” tab is now available for Yahoo as well.

OAuth2 refresh token for Yahoo account looks like this:

AEawIGjLwMLD4B80rfvpr9Yhk2Si~001~YApSpi7faQ2Gh1POiyxbQc4-

All tokens are created for Mozilla ThunderBird client data, namely:

ClientId: dj0yJmk9NUtCTWFMNVpTaVJmJmQ9WVdrOVJ6UjVTa2xJTXpRbWNHbzlNQS0tJnM9Y29uc3VtZXJzZWNyZXQmeD0yYw--

ClientSecret: f2de6a30ae123cdbc258c15e0812799010d589cc

By the way, to prevent the Yahoo creator from throwing up errors about the impossibility of creating an application password after creating an account, you can run MailBot with the following command line options:

MailBot.exe /apppass:off /POP3:off /IMAP:off /SMTP:off

Yahoo/AOL

Fixed:

• SMS deliverability to phone numbers
• thread loop on error Read more »

tavel \\ AOL, CaptchaFox, captchasolvingapi, CLI, funcaptcha, GMX Europe, GMX.com, IMAP, KoCaptcha, Mail.com, MailBot, Mg-Captcha, OAuth2, POP3, ruCaptcha, Runbox, SCTG, SMS-Activate, SMTP, Yahoo, checker, экспорт

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