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 »
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 »