Demo
Demo

Knowledge base

PMTA knowledge base›Accounting record§ 12.2

Received

r
The message entered the node

The message was successfully submitted to the node — through a mail session or through the submission interface.

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

The only record about entry. All the others are about what happened next.

Matching what was received against what was delivered and bounced shows whether the balance adds up: a message that is in none of the outcomes got lost somewhere.

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. It reads them — the records arrive as a stream through a webhook, and all the analytics is built on them: volumes, deliverability, bounces by category.
Recommended values

Which question this record answers:

Question Is it this record
the message entered the node 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
r,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

2 relations

Does not work without

Sending addressThe sending address column: for a received message it may still be empty. § 12.2.5

Where you can see it

Two tags the sender puts on a messageIdentifiers the submitting side assigns to a message at submission. § 12.2.5

Referenced from

What to do with an accepted messageThe accounting record in which the result is visible. § 13.1

How to check on the node
How many records of each type arrived:
grep -c "^r," /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

◇The source default is the bottom rung, tied to whoever connectsA source block matching the sender’s address can name a default stream; it applies when no choice was made higher up the ladder.◇How a message gets into the engineSix described submission methods: extended SMTP, four language bindings and a directory the node watches on disk.◇A license for a fleet, not for a serverThe license is not bound to a server: it is installed on as many machines as the instance limit allows, and the nodes send volume statistics to the vendor every hour.

In the Hub
Cost of a mistake
safe: a wrong value breaks nothing
Scenarios
Connect a sending platform · Sender isolation