This is a discussion on Re: [courier-users] IDN in domain name within the Courier-Imap forums, part of the Mail Servers and Related category; --===============0603422962== Content-Type: multipart/signed; boundary="nextPart6990733.uEG1S37CmA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
--===============0603422962==
Content-Type: multipart/signed; boundary="nextPart6990733.uEG1S37CmA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart6990733.uEG1S37CmA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi. On Tuesday 15 April 2008, Jesper Langkj=E6r wrote: > Hi.. > > I've live i Denmark and pretty funny letters like (=E6=F8=E5 =C6=D8=C5) > And now when you can have this i your domain name we have som problem > with courier-0.56.0-1.6. > When we try to send mail to ex. permat=E6t.dk we get an "#5.0.0 smtp; 501= Bad > address syntax" > > Are ther anything we can do about that ? As far as I know the IDN specs, all server applications should never been=20 bugged with IDN domain names. Clients should do the punycode conversion=20 offline and then only use the xn--foobar-...-version in SMTP dialog. Quote from http://tools.ietf.org/html/rfc3490#section-6 about the=20 communication of the client program to the server: | ACE unless the protocol is updated to handle other encodings But hey, IMO it's a *really* bad idea to use IDN for e-mail at all. In practice, nearly noone does only provide his webpage via IDN because peo= ple=20 with non-native keyboards will not be able to call the address. Concerning= =20 e-mail, this is even worse, I think. There aren't many client programs out= =20 there that can handle IDN addresses and it breaks the allowed characters fo= r=20 header fields as described in RFC 2822. regards, Bernd =2D-=20 There are only two things wrong with C++: The initial concept and the implementation. - Bertrand Meyer --nextPart6990733.uEG1S37CmA Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iQIcBAABAgAGBQJIBFOwAAoJEA0b18vi86Q/6BYP/jdlj4G9m62vKsElc9L+E34v CEU5ajj9IUPDiaImRSb1exem0bcW6oQOv21L2p/Y5gaOh8kHsM3s6NNSdCUa3waB Znae7RVY2e+Gp13S9yrWSVleQ6jDfQ+D7BChE+xIh+Cb6PZtlz Q3BseEKHJt4Pew 9WRavFYEe8A+ZKZkA7+vUcxLlxWzbyUlYUC/06YqUc33KHJBn26DYfFGAvjMXQ8q /Ny1KhiJHuoT4y+xpiGSBX3Fcf/2j+N6n31NYDB/T9S/UX6OikN8vEbuzNpSEpSz GzrLv+Hp39jvYT+l82NGDx0AdDCVNMqz/v9eFy6FCWOjYONOZPF1Ax6nm1Wo2hcZ FqjyAY2eVnVoHDjUssPnEARcrbLPH72faSB7IlGECKG5CkX3l1 QoOiAUmL6ysgIu iy6w4VZ4DKA+tnVuUG34Ftz6L/nS6DfOGn+LGxCOwtXcrHE2RxrTeZ8QUBEqhPo8 Q2Y+u1u2PxomUO1Chf7+OhfOrpRD3huXhCoF36jFMqM422VlbV ZG9lv5ii8gPVId 6sx8zpPcDp8ETMWcEOMFxoOsISnHHc5SuvAblvkGNeh12JT5gk W3eO7ayyMXnuo5 Dl4n20d1urdcOOIhLh9xrxVJ4EpM2Jfodq11GzpzLZ0yHTdCJY 8PHZc1WU1bY5G0 F4OiTPEUJ61+mAZpyCfJ =axnk -----END PGP SIGNATURE----- --nextPart6990733.uEG1S37CmA-- --===============0603422962== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757...un.com/javaone --===============0603422962== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users --===============0603422962==-- |
![]() |
| Thread Tools | |
| Display Modes | |
|
|