Topic: failed spamassassin install

[Randall Perry]

HELP! I just tried to configure spamassassin for one of my e-smith servers and now no mail gets through!

Months ago I had setup clam AV and amavis to scan, but did not use the contributed RPM (which, it worked fine up until today).

I get an error that I see under
/var/log/smtpfront-qmail/current
"Script is not setuid/setgid in suidperl"

what do I do now?

I edited back the /usr/sbin/qmail-queue.amavis
to be the original.

Any ideas??

[Randall Perry]

I reinstalled clamav and amavis and then the error goes away.
this shows up
@400000003f5e1df22521f564 tcpserver: status: 1/40
@400000003f5e1df22524fad4 tcpserver: pid 3228 from 63.236.75.213
@400000003f5e1df227f7c214 tcpserver: ok 3228 0:208.16.129.98:25 mx14.blastdirect.com:63.236.75.213::2870
@400000003f5e1df22c47af8c smtpfront-qmail[3228]: MAIL FROM:
@400000003f5e1df22e55a414 smtpfront-qmail[3228]: RCPT TO:
@400000003f5e1df2306de16c smtpfront-qmail[3228]: bytes in: 95 bytes out: 105
@400000003f5e1df23435517c tcpserver: end 3228 status 13
@400000003f5e1df234356504 tcpserver: status: 0/40

but still no mail comes through.

[Ed]

Ouch

[Randall Perry]

Ok.  I  loaded a fresh 5.6 and reloaded from backup.
I am performing the autopsy now on the failed box.
I will document what I find and then write a procedure
for adding spamassassin to a modified esmith box
without jacking up your smtp server.

[Randall Perry]

I did a custom setup of antivirus scanning and had modified the qmail config and the ownership of the antivirus logs and executeables.

The spamassassin install needed to have qmail as the owner and group for permissions to run.

You do not get into this mess when using the amavis-clam RPMs from contrib.org (which I didn't see around when I initially set this all up on 5.1.2 and then did same to my 5.6 box)

Everything is running fine now.