My Basket
A PowerMTA (PMTA) configuration file, typically located at /etc/pmta/config
, defines how the server handles incoming mail, manages queues, and delivers to external ISPs. Sample Configuration File
Below is a foundational "hot" configuration designed for high-throughput delivery and strict authentication:
# --- Basic Server Info --- host-name mail.yourdomain.com license-key "YOUR-LICENSE-KEY-HERE"
<domain outlook.com> max-smtp-out 10 require-starttls yes max-msg-rate 150/hour </domain>
If you want, I can:
Related search suggestions provided.
# --- General Server Options --- host-name ://yourdomain.com postmaster abuse@yourdomain.com run-as-root no # --- Performance & Resource Management --- # Limits for high-volume environments max-smtp-out 500 # Global limit for simultaneous connections max-msg-per-connection 100 # Optimal for most major ISPs max-errors-per-connection 10 # Prevent blacklist triggers on invalid lists # --- Logging & Management --- # Recommended to keep monitoring separate http-mgmt-port 8080 http-access 127.0.0.1 monitor http-access your.admin.ip.here admin Use code with caution. Copied to clipboard Key Setup Tips
IP Warmup: Never start a new "hot" config at full speed. Use the max-msg-per-hour directive to gradually increase volume over 2–4 weeks.
Authentication: Ensure your DKIM keys and SPF records are properly linked within the
Security: Always enable use-starttls for providers that support it (like Gmail and Outlook) to encrypt your mail in transit. sample powermta configuration file hot
Version Control: Keep your configuration in a system like Git to track changes and roll back if delivery rates drop.
Are you looking to optimize this for a specific ISP (like Gmail) or for a bulk marketing scenario?
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). A PowerMTA (PMTA) configuration file, typically located at
max-msg-per-connection 1000: Tells PMTA to send up to 1,000 emails per SMTP connection before closing it. This drastically reduces overhead.
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
<schedule 22-06> set max-smtp-out 50 set throttle-smtp-out 10000 </schedule>
content-filter smtp://127.0.0.1:10025 header-add X-Processed-By "PowerMTA hot-config" message-id-hostname mail1.example.com
smtp-source smtp-source-inject default-virtual-mta vmta-pool-1 # allow anyone from localhost or specific app server IP allow-ip 127.0.0.1 allow-ip 10.0.0.5 Notes and best practices
<domain gmail.com> max-smtp-out 20 vmta ent-flash, vip-luxury max-msg-per-connection 10 bounce-handler gmail-bounce </domain>
automatic-restart yes restart-threshold 3
-- end of file --
If you want, I can:
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