In <4165CFB1(_dot_)8040803(_at_)erols(_dot_)com> Bruce Lilly
<blilly(_at_)erols(_dot_)com> writes:
Charles Lindsey wrote:
But you have not answered the question. We were discussing the <id-right>
in <msg-id>s. Have you heard of any case where this esoteric change of
semantics actually caused a problem?
I have indeed answered exactly that question, in detail.
For example:
Interpreting a msg-id RHS as RFC 2822 id-right means that one
cannot determine whether <foo(_at_)bar(_dot_)com> matches
<foo(_at_)Bar(_dot_)COM>
because RFC 2822 doesn't specify whether or not id-right is
a domain name. It might be or it might not be. In the event
that it is not, RFC 2822 is silent on whether or not case
matters. Under RFC 822, the RHS of a msg-id was always a
domain, and as domain names are always case-insensitive, the
two msg-ids above would match under RFC 822. Under RFC 2822,
one cannot tell whether or not they match.
Yes, I know all that. You have demonstrated that a problem could,
_in_principle_ arise. But my question, which I repeat again and which you
still have not answered, was:
Have you heard of any case where this esoteric change of semantics
actually caused a problem?
IOW, is this a theoretical curiosity, or a cause of real problems in
meatspace?
--
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_)clerew(_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