Bug#362913: spamassassin: false positive on DATE_IN_FUTURE_06_12 due to Resent-Date: header added by spohr.

[Jamie L. Penman-Smithson]

On 16 Apr 2006, at 15:39, Andreas Metzler wrote:

On 2006-04-16 "Jamie L. Penman-Smithson" <[EMAIL PROTECTED]> wrote:

[...]

The Date used in the Resent-Date header is not RFC compliant:

<snip>

Specifically "the zone MUST be within the range -9959 through +9959".
It should be:
Resent-Date: Sun, 16 Apr 2006 12:33:07 +0000

Making it RFC compliant causes DATE_IN_FUTURE to not be triggered:

I see, thanks for the diagnosis.

SA seems to be too strict, it does not accept the old obs-zone
syntax. Fixing the header to be correct obs-zone syntax
Resent-Date: Sun, 16 Apr 2006 09:48:08 GMT
is not enough.

Chapter 4 of RFC 2822 lists the obsolete format in detail:
<http://www.zvon.org/tmRFC/RFC2822/Output/chapter4.html>

--
-Jamie L. Penman-Smithson <[EMAIL PROTECTED]>
 t: +44 1273 424795; f: +44 1273 424795
 PGP: C0A7 955E EED6 A309 23D7 863B C76A 26A3 F0DC FCA8
 never send mail to: [EMAIL PROTECTED]

This Date should never have been generated in the first place, however, you're right in saying that SA should still parse it as equivalent to +0000 since the RFC states that it MUST parse the obsolete format.

PGP.sig
Description: This is a digitally signed message part