On 1/6/2020 3:16 PM, Wietse Venema wrote:
Regexps that accept exactly one the year in the Date: field will bounce some email around the end of the year, because year changes don't happen globally at the same time, and email may be in transit for up to a few days.By the end of 2019 the patterns should be: /^Date: .* 2019/ DUNNO /^Date: .* 2020/ DUNNO /^Date: .* [0-9][0-9][0-9][0-9]/ REJECT bad year in date And by the end of 2020: /^Date: .* 2020/ DUNNO /^Date: .* 2021/ DUNNO /^Date: .* [0-9][0-9][0-9][0-9]/ REJECT bad year in date This could be automated by a cronjob. Wietse
Or even easier, just delete all the Date: header based header_checks. I've found them to be false-positive prone and not very effective against spam. Then you don't have to set reminders to edit it every year, or hope your cronjob works.
Back when I used these, it mostly rejected mail from real people with a bad date on their PCs, and very little spam that wasn't caught by other rules.
I still use spamassassin to do date checks, but there it's scoring rather than pass/fail.
-- Noel Jones
