Dec 20

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.

Arkose Labs wins

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

Dec 15

MailBot has been updated to version 13.65.

On the recommendation of 2Captcha support, MailBot implemented the 2Captcha WebSocket API to combat the low lifespan of Arkose Labs (FunCAPTCHA) tokens.

It can be selected in the “CAPTCHA service API” list in the window for adding a new account on the CAPTCHA solving service:

2Captcha WebSocket API in CAPTCHA services API list

This API supports all types of CAPTCHAs that MailBot needs to solve.

The peculiarity of the WebSocket API is that you do not need to constantly poll the API in anticipation of the result of the CAPTCHA solution, the server itself sends a notification about this. Therefore, in the settings of the CAPTCHA service account in the “API timeouts” panel, the first two timeouts will be disabled, for the WebSocket API they do not make sense, you can only configure the total waiting time for the result of the CAPTCHA solution.

Important! So far, you can work with the 2Captcha WebSocket API in a maximum of 2 threads. In the future, this restriction will be lifted.

CAPTCHA statistics have been radically redesigned, now statistics of all submissions, solutions and errors are maintained separately for each type of CAPTCHA.

On the “Statistics” tab, instead of a simple “CAPTCHA” panel, there is now Read more »

tavel \\ , , , , , , ,

Jul 26

MailBot has been updated to version 13.17.

Implemented the creation of aliases for Mail.ru accounts.

Important! The creation of aliases is supported only for accounts with verified phone number.

Aliases can be created both by the creator (after a successful account creation) and by the checker (for already existing accounts).
To create one alias, you need to solve one regular Mail.ru CAPTCHA image.
So far, aliases are created only on the same domain as the main account.
Created aliases are saved in a separate file with a name like “Mail.ru 2021.05.26 – 12.09.53 aliases.txt” in the “Accounts” folder.

Important! Updated the list of working domains and the API domain for the Interimail API. Unfortunately, access to the domains tavel.ga, tavel.cf, interimail.ga, interimail.cf, interimmail.ga, and interimmail.cf has been lost. Similar domains have been added instead.

Also implemented in MailBot 13.17:

  • background update of balances of all CAPTCHA service accounts when opening the “CAPTCHA” tab:

    Account balances on CAPTCHA services are now loaded automatically in background

  • handling “not enough rating” error in 5SIM.net API (it was displayed in log as EAccessViolation error when trying to get a phone number)
  • added code for Read more »

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

May 19

Runbox logo

MailBot account creator updated to version 12.98.

Account creator and checker of Norwegian email provider Runbox was implemented.

New service is located on the “EU” sub-tab of the “Provider” tab.

There are 29 domains at your service:

  • @runbox.com
  • @mailhost.work
  • @mailhouse.biz
  • @messagebox.email
  • @offshore.rocks
  • @rbox.co
  • @rbox.me
  • @rbx.email
  • @rbx.life
  • @rbx.run
  • @rnbx.uk
  • @runbox.at
  • @runbox.biz
  • @runbox.bz
  • @runbox.ch
  • @runbox.co
  • @runbox.co.in
  • @runbox.dk
  • @runbox.email
  • @runbox.eu
  • @runbox.is
  • @runbox.it
  • @runbox.ky
  • @runbox.li
  • @runbox.me
  • @runbox.nl
  • @runbox.no
  • @runbox.us
  • @xobnur.uk

as well as active access via IMAP, POP3 and SMTP.

It is enough to solve one hCaptcha and specify an alternative email to create Runbox account. You can use “Use randomly generated temporary mailbox” setting on the “Accounts” tab. POP3 / IMAP / SMTP activation occurs automatically after account creation.

Both the Runbox creator and checker support the creation of up to 5 aliases for each Runbox account. To create aliases, enable the “Create aliases” checkbox on the “Accounts” tab and select an exact or random number of aliases to create. Created aliases are saved in a separate file named “Runbox 2021.05.17 – 16.29.07 aliases.txt” in the “Accounts” folder.

Important! Each alias accepts mail on Read more »

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

Feb 22

MailBot account creator updated to version 12.64.

Implemented unlocker of Yandex accounts locked by a password change request:

Form of a Yandex account locked by requirement to change the password

To unlock an account, you need to go through 4 steps:

  1. Solve a regular Yandex CAPTCHA image with Latin text.
  2. Answer the secret question correctly.
  3. Link a phone number via SMS verification.
  4. Set new password.

After completing all the steps, the account becomes fully operational (Yandex.Disk works, receiving/sending mail, etc.). To complete the second step, you will need to know the answer to the account secret question. Since version 12.64 MailBot exports the security question and the answer to it with the prefixes “SQ-” and “SQA-” respectivly, so that checker can correctly extract them from the account string (thanks to @Djekxa for the idea). It looks like this: Read more »

tavel \\ , , ,