dspam broke after 4.5.7 upgrade?

[Krishopper]

Has anyone else been experiencing issues getting dspam going after upgrading to 4.5.7 ?

I changed amavisd.conf and amavisd.conf.in and uncommented dspam.. but it's not running.

I also noticed the dspam directory tree was owned by root:root, so zimbra didn't have permission to execute it.. the zmfixperms script set it to root:root (along with a bunch of other stuff?). I "chown -R zimbra:zimbra dspam-*", so at least the zimbra user can execute it now.. but it's still not running, even with the modified amavis config.

What's going on with permissions in 4.5.7, and any ideas on why dspam won't run at all?

[phoenix]

I'm running the 5.0 beta and DSPAM is running fine for me. You should never modify amavisd.conf as it will get overwritten, always make the modifications in amavisd.conf.in

I don't know why the permissions are getting set wrong but you're the second Ubuntu user to say that in the past couple of days. There is a serious bug in the Debian 3.1 kernel that causes permissions problems but I've not heard of any problem in Ubuntu until this week.

[edit] I meant to add, how are you determining that DSPAM isn't doing anything?

[Krishopper]

I haven't updated my profile yet (my bad), but this is on CentOS 5, actually.

I did make the change in amavisd.conf.in and still no-go on the dspam. I'm not sure what the deal is. I still haven't determined the cause of the issue or a solution.. getting more spam than normal though

/opt/zimbra/dspam/var/dspam/system.log hasn't been updated, and in the message headers there is no dspam information.

[phoenix]

Did you do the obvious and restart Zimbra? Have you made any changes to the spam tag/kill percentages?

[Krishopper]

Zimbra has been restarted several times since then.

Only one thing was changed in salocal.conf.in:

score DSPAM_SPAM 4.5.

When I upgraded I ran the install script to do the upgrade, changed DSPAM_SPAM to 4.5 in salocal.conf.in, and uncommented the "$dspam" line in amavisd.conf.in, and restarted Zimbra - no other changes.

I just went and looked again, and despite the fact that I chown'd to zimbra:zimbra yesterday, it was back to root:root.. I fixed permissions, restarted zimbra, ran a test message through and now it's running.

That aside, why is ${zimbra_home}/dspam being chown'd to root in zmfixperms? It is causing a "permission denied" error when amavisd tries to run it.

Is this a bug that needs to be filed?

[phoenix]

Yes, I'd file that permissions problem as a bug, check it's not in bugzilla already. Thanks.

[Krishopper]

Filed bug 20555

[hlribeiro]

I was with the same problem, it's running now for me too, thanks

Originally Posted by Krishopper

I just went and looked again, and despite the fact that I chown'd to zimbra:zimbra yesterday, it was back to root:root.

Have you found an answer for this?

[Krishopper]

No answer for it.. the dspam directory has retained the zimbra:zimbra ownership so far.. I'm just keeping an eye on the bug to see what the Zimbra guys have to say.

[hlribeiro]

Yeah, I voted for it
Please let me know if you have any updates on this, we CAN'T live without dspam here

Thanks