bridgedb server having mail delivery problems
Nagios is unhappy about polyanthum:
WARNING: postfix mailq is 161 (threshold w = 100)
When I look at the
mailq, i see things like:
7397B100F84 59548 Sun May 23 13:00:47 info@REDACTED.example.com (temporary failure) email@example.com
in the logs, those look like:
May 27 00:04:56 polyanthum/polyanthum postfix/local: 7397B100F84: to=<firstname.lastname@example.org>, orig_to=<email@example.com>, relay=local, delay=299049, delays=299048/0.38/0/0.14, dsn=4.3.0, status=deferred (temporary failure)
a correctly sent mail, instead, looks like this:
May 27 00:06:07 polyanthum/polyanthum postfix/local: 4005E10109E: to=<firstname.lastname@example.org>, orig_to=<email@example.com>, relay=local, delay=0.74, delays=0.02/0/0/0.72, dsn=2.0.0, status=sent (delivered to command: procmail -a "$EXTENSION")
which brings me to procmail (which we should really abandon, IMHO).. its logs (in
~bridgedb/.procmail.log) are not very helpful either:
0 (null) bridges@bridgedb: 250 Recipient address accepted procmail: Program failure (70) of "esmtp"
.procmailrc hasn't changed since 2019, so i don't think this is a regressionin the procmail config itself... following the trace there, however, i see it pipes its message through esmtp (which, unfortunately, is kind of abandoned too) after doing some DKIM checks.
(this is out of scope for fixing the immediate problem, but, really, this kind of stuff should just be done by Postfix itself, which can be hooked into opendkim to check incoming DKIM signatures, and, obviously, deliver to another SMTP server...)
anyways. following the trail leaves me into the bridgedb daemon, and looking at its logfiles, the only trace i can find is...
00:20:48 DEBUG L376:server.validateTo() Validating SMTP 'RCPT TO:' email address...
so yeah, i'm not sure exactly what i'm supposed to do with this, but i guess i would flag it for someone...
/cc @cohosh maybe you know what to do with this? should i just ignore it?