>> On Nov 18, 2015, at 10:49, Wietse Venema <wie...@porcupine.org> wrote: >> >> You need to show PIPE DAEMON logging. That will show WHY the pipe >> daemon terminated with an error, WHY you are getting "connection >> refused" errors, and so on. >> >> $ grep 'postfix/pipe.*fatal' /some/log/file >> >> All Postfix daemons log a message before terminating after error. >> >> Some LINUX systems log different errors to different files. If you >> are on such a system, you will need to search multiple files in >> order to find out what is wrong. >> >> Wietse >> >
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=<r...@cfcl.com>, 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 d3-js+bncbc5ifme6uqibbyo5wczakgqeoxgz...@googlegroups.com r...@cfcl.com 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: d3-js+bncbc5ifme6uqibbyo5wczakgqeoxgz...@googlegroups.com(78): unable to execute /usr/sbin/postdrop -r: Unknown error: 0 spamchk: Error code 75 running sendmail! ) Once the connection is refused, it's refused from that point on. There's something about 02:30 am.
