Knowledge base
One delivery attempt failed, and the recipient stays in the queue until the next one.
The record type letter is t. It comes first in the line, and that is how the parser tells one type from another.
There can be several records per message — one per attempt. You cannot count messages by them: you will get the number of attempts.
After such a record the recipient usually moves to the waiting area and is unavailable for sending until the deadline.
Which question this record answers:
| Question | Is it this record |
|---|---|
| the attempt failed, but the message stays | 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 first letter of the line is the record type t,2019-02-08 21:53:41+0000,...
Related entries
2 relations
grep -c "^t," /var/log/pmta/acct-*.csv cut -d, -f1 /var/log/pmta/acct-*.csv | sort | uniq -c
What else to read
3 articles
◇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.◇Backoff mode — the queue's second personalityA queue that a receiver has started refusing switches to a parallel set of limits, retries and routes — ten directives that act only in this mode.◇Reputation monitoring inside the nodeThe engine itself watches the receiving servers’ replies and changes the queue mode on a pattern match — a reaction within the connection, not through telemetry.
- Cost of a mistake
- safe: a wrong value breaks nothing
- Scenarios
- Troubleshoot deliverability · Tune the pace for a provider