Go to content

Sample Powermta Configuration File Hot

To adapt this configuration to your specific needs, please share: The in your rotation pool Your estimated peak hourly email volume

Always monitor your PowerMTA Web Console during the first 24 hours of a new campaign to spot throttling issues in real-time.

throttle domain gmail.com

delivery-report yes delivery-report-path /var/log/pmta/reports sample powermta configuration file hot

By explicitly defining your sources, you prevent unauthorized access and ensure that submitted mail is correctly routed through your vMTA pool.

I’ve put together a that focuses on three critical pillars:

virtual-mta warm-pool

Last updated: May 2026 – Compatible with PMTA v4.5+.

Ensure your Mail-From domain, From-Header domain, and DKIM signature domains match up to pass strict DMARC verification policies.

A PowerMTA (PMTA) configuration file, typically located at /etc/pmta/config To adapt this configuration to your specific needs,

A "cold" or default PMTA config suffers from:

# Default limits for all domains max-smtp-out 20 max-msg-per-connection 100 retry-after 10m # Specific limits for Gmail to avoid "too many connections" max-smtp-out 5 max-msg-rate 200/h Use code with caution. Copied to clipboard Essential Configuration Tips

: Ensure your DKIM keys and SPF records are properly linked within the block to prevent immediate "junk" filtering. Ensure your Mail-From domain, From-Header domain, and DKIM

source /0 # Matches all connecting IPs always-allow-relaying true process-x-virtual-mta yes remove-received-headers false add-received-header true hide-message-source false require-auth true

This command applies configuration changes without stopping the mailer or dropping existing connections. No restart is required for most directive changes, except:

Back to content