From: Dirk Nimmich (nimmich@muenster.de)
Date: Mon Apr 21 2003 - 14:57:58 CDT
Bruce Lilly wrote:
> Charles Lindsey wrote:
> >The following summary shows all the differences between the usages in
> >RFC 2822 and in Usefor, as they stand in the current draft.
> [...]
> >1.5 Body lines are restricted to 998 characters plus CRLF (as in RFC
^^^^^^^^^^
> > 2822). However, all agents SHOULD, and relaying agents MUST, process
> > lines of arbitrary length.
>
> MIME requires that any header line containing an encoded-word be no longer
^^^^^^^^^^^
> than 76 octets.
Apart from the difference marked above it is a good idea to also
accept lines with encoded-words that are longer than that because
they appear in the real world.
> >2. Differences enforced by verbiage.
> >------------------------------------
> [...]
> >2.3 The content of the first line of a header MUST NOT consist of WSP only
> > (though such SHOULD be accepted). Observe that continuation lines
> > of headers also MUST NOT consist of WSP only, as in RFC 2822.
>
> The first part of that may be a problem (see above and below re.
> encoded-words -- it may be necessary to fold).
No problem here except when the charset*language part of an
encoded-wort exceeds 76 - header-name length - 10 characters (for
colon, SP, =?, ?Q? or ?B?, ?=, and at least one charater as
encoded-text). White space between two encoded-words is to be
ignored, so you can fold in between without any effect for the
decoded text. "=?ISO-8859-1?Q?F=AE?= =?US-ASCII?Q?rber?=" decoded is
"Färber", for example (whereas "=?ISO-8859-1?Q?F=AE?= rber" would be
"Fä rber").