Charles Lindsey wrote:
In <3DFF6CA2(_dot_)80305(_at_)alex(_dot_)blilly(_dot_)com> Bruce Lilly
<blilly(_at_)erols(_dot_)com> writes:
To: empty-list:;, =?iso-8859-1?Q?J=FCrgen?= j(_at_)foo(_dot_)com
I made an error; that should be
To: empty-list:;, =?iso-8859-1?Q?J=FCrgen?= <j(_at_)foo(_dot_)com>
Yes, groups in addresses are a pain
It's not a problem for a grammar-based parser, nor for relatively simple
parsing (the group addresses are bracketed by the colon/semicolon
pair). Even a regular expression could be crafted to handle groups.
Excluding content bracketed in <> would also be an error. Consider RFCs
2368 and 2369 (not to be confused with 2396, which is also applicable) and:
List-Owner:
<mailto:%3D%3fiso-8859-1%3FQ%3fJ%3dFCrgen%3F%3d%20j(_at_)foo(_dot_)com?Subject=list>
That also is an error, I meant
List-Owner:
<mailto:%3D%3fiso-8859-1%3FQ%3fJ%3dFCrgen%3F%3d%20%3cj(_at_)foo(_dot_)com%3E?Subject=list>
That does contain an RFC2047 encoded-word within the <>.
Eh? I don't see one.
As mentioned in the earlier message, it's URI-encoded as required by
RFC 2368 (section 2). Depending on UA, you may be able to see it
simply by positioning your cursor over the mailto URI (at least
that works with Mozilla 1.2.1).
Somewhat off-topic digression: I checked handling of that in a few MUAs.
Here's what happens:
Mozilla 1.2.1: positioning the cursor over the URI displays the URI-
decoded version on the status line. Clicking on the URI opens a
message composition window which seems to do the right things (mailbox
appears as To header, display name is decoded for display, subject
header is correct).
Evolution 1.2.1: right-clicking on the URI sort-of displays the URI-
decoded version (the angle brackets around the addr-spec are missing).
Clicking on the URI opens a composition window with a syntactically
and semantically correct To header, but the 2047 encoding is not
decoded for display. The Subject header is correct.
Kmail 1.4.3: hovering over the link simply displays it verbatim on
the status line. Clicking opens a composition window which gets the
To header correct (and 2047-encoding decoded for display), but leaves
the Subject field blank.
Microsoft Outlook Express: hovering over the URI displays the URI-
decoded version on the status line. Clicking on it opens a
composition window, but the To header is botched pretty badly.