Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!news.musoftware.de!wum.musoftware.de!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Sandman Newsgroups: comp.lang.php Subject: Re: What this means "(\w|-)+@\w"? Date: Wed, 03 Aug 2011 10:02:46 +0200 Lines: 41 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: individual.net IFMus7PVvKlraIyQmYZNKQPjqjkck5QYoxSKtwGvPknsvOhL0= X-Orig-Path: mr Cancel-Lock: sha1:0HBJswgxX7mSCWRZdqmVIQG5EwA= User-Agent: MT-NewsWatcher/3.5.2 (Intel Mac OS X) X-Face: $@,Vfa$,)%=Qa7L]y)&oZj_\EiHc}}Af0Bei"4a_%)"c6TQ+P/:53>;PNGuWUmkqyeN-qM65foJ[;T_(k;>]&G\T4Lhm:2 ujye2_,iUJFE;NZn>y;.|-hl7g~bIOF1qG\o, Eli the Bearded <*@eli.users.panix.com> wrote: > In comp.lang.php, Sandman wrote: > > Is SMTP supposed to support IDN? And even if it's supposed to, what > > SMTP servers correctly parse IDN? I mean, percentage-wise? > > IDN exists above the SMTP layer. An international domain name > supporting client is supposed to convert the name to and from > punycode, which is highbit text encoded in plain ASCII > alphanumerics. The punycode name is valid at for all email > purposes. > > In this model, a user entering an email address with an IDN > host into a form should be allowed. But the web site needs to > convert that -- as needed -- to the traditional DNS form. > > I know I've never done that in my code. I should probably fix > that. Yes, I know it is above the smtp layer, but a SMTP surely shouldn't deliver mail to a client with IDN as punycode? But I suppose the punycode could be only in the transmission layer with the "To:" header intact as IDN. I own a couple of IDN, but I never accept mail to them though. Perhaps I should. :) > Elijah > ------ > perhaps this is finally the excuse to get a vanity IDN hostname Or Emoji: http://www.panic.com/blog/2011/07/the-worlds-first-emoji-domain/ :-D -- Sandman[.net]