Generating PDF…
This write-up provides a sample "hot" (high-throughput/aggressive) configuration for PowerMTA 5.x/6.x, suitable for dedicated high-volume sending infrastructure, ensuring maximum speed and deliverability in 2026.
A "hot" config generally means reducing delays, enabling aggressive parallel connections, using multiple IP addresses (rotation), and minimizing internal logging overhead to maximize outbound throughput. ⚠️ Warning: Before You Use This
Warm-up: If these are new IPs, do not start with a hot config. You will be blocked.
Reputation: This config assumes you have already established a good IP reputation.
DNS: Ensure SPF, DKIM, DMARC, and rDNS are perfectly set up before applying these settings. Sample PowerMTA Hot Configuration File (/etc/pmta/config)
# ========================================================== # PowerMTA Hot Configuration Sample (2026) # ========================================================== # -- Global Settings -- Use code with caution. Copied to clipboard Key "Hot" Configuration Components
Virtual MTA Pool (
max-smtp-out 500: Sets a high number of parallel connections allowed to a single destination domain (e.g., yahoo.com).
max-msg-per-connection 1000: Tells PMTA to send up to 1,000 emails per SMTP connection before closing it. This drastically reduces overhead. sample powermta configuration file hot
max-conn-rate 10/s: Allows the server to open 10 new connections per second.
Logging Optimization (log-connections no): Disables detailed logging of every connection command, which saves disk I/O and increases speed.
hide-message-source true: Removes IP information from email headers to protect privacy, often used to prevent internal IP exposure. Steps to Apply
Backup current config: cp /etc/pmta/config /etc/pmta/config.bak Edit the config: nano /etc/pmta/config Validate config: pmta reload (check logs for errors) Restart PMTA: systemctl restart pmta To help tailor this config further, could you tell me: How many IPs are you using? What is your estimated daily sending volume?
Are you primarily sending cold outreach or opt-in marketing?
I can provide specific rate limits (max-smtp-out) based on your answer. PowerMTA Server Setup | Send 100K+ Emails Daily
In PowerMTA (PMTA), a "hot" configuration generally refers to high-volume or "aggressive" delivery settings, often used for warming up IPs or sending to high-reputation recipients. This configuration is typically managed within the /etc/pmta/config Sample High-Volume (Hot) Config Review A robust PowerMTA configuration uses
directives to control delivery traffic. Below is a review of standard "hot" parameters: Moving from PowerMTA - KumoMTA Let me explain what each section does: Introduction:
powermta.conf
# PowerMTA configuration file
# General settings
server_name = "example.com"
server_id = "example.com"
# Logging settings
log_level = "info"
log_file = "/var/log/powermta.log"
# MTA settings
mta_bind_address = "0.0.0.0"
mta_bind_port = 25
# Authentication settings
auth_type = "auth_file"
auth_file = "/etc/powermta/auth_file"
# Relay settings
relay_hosts = "trusted_mta.example.com"
relay_port = 25
# Domain settings
domain "example.com"
# MX records
mx_record "mx1.example.com" 10
mx_record "mx2.example.com" 20
# Mailbox settings
mailbox "/var/mail/%d/%u"
format = "mbox"
# Virtual domain settings
virtual_domain "virtual.example.com"
# Mailbox settings
mailbox "/var/mail/virtual/%u"
format = "maildir"
# User settings
user "postmaster"
# Mailbox settings
mailbox "/var/mail/postmaster"
format = "mbox"
# Access control settings
access_control
# Allow relaying from trusted hosts
allow relay from "trusted_mta.example.com"
# Deny relaying from blocked hosts
deny relay from "blocked_mta.example.com"
# Miscellaneous settings
bounce_queue = "/var/spool/powermta/bounce"
queue_dir = "/var/spool/powermta/queue"
Let me explain what each section does:
In the world of high-volume email delivery, PowerMTA (PMTA) by SparkPost is the gold standard for MTA (Mail Transfer Agent) software. However, a standard, out-of-the-box configuration will not survive a modern sending environment. To handle millions of emails per hour, you need a "hot" configuration file—one that is aggressively tuned for throughput, DKIM signing, bounce handling, and ISP throttling.
This article provides a sample PowerMTA configuration file hot environment engineers can deploy immediately. We will dissect every critical directive, explain why default settings fail, and show you how to achieve blazing-fast delivery without landing in the spam folder.
<domain *>
dkim-sign yes
dkim-identity @mydomain.com
dkim-private-key-file /etc/pmta/keys/mykey.pem
spf-envelope-from mydomain.com
</domain>
bounce-log yes bounce-log-path /var/log/pmta/bounce bounce-server mailbounce.example.com bounce-smtp-port 25 max-bounce-recipients 100
http-mgmt-port 8080 http-access 1.2.3.4 monitor # Allow only your admin IP to view logs Use code with caution. Copied to clipboard Step-by-Step Implementation Guide Preparation : Ensure you have a static IP address domain name with the hostname (e.g., mail.yourdomain.com ) set in your server's settings. Install PowerMTA : Upload your RPM or DEB package and install it using rpm -ivh PowerMTA.rpm Place License File : Copy your license.dat /etc/pmta/ Edit the Config YOUR-LICENSE-KEY-HERE with your actual key. smtp-source-ip to your server's public IP. Ensure the matches your domain's rDNS (Reverse DNS) record to avoid being flagged as spam. Set Up DKIM
: Generate a private/public key pair and place the private key in the path specified in the Apply Changes Test for syntax errors: pmta --check-config pmta debug Restart the service: service pmta restart systemctl restart pmta Monitor Performance : Access the web monitor at smtp-source-host 192.168.1.11 ://example.com
In PowerMTA (PMTA), a "hot" configuration refers to a setup optimized for high-throughput delivery hot-standby/disaster recovery
. Configuring PowerMTA effectively involves defining Virtual MTAs (VMTAs), setting domain-specific throttling rules, and ensuring proper authentication to maintain a high sender reputation. Core PowerMTA Configuration Components The primary configuration file is typically located at /etc/pmta/config
. A robust setup for high-volume or "hot" delivery includes: Virtual MTA (VMTA) Definition
: Assigns specific IP addresses to named pools, allowing you to isolate traffic by brand or type of mail. Domain Directives
: Sets delivery limits for major ISPs (like Gmail or Yahoo) to avoid being flagged for spamming. Authentication : Implements to verify sender identity. Throttling & Rates
: Controls the number of connections and messages per minute to match ISP expectations. Dheera Group Sample "Hot" Configuration Snippet
Below is a conceptual example of a configuration designed for a high-performance environment with multiple IPs and ISP-specific tuning.
# Define your local IPs as Virtual MTAs
source-ip 192.168.1.101 default-virtual-mta "vmta-pool-1" smtp-name mail1.yourdomain.com
source-ip 192.168.1.102 default-virtual-mta "vmta-pool-1" smtp-name mail2.yourdomain.com