Proxy pools.
Sets of addresses
for a server and a domain.

The proxy pools page starts with the module tabs, a period choice and the “Create a pool” button. Below is a short hint on what a pool is: who to send to and through what — a server, a domain, replacement rules and a reserve. It also reminds you of the key point: a proxy belongs to exactly one pool, and a pool’s purpose is a hint, not a restriction. The period — 24 hours, 7 or 30 days — only changes the message data on the cards; the makeup and settings of the pools don’t depend on it. If there are no pools yet, this is where you start: create a pool, then fill it with fit addresses from the proxy list.

Enlarge

• Module tabs — this page is the “Pools” tab; next to it are Proxies, Rules, Gates and the other Proxy Gate sections.
• Period — 24 hours, 7 or 30 days; over this span the cards count messages and deliverability.
• Create a pool — opens the new pool dialog.
• Hint — a pool is a node, a domain, its own replacement rules and its own reserve; a proxy lives in exactly one pool.

A pool’s purpose is a hint, not a restriction: it helps you understand what the pool is for but doesn’t limit anything.

The card of a pool for live campaigns on the mta-01 server. The pool has three addresses, all sending, subdomains px-01…px-03 in the news.lumacart-shop.com domain, and the “Careful” rules. The reserve share is 30%, yet there are no spare addresses, and the card warns about it right under the address count: if an address goes bad, the replacement rule will have nothing to swap in. At the bottom — deliverability over the week, 13,946 messages and 97.9% delivered, and the buttons for working with the pool. The pool is made up of two grade A addresses and one B; to cover the missing spare, you add a fit address to the pool with the “Add proxies” button.

Enlarge

• Name and purpose — “Sending · marketing”, live campaigns.
• Address count — 3 proxies, all sending; below it — “spares short: 1”.
• Node and domain — mta-01 and news.lumacart-shop.com with subdomains px-01…px-03.
• Recipients — “send to all” — the pool doesn’t exclude any mailbox provider.
• Rules — “Careful” · 4 pool rules — as in the preset; the arrow leads to the “Rules” tab.
• Grade bar — two grade A addresses and one B.
• Deliverability — 97.9% of 13,946 messages over the period.
• Proxies, Add proxies, Configure — show the addresses, add to the pool, and open the settings dialog.

The pool’s reserve share is 30%. With three sending addresses, at least one spare is needed, otherwise the replacement rule will have nothing to swap in.

The second pool works on the mta-02 server and is made up of five addresses of varying quality. Two addresses are sending, two wait in reserve, one is in quarantine — port 25 closed on px-06. The grade bar shows the mix right away: three B addresses, one C and one D. The pool’s deliverability is 91.8% of 11,800 messages: it includes px-06’s messages sent before quarantine. The card shows that there are spares for replacement and that the address that went bad has already been pulled from sending. Deliverability also includes the messages of px-05, which Yahoo doesn’t accept; the pool’s address table helps you sort it out — the “Proxies” button opens it.

Enlarge

• Address count — 5 proxies: 2 sending, 2 in reserve, 1 in quarantine.
• Node and domain — mta-02 and news.lumacart-shop.com with subdomains px-04…px-05.
• Rules — “Normal” · 4 pool rules — as in the preset.
• Grade bar — B are working, C are secondary, D are not fit for mail: port 25 closed on px-06.
• Deliverability — 91.8% of 11,800 messages over the period.

Deliverability includes both px-06’s messages sent before quarantine and the messages of px-05, which Yahoo doesn’t accept.

The “Proxies” button opens the pool’s addresses right inside the card — no need to go to another tab. The table shows how each address is doing: subdomain, how many messages it sent, what share arrived, how fast the mail server answers and what state the address is in. In the example px-05 delivers 79.0% and gets the mail server’s greeting only after 2.4 s — that’s where to start digging. The address’s name takes you to its page. The reserve addresses px-07 and px-08 have no subdomain or messages yet — a subdomain is issued when the address is put into sending — and px-06 is in quarantine with grade D.

Enlarge

• Proxy · entry → exit — the name, the connection address with its port, and the exit IP.
• Grade — the address’s rating from the checks: C for px-05, D for px-06.
• Subdomain — the address’s name in the pool’s domain; reserve and quarantined addresses don’t have one.
• Messages and delivered — px-04 has 4,910 messages and 97.1%, px-05 has 79.0%.
• To banner — how long to wait for the mail server’s greeting: 2.4 s for px-05.
• State — sending, in reserve or in quarantine.

