What proxy list formats are supported by MailBot?

Program supports specifying proxy details in URI format (RFC 3986):


That is, you can specify:

  • proxy protocol (optional part), you can specify: socks5, socks4, https, http, ssh
  • proxy username and password (optional part), separated by a colon
  • proxy address (mandatory part), consists of IP address or domain and port number, separated by a colon

Examples of valid formats:

  • IP:port
  • host:port
  • username:password@IP:port (ZennoBox format)
  • https://IP:port
  • socks5://username:password@host:port
  • ssh://username:password@IP:port

Important! If the username or password contains special characters from the set !#$&'()*+,/:;=?@[] then, according to the URI format, they must be URL encoded.

Does MailBot support IPv6 proxies?

No. MailBot supports only IPv4 and IPv4-IPv6 proxies.

Why is there no support for IPv6 proxies?

To date, IPv6 proxies have no advantages in terms of creating accounts, since IPv6 addresses are banned by entire subnets. In addition, only Yandex allows to sign up via IPv6 from email providers supported by MailBot.

What type of proxy is better to use?

It is always better to use a SOCKS proxies (SOCKS4 or SOCKS5 — it doesn’t really matter), since HTTP(S) proxies interfere with HTTP protocol when transmitting traffic and therefore, on average, generate much more errors than SOCKS proxies that work at TCP level and do not interfere with the HTTP protocol.

As a rule, proxy providers allow access to their proxies using any protocol, therefore, it is advisable to select the “HTTP(S)” proxy type only in cases where it is known for sure that proxies support only HTTP.

I have big list of proxies with only several unique IP addresses but with different port numbers. For example, a fragment of AWM Proxy‘s list:

Does the program properly handle such lists?

These are backconnect (also known as rotating) proxies. MailBot is able to create accounts with such lists, however, because these IP addresses are not real external IPs from which signup takes place, the proxy ban subsystem will not work correctly and it is recommended to disable it. It is planned to fully support the backconnect proxies in the future.

How to disable the registration limit from one IP address, in order to the proxies will not get banned at all by this criterion?

You need to setup settings “Accounts per IP address” to 0 and “IP address ban time (hours:minutes)” to 0:0 on “Creator” tab.

How to clear a list of erroneously banned proxies?

You need to delete \DB folder.

I use proxies from, why there is no connection to domains?

This is luminati‘s policy, they blocked access to some email providers. This is what their support answered on this issue: We don’t allow access to mobile domains (it’s blocked from our end) What is your use case for
However, domains, for example, are not blocked.

I want to use my own proxies for FunCAPTCHA or reCAPTCHA solution, how can I pass them to the CAPTCHA solving service? And what if my proxies are binded to IP address?

To pass the current proxy from MailBot to the CAPTCHA API for solving FunCAPTCHA or reCAPTCHA, you need to check “Send proxy for FunCAPTCHA” or “Send proxy for reCAPTCHA” checkboxes respectively on the “CAPTCHA” tab. If proxies are binded to IP address, use the instructions for 2Captcha API and CapMonster Cloud API. Unfortunately, other CAPTCHA solving services do not support such proxies.

I have 30k proxies in my list, but accounts are created very slow. Why?

A large list does not mean that there is a lot or even a single working proxy in it. Typically, the larger the list, the fewer working proxies it has, especially if the list was not purchased. Therefore, MailBot spends most of the time on checking non-working proxies. In this case, it is better to pre-select the working proxies from the list using a professional proxy checker, which is available for clients in the “Download” section.

3 Comments to “Proxy”

  1. 1. 75536299:

    если прокси с разными паролями в каком виде список давать проге

  2. 2. tavel:

    Индивидуальные логины/пароли для каждого прокси не поддерживаются

  3. 3. tavel:

    Начиная с версии 8.32, MailBot начал поддерживать индивидуальные логины/пароли для каждого прокси. Поддерживаемые форматы списков прокси перечислены в вопросах и ответах выше.

Написать ответ

Вы должны войти чтобы комментировать.