The pair, ready-made
The queue name — the receiver and the sending address together.
It is part of the default set. The field set is defined in the accounting block, and fields are worth adding deliberately: there are as many delivery records as delivered recipients, and every extra column is multiplied by that volume.
A ready-made grouping key: no need to glue two fields together yourself.
The main trap is listing fields without the star. The field is in the default set, but a list in record-fields without * replaces that set: the lines keep only the named fields, and this one disappears silently.
What the Hub does. It does not read it — the event normalizer parses fourteen fields, and this one is not among them. The field is part of the default set, so it stays in the accounting file on the node and is available for manual investigation.
Recommended values
Where the field exists and whether the star includes it:
| Record type |
In the star |
| d — delivery |
yes |
| b — bounce |
yes |
| t — temporary failure |
yes |
| tq — queue failure |
yes |
In a shared file an empty value comes in two kinds: the line has no data — or the field is not selected for its record type.
The record types with this field and the default set markers come from the manual (§ 12.2.1, § 12.2.2, § 12.2.3, § 12.2.4); a list without the star replaces the set — § 3.3.11.12. The table is ours.
Example configuration
<acct-file /var/log/pmta/acct.csv>
record-fields d *, !orcpt</acct-file>
The star with ! removes an unwanted field while queue stays; a list without the star would keep only what it names.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.