Scalix Forums

Hello,

Scalix 11.4
Spamassassin 3.x

Following the Wiki, I think i finally have Spamassassin properly configured to scan properly, but can someone first verify the following mail log output verifies Spamassassin is running somewhow?

May 27 23:06:17 mailserver sendmail[5224]: n4S66G7k005224: from=<Lproserpine@lasvegassun.com>, size=1048, class=0, nrcpts=1, msgid=<2IX860EJXVWDA996@nellisrac.org>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
May 27 23:06:19 mailserver sendmail[5230]: n4S66G7k005224: to=<tonysu@su-networking.com>, delay=00:00:03, xdelay=00:00:01, mailer=scalix_mime, pri=121048, relay=mailserver, dsn=2.0.0, stat=Sent (Ok)
May 27 23:07:25 mailserver sendmail[5333]: starting daemon (8.14.3): SMTP+queueing@00:30:00
May 27 23:07:25 mailserver sendmail-client[5338]: starting daemon (8.14.3): persistent-queueing@00:01:00
May 27 23:08:33 mailserver clamd[2527]: SelfCheck: Database status OK.

I have run spamassassin --lint which does not return any errors.

But, the subject lines are not being re-written. The contribution by Mark Nikkels at the end of the Scalix Spamassassin Wiki at http://www.scalix.com/wiki/index.php?title=HowTos/SpamAssassin apparently only applies to "older" versions of Spamassassin (approx 2.4/2.6 and earlier). In Spamassassin 3.x the entries suggested by Mark Nikkels are supposed to be replaced with

rewrite_header Subject ****SPAM(_SCORE_)****

Up to this point I have not configured Bayes at all, but assume that even so I should already be able to see re-written subject lines... Or, maybe with Spamassassin the subject line is no longer modified and there is only a new hidden header parameter?

At the moment, Scalix is otherwise working without apparent problems but of course I'm seeing everything including spam.

TIA.

What platform are you running? suse or centos or other?

is a spamassassin daemon running? (in centos "service spamassassin status")

is a spamass-milter daemon running? (in centos "service spamass-milter status")

did you use a sendmail.mc to input the spamassassin mail filter? what lines did you put in the sendmail.mc file to tell sendmail to hand off to spamass-milter/spamassassin?

And have you got SMTPFILTER=TRUE in /var/opt/scalix/??/s/sys/smtpd.cfg so that scalix knows to hand off to sendmail for scanning?

Hello Les,
Thx for responding, sorry for not including basic info in my original post... (responses inline)

les wrote:What platform are you running? suse or centos or other?
<Tony> Am deployed on OpenSuSE 11.1 </Tony>

is a spamassassin daemon running? (in centos "service spamassassin status")
<Tony> Yes </Tony>

is a spamass-milter daemon running? (in centos "service spamass-milter status")

<Tony> Yes </Tony>

did you use a sendmail.mc to input the spamassassin mail filter? what lines did you put in the sendmail.mc file to tell sendmail to hand off to spamass-milter/spamassassin?

<Tony> Yes, and made the appropriate entry </Tony>

And have you got SMTPFILTER=TRUE in /var/opt/scalix/??/s/sys/smtpd.cfg so that scalix knows to hand off to sendmail for scanning?

<Tony> Yes. Am I to understand that this in particular needs to be working to even get the log readout I posted? </Tony>

I believe you need to edit your /etc/default/spamass-milter file and change
this
OPTIONS="-u spamass-milter -i 127.0.0.1"

to this
OPTIONS="-u spamass-milter "

and restart services

wheelert wrote:I believe you need to edit your /etc/default/spamass-milter file and change
this
OPTIONS="-u spamass-milter -i 127.0.0.1"

to this
OPTIONS="-u spamass-milter "

and restart services

Thx for the suggestion, but I think according to the spamassassin wiki I referenced in the original post, the spamass-milter file only exists and is configurable for Scalix 10.x.

I'm running Scalix 11.x so I followed the instructions which describe the alternate configuration that describes disabling sendmail management by command in the file /etc/sysconfig/mail, then modifying linux.mc, then regenerating sendmail.cf.

Also, the net result appears to be that although in CentOS/Fedora the spamassassin and spamass-milter services are separate, on SuSE both are supposed to be tightly integrated and managed with the spamd service.

I've gone over the steps carefully and don't think I've missed anything... Which is why I was hoping someone might be able to suggest how to really determine whether spamassassin really is scanning and whether the logfile output I originally quoted might look "right" to someone who knows what to look for.

Thx again,
Tony

tonysu wrote:

wheelert wrote:I believe you need to edit your /etc/default/spamass-milter file and change
this
OPTIONS="-u spamass-milter -i 127.0.0.1"

to this
OPTIONS="-u spamass-milter "

and restart services

Thx for the suggestion, but I think according to the spamassassin wiki I referenced in the original post, the spamass-milter file only exists and is configurable for Scalix 10.x.

I'm running Scalix 11.x so I followed the instructions which describe the alternate configuration that describes disabling sendmail management by command in the file /etc/sysconfig/mail, then modifying linux.mc, then regenerating sendmail.cf.

Also, the net result appears to be that although in CentOS/Fedora the spamassassin and spamass-milter services are separate, on SuSE both are supposed to be tightly integrated and managed with the spamd service.

I've gone over the steps carefully and don't think I've missed anything... Which is why I was hoping someone might be able to suggest how to really determine whether spamassassin really is scanning and whether the logfile output I originally quoted might look "right" to someone who knows what to look for.

Thx again,
Tony

The original logs you posted dont make any mention of spamassassin at all, so its likely that sendmail is not calling spamass-milter to run through spamassassin.

I'm not familiar with the suse environment, so i'm not gonna be too much help to you. In CentOS/Redhat its a very straightforward setup.

Thx for the help guys...

Unless the original Wiki poster can shed some light, I'll start trying to get answers elsewhere, too.

Tony

For anyone following in my footsteps (configuring Spamassassin on OpenSuSE <any version>),

I'm pretty much going to abandon this path, it seems that SuSE has been favoring Postfix in favor of Sendmail for quite some time now (I've generally installed Postfix myself everywhere else and wouldn't be using Sendmail now except for that this what Scalix sets up).

Instead I'm going to explore the Amavisd option instead

http://www.scalix.com/wiki/index.php?title=Scalix/Sendmail_%26_Amavisd-New_HOWTO

The SuSE community fully supports the use of amavisd no matter what MTA is used.

And I suppose since I've likely mucked up my existing 11.4.2, instead of undoing all the configurations I made I'll likely coonsider upgrading to the latest version of Scalix instead.

Tony