Demo
Demo

Knowledge base

PMTA knowledge base›Accounting record§ 12.2

Delivery notification

rs
A report that is not about a bounce

A delivery status notification that is not a bounce has arrived — for example, a delivery confirmation.

The record type letter is rs. It comes first in the line, and that is how the parser tells one type from another.

The rarest record type: few receivers send such notifications, and only on request.

It is useful as a delivery confirmation from the receiver itself, rather than by the fact of handing the message over. But it cannot be relied on: far from everyone sends it.

The main trap is counting things from the wrong records. One record type answers one question, and a substitution gives a plausible wrong number: attempts instead of messages, queues instead of recipients, the day a report was received instead of the day of sending.
What the Hub does. There are no report processors in the configuration, so such records do not appear. Reports that arrive as emails are accepted at role addresses and discarded.
Recommended values

Which question this record answers:

Question Is it this record
a report that is not about a bounce yes
how many messages in total only together with the other types
why it happened look at the reply text, not at the record type

Record types are enabled and disabled in the accounting block. A disabled type does not disappear from a report — it disappears from the data, and the absence of events becomes indistinguishable from there genuinely being none.

The separation of questions is ours. From the manual here are the condition under which the record appears and its letter.
Example configuration
# the first letter of the line is the record type
rs,2019-02-08 21:53:41+0000,...
Parsing accounting starts with this letter: all the other columns make sense only in combination with it.
yellow — — directive names, blue — blocks. They are highlighted the same way in the text of the card.
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

1 relation

Same name in other blocks

Parsed bounce from outsideA neighboring type: there the report is about a failure, here about everything else. § 12.2.6

How to check on the node
How many records of each type arrived:
grep -c "^rs," /var/log/pmta/acct-*.csv
cut -d, -f1 /var/log/pmta/acct-*.csv | sort | uniq -c
Zero while sending is going on means one of two things: there are no events of this kind, or the record type is disabled in the accounting block. The second command helps tell them apart — it prints a summary across all types.
◇

What else to read

3 articles

◇What the node tells about itself and through which channelsSeven observation surfaces: the web monitor, the console in four formats, the log, accounting, accounting search, metrics and export to external analytics.◇The watchdog that restarts the engineKeeps an eye on the engine and brings it back up after a crash by itself, sending a crash report to the postmaster address.◇How the policy for a receiver is assembledSettings are assembled from the most general pattern to the most precise; the order of blocks in the file means nothing.

In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Scenarios
Troubleshoot deliverability