Results 1 to 7 of 7

Thread: SpamAssassin Bayes Check Disappeared After 4.0.3-to-4.5.2 Upgrade

  1. #1
    Justin is offline Member
    Join Date
    Dec 2005
    Posts
    10
    Rep Power
    9

    Arrow SpamAssassin Bayes Check Disappeared After 4.0.3-to-4.5.2 Upgrade

    Hi folks. Last night I upgraded our Zimbra OS edition from 4.0.3 to 4.5.2 on Mac OS X 10.4.8 (x86). The upgrade seems to have gone smoothly, except for two issues:

    1. The Bayes and DSpam checks do not appear in the X-Spam-Status header (they did before the upgrade). The disabling of DSpam was mentioned in the upgrade docs, so uncommenting the relevant line in avamisd.conf.in successfully re-enabled DSpam. However, I have no idea why the Bayes_99, Bayes_50, etc, are not showing up in the headers. A quick perusal of /opt/zimbra/amavisd-new-2.4.3/.spamassassin shows that all the bayes_* database files have the exact same timestamp and filesize as the ones in the 4.0.3 backup directory. (The only difference is the presence of an "init" file in the 4.0.3 directory that does not appear in the 4.5.2 directory.) So it would seem as though the databases were migrated successfully, and yet the Bayes headers do not show up. Does anybody have any suggestions as to how to re-activate the Bayes check?

    2. It seems the upgrade process did not successfully find the admin account at "admin@mydomain.com" and instead automatically created one at "admin@mail.mydomain.com". (The fully qualified domain name of the box is mail.mydomain.com, but of course in our case all mail is sent/received from "address@mydomain.com".) Interestingly, when upgrading from 4.0.2 to 4.0.3, a very similar thing happened whereby the system decided that "admin@myhostname.local" was the admin account. There are a bunch of deferred messages with "admin@myhostname.local" as the sender/receiver (this was the case prior to the 4.5.2 upgrade). Post-4.5.2-upgrade, if I look in amavisd.conf, I see that all notification sender/recipients are currently set to "admin@mail.mydomain.com", which clearly should not be the case. Does anyone have any suggestions as to how I can rectify this and direct Zimbra to the one and only true admin account on the system (i.e., "admin@mydomain.com"), for notifications as well as everything else?

    Any and all suggestions would be greatly appreciated!

    Justin

  2. #2
    JHill is offline Active Member
    Join Date
    Jun 2006
    Posts
    28
    Rep Power
    9

    Default

    I'm experiencing #1, but upgraded from 4.5.1.

  3. #3
    Justin is offline Member
    Join Date
    Dec 2005
    Posts
    10
    Rep Power
    9

    Default Anybody at Zimbra out there? ;)

    Here's one clue... The output of /opt/zimbra/log/spamtrain.log contains the following:

    Code:
    bayes: cannot open bayes databases /opt/zimbra/amavisd/.spamassassin/bayes_* R/O:
    tie failed: No such file or directory
    bayes: cannot open bayes databases /opt/zimbra/amavisd/.spamassassin/bayes_* R/W:
    tie failed: No such file or directory
    ERROR: the Bayes learn function returned an error, please re-run with -D for more information
    However, the bayes_* files are there, despite the assertion above:

    Code:
    $ ls -la /opt/zimbra/amavisd/.spamassassin
    drwxr-xr-x   6 zimbra  zimbra      204 Feb 27 05:18 .
    drwxr-xr-x   9 zimbra  zimbra      306 Feb 26 10:19 ..
    -rw-------   1 zimbra  zimbra  5279744 Feb 25 16:57 auto-whitelist
    -rw-------   1 zimbra  zimbra    50952 Feb 25 16:50 bayes_journal
    -rw-------   1 zimbra  zimbra  2580480 Feb 25 16:50 bayes_seen
    -rw-------   1 zimbra  zimbra  5251072 Feb 25 16:50 bayes_toks
    I'm stumped. Anybody have any suggestions?

  4. #4
    chh
    chh is offline Advanced Member
    Join Date
    May 2006
    Posts
    196
    Rep Power
    9

    Default

    Had this at home once. The only thing I can tell you, is that it is not an issue with the credentials.

  5. #5
    JHill is offline Active Member
    Join Date
    Jun 2006
    Posts
    28
    Rep Power
    9

    Default

    It looks like my issues are unrelated to the bayesian checks. I had a secondary mail server that was being seen as trusted, I added a value for ZimbraMtaMyNetworks excluding its IP address and things seem to be better.

  6. #6
    Justin is offline Member
    Join Date
    Dec 2005
    Posts
    10
    Rep Power
    9

    Default Getting desperate

    Might someone from the Zimbra team have any suggestions for troubleshooting the aforementioned problems?

  7. #7
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,499
    Rep Power
    56

    Default

    The problem with the bayes db going missing was bug 13947 and was fixed in 4.5.1 Have a look at the bug report and see if it applies to you, if it does then I guess you'd better reopen that bug or create a new one.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Upgrade from 3.1.3 to 4.0.3
    By rrojas in forum Installation
    Replies: 4
    Last Post: 05-22-2007, 08:45 AM
  2. Questions for Upgrade from 4.05 to 4.5.2
    By Rick Baker in forum Installation
    Replies: 6
    Last Post: 02-24-2007, 10:42 AM
  3. 4.0.3 -> 4.5.1 upgrade
    By Storm16 in forum Installation
    Replies: 1
    Last Post: 02-11-2007, 09:44 PM
  4. Replies: 9
    Last Post: 01-26-2007, 06:31 AM
  5. Upgrade to 4.0.3 on Suse 9.3
    By winne27 in forum Migration
    Replies: 3
    Last Post: 10-27-2006, 10:30 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •