I am running a server with Centos 4.4, using a combo of sendmail-clamav-spamassassin for mail, which has been working quite well up until last night. Around 3:00am, all mail going to all users was being rejected by spamassassin. My ~/mail/.procmailrc is as follows:
======================== MAILDIR=$HOME/mail
# :0 H * ^X-Spam-Status:.*Yes { EXITCODE=67 :0: /dev/null } =========================
Checking yum logs, nothing that would affect SA or sendmail was updated, so I have no idea why everything would suddenly go bananas. Clamav was updated, but that was at 5:00am, and the mails were getting bounced back starting at 3:00. I am attaching 2 maillog snips showing mail from the centos list, with one going thru as expected and the other getting bounced back per my .procmailrc file. Any help appreciated.
Tom Elsesser wrote:
I am running a server with Centos 4.4, using a combo of sendmail-clamav-spamassassin for mail, which has been working quite well up until last night. Around 3:00am, all mail going to all users was being rejected by spamassassin. My ~/mail/.procmailrc is as follows: Oct 30 07:09:02 linux sendmail[20671]: k9UC8xCK020669: to=tom@acalprecision.com, delay=00:00:03, xdelay=00:00:02, mailer=local, pri=89726, dsn=5.1.1, stat=User unknown Oct 30 07:09:02 linux sendmail[20671]: k9UC8xCK020669: k9UC92CK020671: DSN: User unknown Oct 30 07:09:02 linux spamd[348]: prefork: child states: II
The key here is contained in the last three lines of the maillog. I've recently seen this behavior on one of the servers I maintain and it happened just after upgrading a CentOS 4.3 server to 4.4. The problem is the Sendmail update.
You have two choices:
1. Remove the current version of Sendmail and install the Sendmail packages that come with CentOS 4.3
2. Remove Sendmail altogether and install Postfix.
Clearly choice number one is easier and much less painful since you won't have to switch out your configuration files for SA, ClamAV or Sendmail.
Mark Weaver wrote:
Tom Elsesser wrote:
I am running a server with Centos 4.4, using a combo of sendmail-clamav-spamassassin for mail, which has been working quite well up until last night. Around 3:00am, all mail going to all users was being rejected by spamassassin. My ~/mail/.procmailrc is as follows: Oct 30 07:09:02 linux sendmail[20671]: k9UC8xCK020669: to=tom@acalprecision.com, delay=00:00:03, xdelay=00:00:02, mailer=local, pri=89726, dsn=5.1.1, stat=User unknown Oct 30 07:09:02 linux sendmail[20671]: k9UC8xCK020669: k9UC92CK020671: DSN: User unknown Oct 30 07:09:02 linux spamd[348]: prefork: child states: II
The key here is contained in the last three lines of the maillog. I've recently seen this behavior on one of the servers I maintain and it happened just after upgrading a CentOS 4.3 server to 4.4. The problem is the Sendmail update.
You have two choices:
- Remove the current version of Sendmail and install the Sendmail
packages that come with CentOS 4.3
- Remove Sendmail altogether and install Postfix.
Clearly choice number one is easier and much less painful since you won't have to switch out your configuration files for SA, ClamAV or Sendmail.
There was a thread on this too. Someone ran newaliases and it fixed the problem for him.
Feizhou wrote:
Mark Weaver wrote:
Tom Elsesser wrote:
I am running a server with Centos 4.4, using a combo of sendmail-clamav-spamassassin for mail, which has been working quite well up until last night. Around 3:00am, all mail going to all users was being rejected by spamassassin. My ~/mail/.procmailrc is as follows: Oct 30 07:09:02 linux sendmail[20671]: k9UC8xCK020669: to=tom@acalprecision.com, delay=00:00:03, xdelay=00:00:02, mailer=local, pri=89726, dsn=5.1.1, stat=User unknown Oct 30 07:09:02 linux sendmail[20671]: k9UC8xCK020669: k9UC92CK020671: DSN: User unknown Oct 30 07:09:02 linux spamd[348]: prefork: child states: II
The key here is contained in the last three lines of the maillog. I've recently seen this behavior on one of the servers I maintain and it happened just after upgrading a CentOS 4.3 server to 4.4. The problem is the Sendmail update.
You have two choices:
- Remove the current version of Sendmail and install the Sendmail
packages that come with CentOS 4.3
- Remove Sendmail altogether and install Postfix.
Clearly choice number one is easier and much less painful since you won't have to switch out your configuration files for SA, ClamAV or Sendmail.
There was a thread on this too. Someone ran newaliases and it fixed the problem for him.
wish that would have worked in my case, but it did nothing at all to fix the problem. In my case Sendmail was completely ignoring the MX record in DNS to the point of driving me mad.
Tom Elsesser wrote:
I am running a server with Centos 4.4, using a combo of sendmail-clamav-spamassassin for mail, which has been working quite well up until last night. Around 3:00am, all mail going to all users was being rejected by spamassassin. My ~/mail/.procmailrc is as follows: Oct 30 07:09:02 linux sendmail[20671]: k9UC8xCK020669: to=tom@acalprecision.com, delay=00:00:03, xdelay=00:00:02, mailer=local, pri=89726, dsn=5.1.1, stat=User unknown Oct 30 07:09:02 linux sendmail[20671]: k9UC8xCK020669: k9UC92CK020671: DSN: User unknown Oct 30 07:09:02 linux spamd[348]: prefork: child states: II
The key here is contained in the last three lines of the maillog. I've recently seen this behavior on one of the servers I maintain and it happened just after upgrading a CentOS 4.3 server to 4.4. The problem is the Sendmail update.
You have two choices:
- Remove the current version of Sendmail and install the Sendmail
packages that come with CentOS 4.3
- Remove Sendmail altogether and install Postfix.
Clearly choice number one is easier and much less painful since you won't have to switch out your configuration files for SA, ClamAV or Sendmail.
There was a thread on this too. Someone ran newaliases and it fixed the problem for him. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Agree, it sounds more like an aliases issue.
Mark Weaver wrote:
The key here is contained in the last three lines of the maillog. I've recently seen this behavior on one of the servers I maintain and it happened just after upgrading a CentOS 4.3 server to 4.4. The problem is the Sendmail update.
I haven't updated sendmail since I made the switch to 4.4 in what...early September? It has been running happily since then. If I stop the spamassassin service, the mails come as expected.
Clearly choice number one is easier and much less painful since you won't have to switch out your configuration files for SA, ClamAV or Sendmail.
Thanks for the advice, and that's probably what I'll do, but I don't know why it just started last night.