The block gathers rules for reacting to receiver responses during delivery. The mechanism is analyzed separately (smtp-pattern-list); this is about the block.
It lives at the top level and acts by reference from a receiver block. Without a reference the rules are not applied to any queue.
This is the only way into backoff mode. Directives with the backoff- prefix describe what will happen; a match here decides when (backoff-mode).
Do not confuse it with the sending address selection list — the name differs by one word, and it works on the opposite side of the node (<pattern-list>).
# the list and the reference to it — they do not work apart <smtp-pattern-list block-errors> reply /^421 .* too many errors/ mode=backoff</smtp-pattern-list> <domain aol.com> smtp-pattern-list block-errors </domain>
0 relations
Backoff mode — the queue's second personalityThe only thing that switches the mode on: an action on a match of the receiving server’s reply. § 3.3.10.53backoff-to-normal-after<domain>A mailbox provider rule can carry its own return period — and then this directive is ignored for that queue. § 3.3.10.53reenable-source-ip-after<domain>Ignored if a mailbox provider rule disabled the address with its own return deadline. § 3.3.10.56smtp-pattern-list<domain>The list itself is declared by this block; the line only attaches it to the recipient domain. § 3.3.10.101
3 articles
◇Two inbound report processors and what to do with themBounces by message and complaints are parsed by two identically structured blocks; each has its own address list and its own pair of decisions about the message’s fate.◇A return address with the recipient written into itThe bounce arrives at a unique address, and there is no need to parse its content.◇What to return in a bounce reportWhat to enclose in a bounce report: the whole message or only its headers.