Page 1 of 3 123 LastLast
Results 1 to 10 of 30

Thread: [SOLVED] FH_DATE_PAST_20XX - Spamassassin bug - incorrect tagging from Jan 1, 2010 on

  1. #1
    Yann2 is offline Active Member
    Join Date
    May 2007
    Posts
    43
    Rep Power
    8

    Default [SOLVED] FH_DATE_PAST_20XX - Spamassassin bug - incorrect tagging from Jan 1, 2010 on

    Hello, it seems there is a rule in Spamassassin with a weight of 2 affecting all emails with a sent date of 2010 and later.

    More information: Rules/FH_DATE_PAST_20XX - Spamassassin Wiki

    Seems my Zimbra spammassassin had this rule, I applied the proposed configuration workaround.

  2. #2
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,473
    Rep Power
    56

    Default

    Quote Originally Posted by Yann2 View Post
    Hello, it seems there is a rule in Spamassassin with a weight of 2 affecting all emails with a sent date of 2010 and later.

    More information: Rules/FH_DATE_PAST_20XX - Spamassassin Wiki

    Seems my Zimbra spammassassin had this rule, I applied the proposed configuration workaround.
    Can you file a bug report in bugzilla?
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Yann2 is offline Active Member
    Join Date
    May 2007
    Posts
    43
    Rep Power
    8

  4. #4
    phoenix is online now Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,473
    Rep Power
    56

    Default

    Thanks very much and Happy New Year to you.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #5
    Yann2 is offline Active Member
    Join Date
    May 2007
    Posts
    43
    Rep Power
    8

    Default

    Thanks, to you and to the whole Zimbra team too

  6. #6
    WolfyPDX is offline Intermediate Member
    Join Date
    Aug 2009
    Posts
    24
    Rep Power
    5

    Default [SOLVED] Serious SpamAssassin Bug

    There's a serious bug in SpamAssassin that is rewarding 3+ points to every email starting today (01/01/2010). The problem is the rule FH_DATE_PAST_20XX which is intended to flag mail from the future as spam. This is likely to create a lot of false positives in mail received on Zimbra systems. The short term solution is to edit /opt/zimbra/conf/spamassassin/50_scores.cf and 0 out the FH_DATE_PAST_20XX rule, then restart.

  7. #7
    WolfyPDX is offline Intermediate Member
    Join Date
    Aug 2009
    Posts
    24
    Rep Power
    5

    Default

    Ah, I see somebody else has reported this too.

  8. #8
    deepblue is offline Partner (VAR/HSP)
    Join Date
    Jul 2006
    Location
    Stuttgart / Germany
    Posts
    223
    Rep Power
    9

    Default

    Hi all,

    I stumbled upon the same thing. In Zimbra 6.0.3 it is enough to put
    Code:
    score FH_DATE_PAST_20XX 0.0
    in salocal.cf(.in) and restart amavis. But this does not do the job in Zimbra 5.0.x.

    I had to edit /opt/zimbra/conf/spamassassin/72_active.cf and I modified line 543 to be:

    Code:
    header   FH_DATE_PAST_20XX      Date =~ /20[2-9][0-9]/ [if-unset: 2006]
    Regards
    Thomas

  9. #9
    raj's Avatar
    raj
    raj is offline Moderator
    Join Date
    Oct 2005
    Location
    USA, Canada and India
    Posts
    777
    Rep Power
    10

    Default

    ok spent few hours updating all zimbra nodes

    orignal discussion for this bug is at
    https://issues.apache.org/SpamAssass...ug.cgi?id=6269

    * it mentiones that if you edit by hand as work-around it will not stick if you run sa-udpate, but zimbra dont package sa-update too YET so i guess it should be ok till new version is released

    Raj
    i2k2 Networks
    Dedicated & Shared Zimbra Hosting Provider

  10. #10
    ajayrockrock is offline Active Member
    Join Date
    May 2007
    Location
    Riverside, CA
    Posts
    27
    Rep Power
    8

    Default

    Quote Originally Posted by deepblue View Post
    I stumbled upon the same thing. In Zimbra 6.0.3 it is enough to put
    Code:
    score FH_DATE_PAST_20XX 0.0
    in salocal.cf(.in) and restart amavis.
    restarting amavis with zmamavisctl stop/start, didn't do the trick for me. I had to shut it down (zmcontrol stop) and bring it back up for zimbra to rewrite the config files. Once I did the full restart, the conf/salocal.cf file was rewritten with the new rule.

Page 1 of 3 123 LastLast

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. [SOLVED] Spamassassin Questions
    By GCamp in forum Administrators
    Replies: 6
    Last Post: 05-02-2009, 10:49 AM
  2. Replies: 30
    Last Post: 01-13-2009, 08:00 AM
  3. Replies: 2
    Last Post: 10-23-2008, 09:50 AM
  4. FC4 Test install getting SU: Incorrect Password
    By bbepristis in forum Installation
    Replies: 16
    Last Post: 08-11-2006, 10:07 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
  •