Knowledge base
The attempt failed at the queue level: the connection was refused, was not established or dropped before the conversation about messages.
The record type letter is tq. It comes first in the line, and that is how the parser tells one type from another.
It differs from an ordinary temporary failure in that the messages have nothing to do with it: there was not a single one that got discussed.
One such record means a failure for the whole queue at once, not for one recipient — and so it carries a different weight in counts.
Which question this record answers:
| Question | Is it this record |
|---|---|
| it never got to the messages — the connection itself failed | 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 tq,2019-02-08 21:53:41+0000,...
Related entries
2 relations
grep -c "^tq," /var/log/pmta/acct-*.csv cut -d, -f1 /var/log/pmta/acct-*.csv | sort | uniq -c
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.◇What makes a virtual machine riskyRunning on a virtual machine is possible, but the manual does not recommend it without sufficient hardware and properly tuned hypervisor settings: under load the node may stop responding.
- Cost of a mistake
- safe: a wrong value breaks nothing
- Scenarios
- Untangle a stuck queue