Demo
Demo

Knowledge base

PMTA knowledge base›Configuration block§ 3.3.14

<pattern-list>

Named selection rules
A layer between what a message looks like and where it will go out from

The block gathers rules for choosing a sending address by message content. The mechanism is analyzed separately (pattern-list); this is about the block itself.

It lives at the top level but acts by reference. A list does nothing by itself: it is attached with a line in a submission block. A list without a reference is a dead setting.

There can be several lists, and different submitting systems can use different ones.

Do not confuse it with the receiver reaction block — that one is named almost the same (<smtp-pattern-list>), but lives on the other side of the node.

Example configuration
# the list and the reference to it — they do not work apart
<pattern-list pmta-pattern>
    mail-from /@example\.com$/ virtual-mta=mta-news-1
</pattern-list>
<source {pmta-auth}>
    pattern-list pmta-pattern</source>
The highlighted line is the one without which the list does not act on a single message. The block by itself only describes the rules.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.
Block directives: 3
Routing 3
headerA rule on a named message header that selects a stream or a prioritymail-fromset by the HubA rule on the envelope return address that selects a stream or a priorityrcpt-toA rule on the recipient address that selects a stream or priority
Compatibility
PowerMTA 6.0
described in the manual of this version · platform: any
The vendor does not state the first version for every directive — there is no note here. The name also appears in the 5.0 edition of the manual.
⇄

Related entries

0 relations

Referenced from

pattern-list<source>The rule list itself: it is declared as a separate block and must appear in the file above the source that references it. § 3.3.7.42bounce-category-patterns<domain>Parsing works the same way as in reply pattern lists — and is described there in more detail. § 3.3.10.73

◇

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.

In the Hub
Cost of a mistake
reversible: harms only while it is set
Scenarios
Sending address rotation