Demo
Demo

Knowledge base

PMTA knowledge base›Configuration block§ 3.3.5

<address-list>

A list of addresses, domains, patterns or hashes
The name decides what the list is for

The block gathers addresses, domains, patterns and hashes into one named entity that directives then refer to.

With a name the list is attached by it: suppression-lists for suppression, allowed-sender-lists for allowed senders. It is declared at the root of the file.

Without a name the block is written inside <bounce-processor> or <feedback-loop-processor> and selects the mail that processor parses. This is not suppression — a common misreading.

The list is filled by five directives: address, domain, address-file, hashed-address, hashed-address-file.

Example configuration
# named — declared at the root and attached by name
<address-list suppression1>
    address foo@bar.com
    address /^bounce@/
    domain example.net
</address-list>

# unnamed — lives inside a processor and selects mail for parsing
<bounce-processor>
    <address-list>
        address /^bounce@bounce\./
    </address-list>
</bounce-processor>
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.
Block directives: 5
Suppression 5
hashed-addressAn address hash instead of the address itselfaddressset by the HubAn address, local part or pattern in a listaddress-fileList addresses from a separate filedomainA whole domain in an address listhashed-address-fileAddress hashes from a separate file
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.
◇

What else to read

3 articles

◇Accept, route, deliverA message’s path inside the node: accept, decide where, deliver — and all the settings live between these three steps.◇Four value types the whole config is written inBoolean, domain pattern, regular expression and time interval — defined once in § 3.2 and then used by all directives.◇Reloading settings versus restarting the serviceThe configuration is read at startup, and after that edits are picked up by the reload command — except for the directives the manual marks as requiring a restart.

In the Hub
Cost of a mistake
reversible: harms only while it is set
Scenarios
Configuration lifecycle