From: Russ Allbery (rra@stanford.edu)
Date: Mon May 19 2003 - 23:26:37 CDT
Bruce Lilly <blilly@erols.com> writes:
> 2.3 refers to message bodies, not header fields. In any event, that is
> trivially handled as:
> body = *(1*998text CRLF) [1*998text]
> (the last part accommodates RFC 2046 multipart messages with an
> epilogue, which does not necessarily end with CRLF)
I'm not sure what you all are discussing exactly, but note that all
messages transferred via NNTP are *required* to end in CRLF. There's no
way to transmit a message via NNTP that does not.
How does SMTP handle that issue? Is the CRLF before the period in SMTP
not considered part of the message?
> So I ask again; what component needs to parse From header fields and
> fails to do so when the field body starts on a continuation line?
INN will reject any message where a required header has no non-whitespace
content on the first line. I personally consider this to be a bug in
INN's header parser, but it's a very long-standing one, and even if
eventually fixed (which will be somewhat difficult), there will be a lot
of servers out there for quite a while with this limitation.
-- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>