MailBot by Tavel — email accounts creator, checker and unlocker

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 enabling this setting that affect every proxy and every CAPTCHA solver:

1. CAPTCHA solving service connects to the proxy provided by your account creator, requesting FunCAPTCHA scripts and images through your proxy, as well as performing all HTTP requests related to the FunCAPTCHA solution through your proxy. This means that the Internet traffic consumption through your proxies will increase significantly, and also that the proxies must allow connections to Arkose Labs (owner of FunCAPTCHA) domains. In addition, your proxies must allow connections to them from the CAPTCHA solver’s server, which will necessarily have a different IP address compared to the computer on which MailBot is running.
2. On many proxy providers proxies are available only via whitelisting a specific IP address in the control panel, and it is possible that CAPTCHA solver does not support access via whitelisted IP address, or your proxy provider does not allow you to whitelist more than one IP address for proxy access. In the described cases, the situation cannot be corrected in any way except by changing the provider!

Now I will describe the nuances as of May 27, 2024 and for each service for solving CAPTCHA separately, starting with the most popular:

EzCaptcha

Update from 06/04/2024: They have implemented proxy transfer in their API for the FunCAPTCHA solving, SOCKS/HTTPS proxies are supported, as well as IP address whitelisting (but only for Chinese proxies, in this case, you need to whitelist IP address 202.105.112.236). On the same day, MailBot 16.15 was released, which supports this change in their API.

Update from 05/28/2024: They promise to solve the problem within 2-3 days.

No changes have been made yet, except for this statement:

The solver does not yet support proxy transfer, so FunCAPTCHA for Outlook cannot be solved by it right now.

All requests sent without passing a proxy will time out (ECAPTCHATimeout error).

RockCaptcha

On May 24, a mandatory requirement was introduced to transfer a proxy to solve FunCAPTCHA. On the same day, MailBot 16.13 was released, which supports this change in their API.

However, there are two strict restrictions on the API side:

• only HTTPS proxies are supported, SOCKS is not supported yet
• proxies can be accessed only by username/password, IP address whitelisting is not supported yet

All solutions received without passing a proxy will be invalid (Outlook will reject them with an ECAPTCHAWrongCode error).

CapSolver

They have long supported the transfer of proxy when solving CAPTCHAs.

There are two important nuances:

• if you have proxies accessible via IP address whitelisting, you must whitelist IP addresses 47.253.53.46 and 47.253.81.245 so that CapSolver servers can access your proxies (link to documentation section)
• fixed in MailBot 16.15 all types of proxies are officially supported, however, one of the clients had unsolvable problems with HTTPS proxies

All requests sent without passing a proxy will end in error ECAPTCHA: ERROR_INVALID_TASK_DATA: invalid task data: this PublicKey only supports FunCaptchaTask, not ProxyLess.

Underdog CAPTCHA

Today, Monday, the service published news that proxy transfer has been recognized as a necessity and that appropriate changes to the API are being developed.

All solutions received without passing a proxy will be invalid (Outlook will reject them with an ECAPTCHAWrongCode error).

HardCaptcha

Update from 06/01/2024: Yesterday, May 31, they posted news about the need to transfer a proxy for the FunCAPTCHA solution on Outlook, but they are not yet ready to update their API for this.

This post will be updated, supplemented and translated into other languages ​​as the situation develops.

автор tavel \\ теги: CapSolver, EzCaptcha, funcaptcha, Hard Captcha, MailBot, Outlook, RockCaptcha, Underdog, creator, proxy