@lbutlr wrote:
While updating spamassassin, several emails were destructive lost because of
the absence of spamc. To be fair, the date did get stuck unexpectedly asking
for a confirmation, but still I’d like to avoid this happening again.
Nov 20 10:20:34 mail postfix/pipe[73448]: 42zsss3jHVzcfQ1: to=<xan...@xanmax.com>,
orig_to=<u...@example.com>, relay=spam-filter, delay=0.63, delays=0.61/0/0/0.02,
dsn=2.0.0, status=sent (delivered via spam-filter service (/usr/local/bin/spam-filter: line
23: /usr/local/bin/spamc: No such file or directory))
Nov 20 10:20:34 mail postfix/qmgr[85457]: 42zsss3jHVzcfQ1: removed
The result is a message that has a minimal set of headers and no content.
It's up to whatever calls spamc to handle this correctly.
The custom delivery handler we use has a sub to check for several key
"does this thing exist?" requirements, including "does spamc exist in
the right place, and is it executable?".
It also has a couple of last-minute checks for other, more subtle
failures in piping a message to spamc (and other programs), and returns
the appropriate error codes to the delivering MTA.
-kgd
