Vicki Brown:
> I have two long and complicated errors at approximately midnight on both Nov
> 17 and Nov 18; however, the spam checking continued happily for 2 hours after
> that.
>
> mail.log:Nov 18 00:02:31 g3po postfix/pipe[590]: E8F682F69538:
> to=<[email protected]>, relay=spamfilter, delay=438, delays=436/0.04/0/2.1,
> dsn=4.3.0, status=deferred (temporary failure. Command output: spamchk: Spam
> filter piping to SpamAssassin: /usr/local/bin/spamc -x -E -s 10485760
> spamchk: Message OK. Sending to sendmail: /usr/sbin/sendmail -i -f
> [email protected] [email protected]
> postdrop: error: untrusted configuration directory name:
> /usr/local/cutedge/postfix/etc postdrop: fatal: specify
> "alternate_config_directories = /usr/local/cutedge/postfix/etc" in
> /etc/postfix/main.cf sendmail: warning: command "/usr/sbin/postdrop -r"
> exited with status 1 sendmail: fatal:
> [email protected](78): unable to
> execute /usr/sbin/postdrop -r: Unknown error: 0 spamchk: Error code 75
> running sendmail! )
>
This shows that something has messed up your configuration such
that the Postfix sendmail and postdrop programs no longer work.
In the logfile record above, there are several error messages:
postdrop: error: untrusted configuration directory name:
/usr/local/cutedge/postfix/etc
postdrop: fatal: specify "alternate_config_directories =
/usr/local/cutedge/postfix/etc" in /etc/postfix/main.cf
sendmail: warning: command "/usr/sbin/postdrop -r" exited with
status 1
sendmail: fatal: sender-localpart@sender-domain(78): unable
to execute /usr/sbin/postdrop -r: Unknown error: 0
Does the pathname "/usr/local/cutedge/postfix/etc" appear in the
spam filter script?
Wietse
