May 12

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-

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 \\ , , , , , , , , , , , , , , , , , , , , ,

Mar 31

MailBot has been updated to version 17.2.

The “GMX.fr” provider in MailBot has been renamed to “GMX Europe”.

It also now supports two new domains: gmx.co.uk and gmx.es.

The price of the provider has increased from $67 to $97.

Outlook

Handling of the error HTTP/1.1 503 Service Unavailable with the text Our services aren't available right now is implemented in the account creator.

Fixed:

  • unlocking accounts with a /recover lock type, where password change is required after completing SMS verification
  • fingerprint generation in checker/unlocker
  • country code transfer for United Kingdom in unlocker

Yahoo/AOL.com

Creators now successfully differentiate between invalid CAPTCHA code (ECAPTCHAWrongCode) and already used phone number (EEmailAPIPhoneUsedNumber) errors, rather than always generating EEmailAPIPhoneUsedNumber. This allows to diagnose problems with the reCAPTCHA Enterprise solution used by Yahoo/AOL.

If you are constantly getting ECAPTCHAWrongCode errors when creating Yahoo/AOL accounts, you need to Read more »

tavel \\ , , , , , , , , , , , , , , , , , , , , ,

Nov 03

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:

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 \\ , , , , , , , , , , , , , , , , , ,

Oct 08

MailBot has been updated to version 16.57.

OAuth2 logo

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:

New OAuth2 refresh token generation setting

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 \\ , , , , , , , , , , , , ,

Sep 30

MailBot has been updated to version 16.54.

OAuth2 logo

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

New authentication method setting for IMAP in MailBot

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 \\ , , , , , , , , , , , , , ,