Knowledge base
The block describes one sending address: which IP the message leaves from and what name the node introduces itself with. Everything written inside applies to this address and no other.
Limits written here count the address as a whole — across all receiving servers at once. This is the level at which most decisions about the fleet are made: how much the address sends per hour, how many bytes, how many connections it holds.
Hence the name collision. The same directive names appear both here and in the receiver block — because the question “how much” is asked at both levels, and the answers add up. The mechanism is covered separately (virtual-mta).
A receiver block can be nested inside — then the receiver policy will be this address’s own. That is what the Hub does: it writes the rate and backoff mode inside the address rather than at the node level.
# address properties outside, receiver policy inside <virtual-mta mta-news-1> smtp-source-host 1.2.3.4 news1.example.com domain-key sel1,example.com,/etc/pmta/keys/sel1.pem <domain *> max-msg-rate 500/h </domain> </virtual-mta>
Related entries
0 relations
smtp-source-hostGlobalWritten inside a sending address, the directive is what turns the node’s address set into separate sending identities. § 3.3.1.22include-headers-fromGlobalThe headers are inserted into all messages of a sending address; a line written at the node level goes to each of them. § 3.3.1.55.3Warm-up built into the engineThe cold partner is an ordinary sending address and is declared with the same block. § 3.3.10.57reroute-to-virtual-mta<domain>The target address or pool must exist; the block itself is described on a separate page. § 3.3.10.58backoff-reroute-to-virtual-mta<domain>Where messages are moved to: the block of another sending address — or a pool. § 3.3.10.59
What else to read
3 articles
◇Headers the sender uses to control deliverySix control headers let the submitting side choose a stream, tag a message with a job, set signing options and the key, the envelope identifier and the schedule; each is allowed separately and per source.◇Backoff mode — the queue's second personalityA queue that a receiver has started refusing switches to a parallel set of limits, retries and routes — ten directives that act only in this mode.◇Warm-up built into the engineA warmed-up address hands the first N messages of the day for each receiver to its cold partner; the partner sends them itself and builds history.
- Cost of a mistake
- reversible: harms only while it is set
- Scenarios
- Sending address rotation
- Priority
- critical