Enabling dspam, razor, pyzor etc

[ianw1974]

I'm having problems enabling dspam, razor and pyzor in Zimbra 6.0.1. It just doesn't seem to work.

I've done all the stuff required for razor and pyzor, and they are enabled in the spamassassin v310.pre file.

I've enabled dspam by editing the amavisd.conf.in like I did in v5.x of Zimbra but no incoming email is being marked with header info for either dspam, razor or pyzor.

I edited local.cf to put scoring information for dspam. I also note this post when I searched:

ZCS 6 (amavisd 2.6.3+ and DSPAM)

but the additional config doesn't make any sense to me. Where does it go, and why the change in the first place? Why not keep it simple like it was in v5.x? There doesn't seem to be any documented information on enabling these features.

Any ideas on how I can get dspam working again? As well as razor and pyzor.

[ianw1974]

Nobody got any ideas?!?

[uxbod]

Do you have the spamassassin binary on your server ? If so you could do

su - zimbra
spamassassin -C /opt/zimbra/conf -D --lint > /tmp/sadebug 2>&1

to make sure no errors.

[genzodiwa]

Please see
MTA Functionality

That is only for dspam.

Still trying to sort out razor & pyzor myself.

[genzodiwa]

there is a line in
/opt/zimbra/conf/spamassassin/25_razor2.cf
that says 'ifplugin Mail::SpamAssassin::Plugin::Razor2'
so after following the instructions at
Improving Anti-spam system - Zimbra :: Wiki
and restarting the required services, it should hopefully work properly (without having to edit the
/opt/zimbra/conf/spamassassin/local.cf
file

[uxbod]

Indeed ... you could create you own .cf under /opt/zimbra/conf/spamassassin and that will get called via Amavisd. That means you can have you own configs without affecting the vanilla ZCS ones.

[ianw1974]

I don't have any problems with amavisd, spamassassin. dspam is enabled as per the documentation, but it doesn't work.

Email headers are not being scored, the amavisd config has not been edited other than enabling dspam. Prior to upgrade to 6.0.1 it worked.

[ianw1974]

Never mind, after upgrade to 6.0.2 it's working again.