RFC2369 bug (was

On Thu, 26 Aug 2010 17:18:49 PDT, Harvey Eneman said:

> I think the message is violating rfc2369, i.e., the individual urls are not 
> angle-bracket enclosed.  The real question may be how flexible do we want 
> exmh to be?   We can modify the Hook_MsgShowListHeaders code to ignore the
> invalid list (as per stricture #3) or modify the regular expression to support
> comma separated lists of url's within angle-brackets.

List-unsubscribe: <http://tr.innovyx.net/lu?xcJTqnlvEJnWJqcvq ,
	mailto:[email protected]?subject=unsubscribe>

Well, reading rfc2369 section 2, I see where the mail sender went astray:

   A list of multiple, alternate, URLs MAY be specified by a comma-
   separated list of angle-bracket enclosed URLs.

And it is in fact a comma-separated list of URLS that are angle-bracket enclosed.

   The list header fields are subject to the encoding and character
   restrictions for mail headers as described in [RFC822]. Additionally,
   the URL content is further restricted to the set of URL safe
   characters [RFC1738].

   The contents of the list header fields mostly consist of angle-
   bracket ('<', '>') enclosed URLs, with internal whitespace being
   ignored. MTAs MUST NOT insert whitespace within the brackets, but
   client applications should treat any whitespace, that might be
   inserted by poorly behaved MTAs, as characters to ignore.

So strictly speaking, we're supposed to ignore the line break and whitespace and
treat it as one line-wrapped URL.  And it's at least conceivable that a List-foo:
could contain a long ugly line-wrapped VERP'ed address, at which point it becomes
difficult to properly support a line-wrapped URL and still be flexible enough to
accept the broken form we're looking at here.

The quick fix would be to wrap some code in a 'if ![info exists url]', the pedantic
fix would be to properly elide the white space and un-linewrap it, and I'm pretty sure
nobody's motivated enough to do the mind-reading fix (feel free to astound me with
a patch though ;)  Right now, I'm leaning towards a quick fix, a comment block,
and an entry in the TODO list....

_______________________________________________
Exmh-users mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/exmh-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001

iD8DBQFMdz7UcC3lWbTT17ARAuviAJ40bgqCNQflyY/FlF92sKhzr7dtMwCfU9Ls
ieALT03c5A9naCIAaeNS68A=
=ENcZ
-----END PGP SIGNATURE-----