Even the best config file won't save a cold IP. Gradually increase your volume over 30 days.
<source 0/0> always-allow-relaying yes process-x-virtual-mta yes # Allows the injection source to pick the VMTA Use code with caution. Copied to clipboard Best Practices for High-Volume Delivery
To help refine this template for your specific environment, let me know:
# Logging log_level = 3 log_file = /var/log/powermta.log sample powermta configuration file hot
# Pool C: dedicated transactional IPs <pool name="txn"> ips 203.0.113.30 max-msg-rate 2000/hour max-conn-per-ip 100 concurrency 20 reputation-weight 1.0 </pool>
When IPs are fully warmed up, you can lift restrictive caps, but you should never remove them completely.
: Directs PowerMTA to attempt opportunistic TLS encryption. Major providers prioritize inbox placement for encrypted mail. Even the best config file won't save a cold IP
}
# Define specific domain limits here (e.g., Gmail, Yahoo) domain gmail.com { max-smtp-msg-rate 100/h max-msg-rate 50/s max-connections 20 }
cold-virtual-mta vmta-cold-2 <domain *> max-cold-virtual-mta-msg 500/day</domain> </virtual-mta> Copied to clipboard Best Practices for High-Volume Delivery
Properly setting up SPF, DKIM, and DMARC. Sample powermta.conf (Optimized for High Volume)
max-msg-rate 2/M # Limit to 2 messages per minute during warm-up max-conn-rate 1/M # Limit connection attempts enable-starttls yes # Ensure secure delivery
<source 192.168.1.100> smtp-service yes always-allow-relaying yes process-x-virtual-mta yes hide-message-source true </source>
smtpd-enforce-spf no smtpd-enforce-dkim no
log-stats { file /var/log/pmta/stats.log format "csv" interval 300 keep 30 }