SpamAssassin 2010 Bug
SEWilco writes "You might want to check your spam folder, as SpamAssassin has a rule which is tending to mark email sent in 2010 as spam. There is some discussion in a bug report. The SpamAssassin Wiki FH_DATE_PAST_20XX page doesn't have discussion, but it was updated today with a different date rule."
Instead of having one millenium bug, letting it do it's thing and get it over with we get similar bugs every year. The 2007 zune issue, the impending 2038 issue and this. Of course many more similar bugs that don't deserve their own slashdot article. If they had decided to start using 64-bit time on the 1st of January, 1970 none of these problems would have happened
Hey! Nice to see open source software gets fixed so ultra fast! :P
To be fair though, at least they released it the day it broke things, why didn't they release it by yesterday? Then the default cron job would have picked it up on most servers and nobody would have noticed.
Security is mostly a superstition... Avoiding danger is no safer in the long run than outright exposure. - Helen Keller
Exactly. This is the right "fix" right now - the bug is out there causing real problems, and the fix (while definitely a filthy hack) is well-understood and can be pushed out immediately. If the same thing were to happen ten years from now (or the threshold quietly got pushed back to 2030), that would be nothing short of negligent.
Your solution doesn't work.
It fails on new years eve if someone is in a different time zone or if their clock is slightly off.
I'd suggest that any message sent more than seven (pick your favorite number) days in the future is spam.
Why didn't they release this when it was fixed.
First, it learned that 90% of mail is spam. Then, it got lazy. Now, it just stamps everything.
APK quotes people (including myself) without context and should not be trusted. Just thought you should know.