send-log verifiedcritical
Delivery log
in the configuration this is a line
send-log: /var/log/mailerq/send.logText log of every delivery attempt — the only record of intermediate attempts, which never reach the result queues.
Values
- Values
file path- Default
/var/log/mailerq/send.log · taken from the build- applying
restart required- where it can be set
in the config file · with a startup flag · as an environment variable
In detail
One line per attempt, in the shape set by send-log-format. The queues carry only final outcomes: a message that failed four times and is waiting for a fifth appears nowhere in success or failure, but every one of those four attempts is in this file. That makes it a required source rather than a convenience. Hub's collector already reads it for exactly this reason, in chunks, keeping its position — which also means the file must not be rotated out from under it faster than the collector runs.
What happens if you get it wrong
Rotated or truncated between collector runs.The attempts written in the removed part are lost for good — nothing else recorded them. Retry history for that window simply does not exist.inference · inference
Disabled to save disk.Final outcomes still arrive through the queues, but every intermediate attempt becomes invisible, and with it the whole picture of how hard a domain was pushed before it accepted.inference · inference