You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2006/01/05 14:21:31 UTC

[Bug 4754] Mail sent during a leap second

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4754





------- Additional Comments From bas@debian.org  2006-01-05 14:21 -------
There seem to be two testing rules (T_INVALID_DATE and T_INVALID_DATE2) already
that take the leap second into account correctly.  
However, both those test rules as well as the one currently in use seem to relax
the RFC requirements a bit: all of them allow for am/pm specifiers and for a
single-digit hour, which aren't allowed according to the rfc.  Maybe this could
also be checked for?  For example (based on T_INVALID_DATE):

header T_INVALID_DATE3      Date !~
/^\s*(?:(?i:Mon|Tue|Wed|Thu|Fri|Sat|Sun),\s+)?[0-3\s]?[0-9]\s+(?i:Jan|Feb|Ma[ry]|Apr|Ju[nl]|Aug|Sep|Oct|Nov|Dec)\s+(?:[12][901])?[0-9]{2}\s+(?:[01][0-9]|2[0-3])\:[0-5][0-9](?:\:(?:[0-5][0-9]|60))?\s+(?:[+-][0-9]{4}|UT|[A-Z]{2,3}T)(?:\s+\(.*\))?\s*$/




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.