Comments on: SpamAssassin Problems

By: The Proverbial Barry

The Proverbial Barry — Mon, 04 Jan 2010 20:44:33 +0000

Amie- they were not YOUR names in the first place.

By: J.D. Falk

J.D. Falk — Mon, 04 Jan 2010 20:40:56 +0000

It’s extremely unlikely that an ISP would reject (5xx reply, sometimes called a “hard bounce”) messages based on a single SpamAssassin rule. More likely, the message had other spam-like characteristics as well.

(Actually, it’s rare that they’ll reject based on SpamAssassin at all. SA is more commonly used as a filter, after the message was accepted.)

By: SpamAssassin Users: 2010 Emails May be Flagged | MailerMailer Blog | In The Box

Mon, 04 Jan 2010 19:58:25 +0000

[...] who are using SpamAssassin as their email filter. In a recent post on email delivery blog Word to the Wise, Steve Atkins mentioned the problem and the quick fix, which takes about 10 seconds for an email [...]

By: Amie

Amie — Mon, 04 Jan 2010 14:52:23 +0000

I lost almost 100 names due to this bug. Email addresses from certain ISPs were “hard bounced” and I have to go in and hand delete them all from the cleaned list so that they can be resubscribed.

By: SpamAssassin Y2K10 Problem | Email Marketing

SpamAssassin Y2K10 Problem | Email Marketing — Sun, 03 Jan 2010 01:06:14 +0000

[...] Horrible title, I know. Anyway, if you’re seeing your emails get junked more often than usual this year (perhaps in your inbox inspection reports), it’s probably because of this date issue that Laura Atkins talks about here. [...]

By: Jared

Jared — Sat, 02 Jan 2010 20:58:22 +0000

Wow! A ton of email marketing is going to get blocked because of this. I’m sure some of those emails could be annoying but on the other hand there will probably be important things that will get blocked as well. Hopefully this get’s fixed asap.

By: SpamAssassin Y2K10 Problem | MailChimp Email Marketing Blog

SpamAssassin Y2K10 Problem | MailChimp Email Marketing Blog — Sat, 02 Jan 2010 16:46:00 +0000

[...] than usual this year (perhaps in your inbox inspection reports), it’s probably because of this date issue that Laura Atkins talks about here. Spread the monkey [...]

By: John Levine

John Levine — Sat, 02 Jan 2010 04:14:19 +0000

If you can edit the main spamassassin config files, this bug takes about 10 seconds to fix. Find the file 72_active.cf which is usually stored in
/usr/local/share/spamassassin/72_active.cf, find the line that starts “header FH_DATE_PAST_20XX”, and change [1-9] to [2-9]. If you use compiled patterns, run sa-compile, if you use spamd, restart it.

This bug is annoying, but it sure is easy to fix.

By: Mike

Mike — Fri, 01 Jan 2010 16:42:31 +0000

This issue has been known about for over a year and a fix was written about six months ago. It just hasn’t been rolled out properly. See https://secure.grepular.com/blog/index.php/2010/01/01/spamassassin-2010-bug/ for more information about how this all went down.