Added API support for several CAPTCHA solving services that can automatically solve FunCAPTCHA for Outlook:
RockCaptcha, price for 1000 solutions of FunCAPTCHA for Outlook: $1.0
Hard Captcha, price for 1000 solutions of FunCAPTCHA for Outlook: $1.0
captcha.onl1n3, price for 1000 solutions of FunCAPTCHA for Outlook: $1.0
Because accurate time is critical for features such as TOTP and IMAP email searching, MailBot now automatically synchronizes your local computer’s time with time.google.com during startup.
Updated context menu for the list of accounts on the “Creator” tab:
New items added:
“Phone number only”
“App password only”
“TOTP secret key only”
“Get TOTP code”
Outlook/Hotmail
Fixed:
persistent ESignupError error immediately after Read more »
Ake.net — reliable and affordable proxies that will help you avoid restrictions and blocks on the network. The service offers all types of proxies: mobile, residential, and corporate.
The price is the same for all types of proxies: $3 per GB. You only pay for the traffic used, with no restrictions on time and the number of created ports. This makes Ake.net the ideal proxy provider for working with MailBot for two reasons.
Firstly, the connection through Ake cannot be traced, as all proxies here are reverse ones. Additionally, Ake provides a wide range of port settings — over 200 countries and 10+ million trusted IP addresses. There is also free targeting on ASN numbers of regional operators, allowing you to safely use mobile proxies.
Secondly, payment only for traffic helps save on creating mailboxes using MailBot. If you enable the “Compress traffic” setting, 1 GB of traffic will be enough to create ~4200 Outlook/Hotmail email accounts. This means you won’t overpay for extra traffic.
Currently, Ake.net offers a free 3 GB test using the promocode TAVEL. An excellent opportunity to practically experience the benefits of Ake.
Activation of two-factor authentication (2FA) in accounts via TOTP has been implemented. After successful activation, a secret key will be stored along with the account data, which has the following form: 3hmkerjjj6cw7kfi3
It is absolutely not necessary to use the Microsoft/Google Authenticator app to get the code from this key, on the “Email features” tab in MailBot there is a completely similar code generator, which opens by clicking on the “TOTP…” button.
Without a secret key, it will still be possible to get into the account using, for example, a recovery email, in this case you need to click on the “Sign in another way” link on this form:
Despite this, it is strongly not recommended to uncheck the “OTP secret key” box on the “Export” tab, since TOTP is the fastest and most stable confirmation method.
The checker can now also bypass 2FA via TOTP if the account string has a secret key. If there is no secret key, but there is a recovery email with a password, the checker will still be able to authorize in the account by receiving an email with a confirmation code.
Attention! So far 2FA activation is implemented only after adding a recovery email to the account. Activation after phone number verification is planned in the next versions of MailBot.
Attention! After enabling 2FA in your account, it becomes possible to authorize via POP3/IMAP/SMTP only with app password, so this password is created automatically and saved along with the account data.
The application password looks like this: lbtmyfqaycrgsvxn
It is easy to confuse it with Read more »
Microsoft’s landing page is skipped now in creator and checker when receiving sign up and sign in forms.
This gave the following bonuses:
The speed of work has increased, because Microsoft server that served the landing page couldn’t handle the load on September 13 and often went down, which led to EIdReadTimeout errors.
Internet traffic consumption has decreased, since the landing page is almost 150 KB in size.
Eliminated EFormURLNotFound errors at the stage of receiving sign up and sign in forms.
Fixed the problem of receiving two identical codes in a row from verification emails when adding a recovery email to an account if Rambler mailboxes are used as recovery emails.
Inbox.lv
Verification of the recovery email when creating an account has been implemented:
Attention! If the “Verify recovery email” checkbox on the “Recovery email” tab in MailBot is not checked, then accounts Read more »
Instead of a patchwork of changes for all email providers, which is hard to read, let’s try to break down changelogs by email provider. Please send your opinions in which form you prefer to read the changelog.
Outlook/Hotmail
Implemented adding and verifying a recovery email in the creator, in the signup mode without phone verification. Previously, this was implemented only in the unlocker.
Verifying a phone number to enable SMTP is not necessary now, verifying the recovery email gives the same trust to the account as verifying the phone.
During the process two letters with confirmation codes are received on the recovery email, this is normal.
Creation of aliases is implemented in Outlook creator, checker and unlocker.
Attention! To create aliases in your Outlook account, it must has verified recovery email!
Attention! Outlook now allows you to create only 2 account aliases and only on the outlook.com domain!
The checker now is able to create Outlook mailboxes for Microsoft accounts created via phone number:
This allows you to finish creation of mailboxes for accounts in format +380983524927:V5p9axnJc, which were previously saved in “partially created” files.
When creating accounts via phone number, creator now updates Read more »