Re: allowed chars in local-part

Reindl Harald: > Am 06.03.2012 02:41, schrieb Wietse Venema: > > Reindl Harald: > >> i am not sure if my validation is up-to-date in > >> rejecting "frankkr?t...@example.com" > >> > >> AFAIK ??? are only allowed in DOMAIN name (IDN) > > > > RFC5321/22 do not allow non-ASCII in the localpart or dom

Re: allowed chars in local-part

Am 06.03.2012 02:41, schrieb Wietse Venema: > Reindl Harald: >> i am not sure if my validation is up-to-date in >> rejecting "frankkr?t...@example.com" >> >> AFAIK ??? are only allowed in DOMAIN name (IDN) > > RFC5321/22 do not allow non-ASCII in the localpart or domain, or > in any message head

Re: allowed chars in local-part

Reindl Harald: > i am not sure if my validation is up-to-date in > rejecting "frankkr?t...@example.com" > > AFAIK ??? are only allowed in DOMAIN name (IDN) RFC5321/22 do not allow non-ASCII in the localpart or domain, or in any message header. All encodings of non-ASCII in domains and header valu

allowed chars in local-part

hi i am not sure if my validation is up-to-date in rejecting "frankkröt...@example.com" AFAIK üöä are only allowed in DOMAIN name (IDN) this moment got a notify that a address with this localpart was removed from a newsletter table where validation at input-time seems to be missing signatur