A special treat for the ten year anniversary of Y2K...

SpamAssassin gives any message sent in 2010 a default score of 3.2 because that date "is grossly in the future." But it gets better: they discovered and "fixed" this in June 2009... but never bothered to push out a release. Because being fixed in CVS is good enough, right? That's the Linux way.

You want "score FH_DATE_PAST_20XX 0".

Tags: , , , ,

18 Responses:

  1. blaisepascal says:

    Why are they using a fixed date or string pattern to determine if a message is "grossly in the future"? Is there a reasonable explanation I don't see?

  2. genehack.org says:

    FWIW, if you run 'sa-update', it should pull down a new set of rules with a fix for this. That may be better than zero-ing out the rule.

    That said, yeah, fixing this in advance would have been nice.

  3. duskwuff says:

    Alternatively, header FH_DATE_PAST_20XX Date =~ /20[2-9][0-9]/ [if-unset: 2006] also "solves the problem".

    • pushupstairs says:

      I just changed mine to that until a real fix comes out. I also changed the describe line for it to "The date may or may not be grossly in the future. There is a possibility the date may be in the past." for increased accuracy.

  4. Finally! We live in the future now!

    • ywwg says:

      Not just in the future, *grossly* in the future. I think that just about sums up these grim meathook times.

  5. captain18 says:

    I had just noticed that everything non-local and non-whitelisted was suddenly appearing in my spam folder.

    Thank you for sharing this!

  6. jwz says:

    Also I note that RCVD_IN_BL_SPAMCOP_NET is now listing many (but not all) of Facebook's outgoing mail servers on the blacklist. Thanks, guys, that's really helpful.

  7. emtel says:

    This kind of bullshit is exactly why I stopped running my own mail server and sold my soul to the Global Electronic Brain.