PowerMTA Configuration Guide: VMTAs, Queues & Throttling
PowerMTA is configured through a single text file that controls every IP, domain and delivery rule. This guide walks through the building blocks so you understand what every panel is really doing under the hood.
TL;DR
PowerMTA's behaviour lives in pmta.conf: source IPs, virtual-mta blocks, domain throttling and DKIM keys. Get the structure right and deliverability follows. If hand-editing scares you, AutoPMTA generates and manages this config visually.
The config file structure
Everything starts in pmta.conf. It is read top to bottom and built from directives and named blocks. The four pieces you'll touch most are source blocks, virtual-mta blocks, virtual-mta-pool blocks and domain blocks.
1. Virtual MTAs (VMTAs)
A VMTA ties a sending IP to a hostname. This is how you isolate streams:
<virtual-mta vmta1>
smtp-source-host 192.0.2.10 mail1.yourdomain.com
</virtual-mta>You then group VMTAs into pools so PowerMTA can rotate across IPs. Clean VMTA design is the foundation of IP warmup — each fresh IP gets its own ramp.
2. Domain throttling rules
Mailbox providers will throttle or block you if you send too fast. PowerMTA lets you cap delivery per provider:
<domain gmail.com>
max-msg-rate 100/min
max-smtp-out 20
</domain>Tuning these numbers per ISP is an art. Sending too aggressively triggers spam folder placement and 4xx throttling errors. Our deliverability guide covers the signals to watch.
3. DKIM signing
PowerMTA signs outbound mail with your DKIM key so receivers can verify it. You'll reference the private key and selector per domain. If DKIM, SPF and DMARC are new to you, start with our SPF, DKIM and DMARC setup guide.
4. Bounce & feedback-loop handling
PowerMTA classifies bounces (hard vs soft) and can process feedback-loop complaints automatically. Feeding this data back into suppression lists protects your reputation over time.
Why teams move to a panel
A real production config can run thousands of lines across dozens of IPs and domains. Editing it over SSH is slow and risky — a single misplaced brace can halt the queue. A management layer validates changes, shows you live queue state and prevents typos.
Skip the hand-editing. AutoPMTA builds, validates and manages your PowerMTA config with a visual UI for VMTAs, ISP rules and warmup — see the plans.
Key takeaways
- pmta.conf controls sources, VMTAs, pools and per-domain rules.
- VMTAs isolate IP/domain streams; pools enable rotation.
- Per-ISP throttling prevents blocks and 4xx errors.
- A panel removes the risk of hand-editing large configs.