The reserve addresses px-07 and px-08 haven’t sent yet: they have neither a subdomain nor messages — a subdomain is issued when the address is put into sending.

The “Outside pools” block shows addresses that aren’t in any pool and so send no mail. In the example there are none: outside pools there’s only the rejected px-09, which is counted in the caption but not shown as a separate row. At the bottom it explains what happens to rejected addresses: a free one is deleted with a fingerprint, while bought ones and your own VDS stay in the Hub. The total “3 + 5 + 1 = 9” matches the number of proxies. Addresses of a deleted pool also land here: sending ones are taken out of sending, and fit ones get the “accepted” state and wait until they’re added to another pool.

Enlarge

• Block caption — 0 addresses take no part in anything, 1 more is rejected — it isn’t counted here.
• Rejected free address — deleted from the database with a fingerprint: collection from sources won’t add it again, a manual import will add it and check it again.
• Bought and own VDS — stay in the Hub even if they failed the check.
• Total — 3 + 5 + 1 = 9 — that’s how many addresses are in the whole proxy list.

The total across pools and the “Outside pools” block always matches the overall number of addresses — no proxy gets lost.

The “Configure” dialog of the “Sending · marketing” pool. Here you change the name, purpose, server, domain, rules label, reserve and recheck interval. Next to the fields you see their status: the gate on mta-01 is running, the domain’s signing key is active, and in PowerMTA it is the proxy-pool-1 pool, whose name doesn’t change on rename. A red line warns in advance that changing the server or domain will stop sending until the new DNS records are visible everywhere. You can also see that with a 30% reserve the pool is one spare address short, and the recheck is set to every 24 h.

Enlarge

• Name — in PowerMTA it is the proxy-pool-1 pool; the pool name doesn’t change on rename.
• Purpose — “live campaigns” — a hint that forbids nothing.
• Node — mta-01 — gate running, hubgate 1.1.0.
• Sending domain — the signing key is active, subdomains are px-01.news.lumacart-shop.com and onward.
• How to replace proxies — Careful, Normal or Hard — the pool’s label; the rules themselves are set on the “Rules” tab.
• Reserve — none, 20, 30 or 50% — now 30%, and one spare is missing.
• Check — default, or every 1, 6, 24 or 72 hours; here — once a day.
• Do not send to these providers — only a note for now; it doesn’t affect sending.

You can delete the pool from the same dialog. The addresses stay in the Hub and move to the “Outside pools” block.

The “Create a pool” dialog has the same fields as the settings. From the name reserve-eu you see right away which PowerMTA pool it becomes — proxy-pool-reserve-eu. In the example the purpose “waiting to step in” is chosen, the mta-01 server with a running gate and the news.lumacart-shop.com domain with an active signing key. At the bottom of the dialog is a summary of what you’ll get: server, domain, 30% reserve and the default check. So before you even save, it’s clear where and on whose behalf the new pool will work. While the new pool is empty it sends nothing — you add addresses to it right after creating it with the “Add proxies” button.

Enlarge

• Name — reserve-eu will become the proxy-pool-reserve-eu pool.
• Purpose — “waiting to step in” — a pool for spare addresses.
• Node and domain — mta-01 with a running gate and news.lumacart-shop.com with an active signing key.
• How to replace proxies — the example has “Normal” selected — default thresholds.
• Summary at the bottom — mta-01 · news.lumacart-shop.com · reserve 30% · default check.

While the pool is empty it sends nothing — you add addresses to it with the “Add proxies” button.

“Add proxies” on the “Sending · marketing” pool opens the proxy list in selection mode. The candidates are addresses fit for mail; if an address is already in another pool, it says right there that adding will take it from there. In the example px-07 and px-08 are ticked — spare addresses of the second pool that the first one lacks. This way you top up the reserve straight from the list and see in advance which pool the addresses are taken from. The address px-06, with port 25 closed, isn’t among the candidates — so an address unfit for mail doesn’t get into the pool, and the panel at the bottom offers “Add to pool ‘Sending · marketing’”.

Enlarge

• Mode line — tells you which pool you’re picking addresses for and lets you leave the mode.
• Warning on the address — “currently in the ‘Ramping up new addresses’ pool — adding will take it from there”.
• Ticked — px-07 and px-08 — spare addresses of the second pool that the first one lacks.
• Add to pool — the panel button moves the ticked addresses.

The address px-06, with port 25 closed, isn’t among the candidates: only addresses fit for mail become candidates.