On Fri, Nov 28, 2003 at 09:49:13AM +0100, Peter Rosa wrote:
[top-quoting undone here, i.e., text order "normalized"]
From: "Didier Casse" <didierbe(_at_)sps(_dot_)nus(_dot_)edu(_dot_)sg>
--- Logging /home/stu99/didierbe/mail/procmail.log for didierbe,
/usr/bin/spamassassin:
/usr/bin/spamassassin: No such file or directory
procmail: Error while writing to "/usr/bin/spamassassin"
procmail: Rescue of unfiltered data succeeded
----------------------------------------------------------------------
It seems that procmail can't trigger spamassassin, which btw is
really found in /usr/bin directory! I looked through Google but I
couldn't find a straightforward answer to this. Can anybody help
Check if you have at least exec/read permissions to the whole path
/usr/bin/spamasassin
In addition, check whether your server's invocation of procmail
occurs on a separate machine. Often there are multiple servers
involved in a mail setup. Your shell might be on one machine,
with /usr/bin/spamassassin available, but the mail might be
processed on an altogether different machine.
--
dman
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail