In <3E03AB9A(_dot_)5070001(_at_)Sonietta(_dot_)blilly(_dot_)com> Bruce Lilly
<blilly(_at_)erols(_dot_)com> writes:
Charles Lindsey wrote:
In <3DFF6CA2(_dot_)80305(_at_)alex(_dot_)blilly(_dot_)com> Bruce Lilly
<blilly(_at_)erols(_dot_)com> writes:
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%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).
Yes, but if the URI is decoded URI-wise, then I see nothing which suggests
that it should then be further subjected to RFC 2047 decoding. If it is a
structured header (I guess List-Owner is structured) then RFC 2047
instructs you to identify comments and phrases within it. In your example
there are none. End of story, so far as RFC 2047 is concerned. You now
hand it over to the URI department, which may or may not be able to find a
valid mailing address within it.
--
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