In <2147483647(_dot_)1030011437(_at_)dsl108-043(_dot_)brandx(_dot_)net> Chris
Newman <Chris(_dot_)Newman(_at_)Sun(_dot_)COM> writes:
No. Although in 2822 we deprecated the most problematic constructs
(particularly the ones permitted in 822 but not in 821). It's risky to
retroactively declare previously compliant constructs to be incompliant,
even if we didn't know of any specific implementations. So this is a case
where what's legal by the standard is a superset including constructs which
are not a good idea to use.
If you're curious, here's a writeup I did of special characters in email
addresses:
Yes that looks like a good survey. It contains all that is really
necessary for those who invent mailbox names for their own servers. Life
would be much simpler if we could tell them all the excluded cases were to
be considered obsolete (I.e. MUST accept, but SHOULD NOT use for new
names).
And it would also be useful to be deciding what escape character you are going
to use in those punycoded local-parts.
--
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