https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5996
--- Comment #4 from Sidney Markowitz <[email protected]> 2009-02-03 15:08:11 PST --- The code for the date in future rules looks at the Resent-Date or Date header and the various times in the Received header, looking for the smallest difference other than a final Received header with an identical time. As I recall, a bad date with no time zone is parsed as UTC+0 for the purpose of this rule. It should have nothing to do with time zone setting on the SpamAssassin server, other than if it is also a mail server that affects the time stamps in Received headers. This is very strange. If SpamAssassin is not seeing any Received headers, that would trigger a different rule, not DATE_IN_FUTURE_96_XX. This could only happen if SpamAssassin incorrectly parsed the date in one or more of the Received headers or Date header or if one or more of those headers were mangled before the message was delivered to SpamAssassin. The rule trigger is independent of the current date, being based just on the headers. When you say this is intermittent, do you mean that when you send the same message back through SpamAssassin through the same milter the rule doesn't trigger? Or does it consistently happen with the same message? If the latter, could you run it through with the debug switch on and attach the debugging output here? -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
