Re: Question regarding RFC 2369

In article <1532183533.1694870.1448275552.60F55C41@webmail.messagingengine.com> you write:
>> To the extent the first clause applies to software generating messages
>> that might contain list header fields, usually for the purpose of
>> first sending them, this makes it harder for software to encode
>> message header fields in a generic manner rather than having to deal
>> with special cases like the list header fields, since, among other
>> things, such software may seek to comply with line length limitations
>> in RFC 5322 by folding long lines in accordance with that RFC.

Remember that MUST means "do this if you want to interoperate", not "do this or die."

Plan A: update RFC 2369 to say MAY add spaces, send out a press release, wait for
everyone in the world to update their software to remove spaces when parsing List-x
headers.

Plan B: figure out how to make your URLs short enough that your List-Unsubscribe
headers are under 998 characters.

I know what I'd do.

R's,
John

_______________________________________________
ietf-822 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/ietf-822