jdow wrote:
> > 2.2. Header Fields
> > Header fields are lines composed of a field name, followed by a
> > colon (":"), followed by a field body, and terminated by CRLF.
> > A field name MUST be composed of printable US-ASCII characters
> > (i.e., characters that have values between 33 and 126,
> ^^ NOTE
>
> > inclusive), except colon. A field body may be composed of any
> > US-ASCII characters, except for CR and LF. [...]
>
> NOTE: Character 32 is space. Character 33 is !. The subject does NOT
> begin with the space character. It begins with the first character
> past the space.
Perhaps you misread the RFC excerpt a bit? only the field name (!)
must be composed of characters between 33 and 126. The definition
subject = "Subject:" unstructured CRLF
implies that, as far as I understand, the field body starts with the
character immediately after the colon.
> Now, as to how SpamAssassin parses the Subject field is open for
> question. It appears a lot of rules seem to start presuming zero
> or more blank characters followed by the real search string.
As I wrote before: I believe that many software products dealing
with email assume that the field body starts with the first non-
whitespace character after zero or more whitespaces, or that they
make use of functions like trim() to remove any leading/trailing
whitespaces as they see fit, i.e. when storing or displaying
messages. I don't know if checking for "surplus" whitespaces in
field bodies has a realistic chance of success.
--
Mit freundlichen Grüßen / Sincerely
Dipl. Inform. Ralph Seichter
