Demo
Demo

Knowledge base

PMTA knowledge base›Configuration block§ 3.3.6

<email-patterns>

Patterns for parsing non-standard reports
Custom parsing for a receiver that writes in its own way

The block contains patterns by which the engine parses the bodies of non-standard reports. It has two lines: body-pattern-file — the pattern file itself, repeatable; log-match-info — show in the log which of them matched.

The block is nested in a processor, not written at the root of the file. The bounce processor and the complaint processor have their own sets of patterns.

The extracted fields go into accounting and are placed in the record next to what the engine found itself. For analytics a non-standard report then becomes indistinguishable from a standard one.

Example configuration
# each processor has its own set of patterns
<feedback-loop-processor>
    <email-patterns>        body-pattern-file /etc/pmta/spamcop.txt
        body-pattern-file /etc/pmta/other-isp.txt
        log-match-info true
    </email-patterns>
</feedback-loop-processor>
With several files the second line is mandatory during setup: without it you cannot tell which pattern fired.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.
Block directives: 2
Bounces 1
body-pattern-fileA file with a pattern for parsing a non-standard report
Diagnostics 1
log-match-infoWhether to log which rule recognized a report
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