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
MailBot has been updated to version 15.68.
Outlook/Hotmail
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 »
tavel
\\ 2FA, AOL, funcaptcha, GMX.com, GMX.de, I.UA, IMAP, LSA, Mail.com, MailBot, Meta.ua, Outlook, TOTP, Web.de, Yahoo, avatar, unlocker, recovery email, checker, Yandex
MailBot has been updated to version 14.26.
Important! For successful creation of WP.pl/O2.pl accounts, it is necessary to use dictionaries of exactly Polish names and surnames. Such dictionaries are supplied with MailBot, they can be found in the “Dic” folder, filenames start with “PL_…”.
Important! WP.pl/O2.pl allow account creation only from European IP addresses.
WP.pl and O2.pl now activate paid account features for free for 7 days after account creation. For example, this makes it possible to enable forwarding:
You can enable forwarding activation on created/checked accounts in the “Enable forwarding” panel on the “Accounts” tab in MailBot.
WP.pl/O2.pl creators and checkers now handle notification about Read more »
tavel
\\ funcaptcha, Hotmail, IMAP, MailBot, O2.pl, Outlook, POP3, PVA, SMTP, WP.pl, forwarding, checker
MailBot has been updated to version 13.93.
The interface for working with the phone verification providers APIs has been redesigned similarly to the interface for working with the CAPTCHA solving services API. Now on the sub-tab “SMS”→”API” you can add all your accounts on phone verification providers to the list and switch between them with one click (the picture shows an example of a completed list):
Accounts can be added, edited and deleted, the corresponding buttons are located below the list on the left. For each account on the phone verification provider you can configure each setting Read more »
tavel
\\ funcaptcha, GMX.de, kopeechka, MailBot, Meta.ua, Onet.pl, Outlook, PVA, SIMSMS, sms-acktiwator, SMS-Activate, SMSPVA, Web.de, creator, unlocker, antispam, aliases, checker, Yandex
MailBot has been updated to version 13.70.
Update from January 20, 2022: AnyCaptcha has restored Arkose Labs FunCAPTCHA solution for Outlook!
Outlook creator in MailBot now requires mandatory SMS verification of phone number to create accounts.
Unfortunately, the latest Outlook update introduced a comparison of fingerprints of the browser that solves FunCAPTCHA and the browser that creates Outlook account. If the fingerprints do not match, the solved FunCAPTCHA token is not accepted. Consequently, creating Outlook accounts only by solving the FunCAPTCHA, without SMS verification, is no longer possible via CAPTCHA solving services, which solve the FunCAPTCHA by the transfer of a public key. Unfortunately, all CAPTCHA solving services that are currently on the market solve FunCAPTCHA exactly by the transfer of a public key. That is why lately all clients had been receiving wrong CAPTCHA code errors when trying to create Outlook accounts without SMS verification.
Important! The problem described above has nothing to do with MailBot. This is a fundamental limitation of the current implementation of the CAPTCHA solving services: their workers / scripts have their own browser, which does not connected in any way with the browser used by Outlook account creation programs. Transferring current proxy, user agent, cookies, etc. to the CAPTCHA service API is implemented in MailBot, but cannot help in any way in this matter, since the browser fingerprint that Arkose Labs FunCAPTCHA collects includes hundreds of parameters, not just these 3.
Important! Now only @outlook.com domain is available for registration, the registration on other domains was possible only by solving FunCAPTCHA.
Important! For Russian phone numbers Outlook always asks for a FunCAPTCHA solution! Therefore, you will not be able to use Russian phone numbers to create Outlook accounts, please use any other countries.
Also implemented in MailBot 13.70: Read more »
tavel
\\ funcaptcha, MailBot, Outlook, PVA
|