Examing SA 2.55's spam-report on a test-message, I saw the following:
--------------------------
X-Spam-Status: No, hits=0.5 required=7.5
tests=INVALID_MSGID
version=2.55
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
--------------------------
The "X-Spam-Level" header has no value! Not to be fuzzy, but is that not
illegal?
To be precise, "X-Spam-Level" contains a space as field-body (intentional?).
And I believe the new RFC 2822 allows this. That is, RFC 2822 no longer
requires a space between the ":" and the field-body, so that the space after
the colon could be interpreted as a valid field-body. But is that not
stretching things a bit? I bet you 999 to 1 that most software will split
header lines along the following scheme:
($field_name, $field_body) = split (/: */, $line, 2);
And thus potentially mark the body-field as absent.
Is it not possibe to simply ommit the 'X-Spam-Level' header when zero? Or to
give it a string value, like "below threshold"?
- Mark
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
