Knowledge base
A message template is split into numbered parts — headers, a paragraph, a block of paragraphs, a body part — and each recipient gets the ones named in their *parts variable: as a list or a range, for example 1,3 or 1-3.
The list sets the order of parts: *parts=1,3,2 puts the third part before the second.
A variable from an optional part is needed only by the recipients who get that part.
How *parts reads:
| Value | What goes out |
|---|---|
| 1-3 | all three parts |
| 1,3 | the first and the third |
| 1,3,2 | three parts, the third before the second |
# a recipient without the second part XDFN FName="Bob" *parts=1,3 RCPT TO:<bob@example.com>
Related entries
1 relation
Reserved merge variable namesA related mechanism: they work together. § 11.19.4.3
grep -rn 'allow-mailmerge' /etc/pmta/
What else to read
3 articles
◇Four ways to say “slower”Messages, data volume, connection rate and number of connections — each has its own limit, and each has a “per source address” variant and a backoff mode twin.◇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.◇The sending address — what it is made ofA named set of everything that is a property of the address: which IP the message leaves from, how the node introduces itself, what it signs with and how fast it sends.
- Cost of a mistake
- safe: a wrong value breaks nothing
- Scenarios
- Address warm-up