On Wed, 21 Nov 2018, Bill Cole wrote:
On 21 Nov 2018, at 1:56, @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.
This is a Postfix configuration problem. Don't use the 'pipe' transport for
spam filtering or make sure that whatever it is calling is a *robust* script
that does not rely on the pipe transport to handle breakage.
I'm not familiar with Postfix.
Is /usr/local/bin/spam-filter a standard Postfix message processing
interface mechanism that has been locally configured to call spamc in a
fragile manner?
Or is /usr/local/bin/spam-filter a third-party filtering tool with SA
hooks such that this failure should be reported to *them*?
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Vista: because the audio experience is *far* more important than
network throughput.
-----------------------------------------------------------------------
601 days since the first commercial re-flight of an orbital booster (SpaceX)
