Subject: Technical Assessment Report: PowerMTA 60r3
Date: October 26, 2023 Prepared For: IT Operations / Email Engineering Team Product Version: PowerMTA v6.0r3 (Release 3)
Unlike cloud senders, PMTA requires manual warmup. Use conditional throttling: powermta 60r3
<domain gmail.com>
max-smtp-out 20 # Start low
max-msg-rate 50 # Then increase by 10% daily
warmup "2d" # PMTA v6 feature: automatically ramp up over 2 days
</domain>
<source group high_trust> process-x-remote-mta-name true </source>
<virtual-mta ipv4_pool_1> smtp-source-host pool1.yourdomain.com bind-ip 192.168.1.101-150 max-smtp-out 100 dns-timeout 30 </virtual-mta>
PowerMTA 6.0r3 utilizes a multi-process architecture rather than a single-threaded monolith. It introduces the concept of Pipes.
Administrators can define specific "Pipes" for specific types of traffic (e.g., a dedicated pipe for transactional mail and another for bulk marketing mail). This prevents a backlog in one queue from choking the resources of another, ensuring critical transactional messages are delivered even during high-volume bulk blasts. Step 3: Domain Warmup Configuration (Critical for 60r3)
<domain>)Prior to v6, throttling was primarily IP-based. 60r3 introduced granular domain-level throttling. You can now limit sending to yahoo.com to 500 messages/second while allowing internalcorp.com to run at 10,000/sec.
Example snippet from config file:
<domain yahoo.com>
max-smtp-out 500
max-msg-rate 100
</domain>
<domain yourdomain.com> dkim-sign yes dkim-signature dkim._domainkey.yourdomain.com dkim-private-key /etc/pmta/keys/dkim-private.pem dkim-selector default dkim-headers "From:Subject:Date:To" </domain>
Subject: Technical Assessment Report: PowerMTA 60r3
Date: October 26, 2023 Prepared For: IT Operations / Email Engineering Team Product Version: PowerMTA v6.0r3 (Release 3)
Unlike cloud senders, PMTA requires manual warmup. Use conditional throttling:
<domain gmail.com>
max-smtp-out 20 # Start low
max-msg-rate 50 # Then increase by 10% daily
warmup "2d" # PMTA v6 feature: automatically ramp up over 2 days
</domain>
<source group high_trust> process-x-remote-mta-name true </source>
<virtual-mta ipv4_pool_1> smtp-source-host pool1.yourdomain.com bind-ip 192.168.1.101-150 max-smtp-out 100 dns-timeout 30 </virtual-mta>
PowerMTA 6.0r3 utilizes a multi-process architecture rather than a single-threaded monolith. It introduces the concept of Pipes.
Administrators can define specific "Pipes" for specific types of traffic (e.g., a dedicated pipe for transactional mail and another for bulk marketing mail). This prevents a backlog in one queue from choking the resources of another, ensuring critical transactional messages are delivered even during high-volume bulk blasts.
<domain>)Prior to v6, throttling was primarily IP-based. 60r3 introduced granular domain-level throttling. You can now limit sending to yahoo.com to 500 messages/second while allowing internalcorp.com to run at 10,000/sec.
Example snippet from config file:
<domain yahoo.com>
max-smtp-out 500
max-msg-rate 100
</domain>
<domain yourdomain.com> dkim-sign yes dkim-signature dkim._domainkey.yourdomain.com dkim-private-key /etc/pmta/keys/dkim-private.pem dkim-selector default dkim-headers "From:Subject:Date:To" </domain>