[SOLVED] All mail deferred after upgrade

[shnook]

Hi,

I just completed an upgrade from 6.0.1 to 6.0.2 (OS Edition, Ubuntu 8.04).
All seemed to go well, however, after upgrade all mail is sitting permanently in the queue as deferred.

Looking at the logs, it is showing the issue as an amavis-dspam one -
Oct 25 10:44:29 s11 postfix/smtp[4377]: A9F3644E03D: to=<mail@***.com>, relay=127.0.0.1[127.0.0.1]:10024, delay=5.7, delays=0.01/0/0/5.7, dsn=4.5.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.5.0 Error in processing, id=04925-02, spam_scan FAILED: DSPAM failed: DSPAM: error running program /opt/zimbra/dspam/bin/dspam: exit 6 at (eval 87) line 109, <GEN30> line 163. (in reply to end of DATA command))


Anyone seeing anything similar - I tried to disable dspam checking, that did not seem to help.
Any Suggestions?

Thanks.

[phoenix]

Originally Posted by shnook

Anyone seeing anything similar - I tried to disable dspam checking, that did not seem to help.

It failed because DSPAM isn't running, you need to enable it. You should also check that the owner/group on the DSAPM folder is zimbra:zimbra then restart Zimbra.

[shnook]

Thanks for the fast reply.

dspam was set right, there was a permissions issue with the /opt/zimbra/dspam/bin directory.

they were all owned by root, I switched them all to zimbra:zimbra
(chown zimbra:zimbra /opt/zimbra/dspam/bin/*)

[lanstar]

For what its worth, I had the exact same problem with the exact same solution after upgrading to 6.0.2_GA from 6.0.1_GA (32 bit RedHat RPM distribution). Specifically /opt/zimbra/dspam-3.8.0/bin/dspam is owned by root:root with permissions set to 510 (r-x--x---). All the other executables in that directory have 755 permissions which will let them run irrespective of owner. However, I did as suggested and made zimbra:zimbra the owner of the /opt/zimbra/dspam-3.8.0/bin directory and all its contents.

shnook, I see you had the problem on Ubuntu (and I had it under 32 bit RedHat). I wonder if there's a bug in the common installation script that causes permissions (or ownership) to get set incorrectly... but only some of the time? I'd think if it happened often, there would have been a lot more noise in here about it.

Also for what its worth, I have another server that uses the 64 bit Redhat version that did *not* experience this issue after its upgrade. It too was upgraded from 6.0.1_GA to 6.0.2_GA.