In <200211112234(_dot_)gABMYEl22163(_at_)astro(_dot_)cs(_dot_)utk(_dot_)edu>
Keith Moore <moore(_at_)cs(_dot_)utk(_dot_)edu> writes:
I think it would be reasonable for a displaying user agent to
re-wrap any continued header field that contained encoded-words.
It would be even more reasonable for the original composing agent to do
line splitting for 78 characters _before_ doing the RFC 2047 encoding
(however, it has to watch the 75 limit in RFC 2047). Thar might appear to
break the "SHOULD be less than 78" limit in RFC 2047, but that limit was
provided for the benefit of humans. The hard limit is 998 characters, and
the examples are well inside that.
OTOH, I dislike displaying agents that tinker with what was received.
Sometime people have good reasons to use long headers (long URLs for
example), and it is not up to displaying agents to second guess the user's
intent.
So although Jacob's original example did not breach RFC 2822 in the
letter, it did breach it in the spirit.
--
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133 Web: http://www.cs.man.ac.uk/~chl
Email: chl(_at_)clw(_dot_)cs(_dot_)man(_dot_)ac(_dot_)uk Snail: 5
Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5