Ned Freed <ned(_dot_)freed(_at_)mrochek(_dot_)com> writes:
...
IMO it would be better to say something along the lines of
Header lines are unfolded as described in [IMAIL] section 2.2.3.
Interpretation of header data should be done according to [MIME3]
section 6.2.
This makes the required sequence of operations clear. Note that I also removed
the term "long" - in practice it isn't only long lines that are folded.
I like it, though I think there should be a forward reference to 2.7.2
as that's where the precise requirements are stated. So:
Header lines are unfolded as described in [IMAIL] section 2.2.3.
Interpretation of header data SHOULD be done according to [MIME3]
section 6.2 (see 2.7.2 below for details).
Hmm, applying 2047 decoding requires knowing whether the header is
'structured': if a header is structured, then encoded words can occur
after an open-paren or before a close-paren without intervening
whitespace, something which isn't true of unstructured headers. Do we
need to give guidence to implementors on this or just punt it as a
general 2047 issue not specific to sieve?
Philip Guenther