If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.
how can i configure Exchange 2007 to recieve mails with "ø" in domain name?
a customer has bought a domainname with an ø in it (lets call it "dømain.dk") and would like to send and recieve mails on this domain.
besides the obvious potential compatability issues, is there any way to configure Exchange 2007 to accept scandinavian characters in domainname?
When i try to set up a new domain in "Organization Configuration => Hub Transport => Accepted domains", I get the following error:
X Some controls are not valid
-invalid SMTP domain
Back in exchange 2003, we where able to set up this with some registry hacks, but those are not working here.
It's a Small Business 2008 Server with Exchange 2007
Any input would be appriciated :)
besides the obvious potential compatability issues, is there any way to configure Exchange 2007 to accept scandinavian characters in domainname?
When i try to set up a new domain in "Organization Configuration => Hub Transport => Accepted domains", I get the following error:
X Some controls are not valid
-invalid SMTP domain
Back in exchange 2003, we where able to set up this with some registry hacks, but those are not working here.
It's a Small Business 2008 Server with Exchange 2007
Any input would be appriciated :)
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
This is allowed under RFC's 3490 and 3492. The term you are looking for is called "Punycode"
http://tools.ietf.org/html/rfc3490
http://tools.ietf.org/html/rfc3492
You will find that "dømain.dk" will translate to a real ascii type domain, in this instance, it converts to
xn--dmain-vua.dk
This is what you will need to set exchange to receive for.
There is a punycode converter available at
http://idnaconv.phlymail.de/index.php?decoded=d%C3%B8main.dk&encode=Encode
http://tools.ietf.org/html/rfc3490
http://tools.ietf.org/html/rfc3492
You will find that "dømain.dk" will translate to a real ascii type domain, in this instance, it converts to
xn--dmain-vua.dk
This is what you will need to set exchange to receive for.
There is a punycode converter available at
http://idnaconv.phlymail.de/index.php?decoded=d%C3%B8main.dk&encode=Encode
Oh,
and Verisign also have a punycode converter at
http://mct.verisign-grs.com/
Personally, I'd feel more comfortable using the Verisign one
and Verisign also have a punycode converter at
http://mct.verisign-grs.com/
Personally, I'd feel more comfortable using the Verisign one
Output from Management Shell -> attached code snippet (no go)
pb969:
How do i implement this in Exchange?
i can see the logic in being able to recieve mails on ((dømain.dk)Punycode = xn--dmain-vua.dk), by adding the domain "xn--dmain-vua.dk"
but how about sending email's? wont the sender adress be user@xn--dmain-vua.dk ? i still need it to be user@dømain.dk...
pb969:
How do i implement this in Exchange?
i can see the logic in being able to recieve mails on ((dømain.dk)Punycode = xn--dmain-vua.dk), by adding the domain "xn--dmain-vua.dk"
but how about sending email's? wont the sender adress be user@xn--dmain-vua.dk ? i still need it to be user@dømain.dk...
New-AcceptedDomain : Cannot bind parameter 'DomainName'. Cannot convert value "
dømain.dk" to type "Microsoft.Exchange.Data.SmtpDomainWithSubdomains". Error: "I
nvalid SMTP domain"
At line:1 char:46
+ New-AcceptedDomain -Name "Dømain test" -DomainName <<<< dømain.dk -DomainType Auth
oritative
Hi itfdrift,
It is the same, when someone sends an email using their email client to xxx@dømain.dk, the email client will automatically convert the dømain.dk to the internet acceptable format, in the same way that the email client already converts binary messages to mime. It is transparent to the user
demazter, yes, you cannot put dømain.dk as a domain name in Exchange, or any other email system for that matter, as far as exchange is concerned, it is receving an email addresed to xn--dmain-vua.dk.
As far as the end user is concerned, they are sending an email to dømain.dk
It is the same, when someone sends an email using their email client to xxx@dømain.dk, the email client will automatically convert the dømain.dk to the internet acceptable format, in the same way that the email client already converts binary messages to mime. It is transparent to the user
demazter, yes, you cannot put dømain.dk as a domain name in Exchange, or any other email system for that matter, as far as exchange is concerned, it is receving an email addresed to xn--dmain-vua.dk.
As far as the end user is concerned, they are sending an email to dømain.dk
pb969:
let me get this straight - if i set the users emailadress to username@xn--dmain-vua.dk , and the user sends an email to rexipient x, recipient x should se "username@dømain.dk" as the senders email-address?
That would be awesome :D
let me get this straight - if i set the users emailadress to username@xn--dmain-vua.dk , and the user sends an email to rexipient x, recipient x should se "username@dømain.dk" as the senders email-address?
That would be awesome :D
This is certainly a new one on me.
I would like to see this if you want to send me a test e-mail I can confirm? my e-mail address is on my profile.
I would like to see this if you want to send me a test e-mail I can confirm? my e-mail address is on my profile.
Yes - you got it right,
However, there is a small caveat, and that is, the email client must be international domain name aware,
Because the conversion itself happens at the client application end. In the end, it has nothing to do with Exchange and more to do with the email client they are using. It also has nothing to do with DNS either, because DNS should have the punycode version of the text. This is not a limitation of DNS, but rather the technologies that use DNS.
People with International Domain Name aware email clients will see the from and to fields populated using the origin language characters. People ( like me ) with a Western Email client, wont see it - I would get the punycode version.
My Outlook 2003 doesn't support punycode , Gmail does not, and a test I did on a unix machine didn't like it either. People that do not have International Domain Name aware email clients willl need to send to the punycode equivalent address. If I tried to send to "test@dømain.dk", my email client tells me that there are invalid characters in the To address field.
However, most modern web browsers support the punycode conversion.
For fun, click this address
www.ta¿¿de¿¿.gr
you will find that it is the same as the punycode version below....
www.xn--mxagdoy8a2b5a.gr
It's not the best example, because it has a diversion to another site completely ( a greek travel site ), but you will see that both the original and punycode go to the same place. www.ta¿¿de¿¿.gr was the only real example I could find off the top of my head so quickly :)
Unfortunately, while this is all possible, your client may need to come down to earth on a few practicality issues, because of the nature of how many email clients would require the punycode version, and I cant guarantee the availability of International Domain Name aware email clients in the native country, the client may be better advised to keep the international name for their website, and use something simpler for email.
Paul
However, there is a small caveat, and that is, the email client must be international domain name aware,
Because the conversion itself happens at the client application end. In the end, it has nothing to do with Exchange and more to do with the email client they are using. It also has nothing to do with DNS either, because DNS should have the punycode version of the text. This is not a limitation of DNS, but rather the technologies that use DNS.
People with International Domain Name aware email clients will see the from and to fields populated using the origin language characters. People ( like me ) with a Western Email client, wont see it - I would get the punycode version.
My Outlook 2003 doesn't support punycode , Gmail does not, and a test I did on a unix machine didn't like it either. People that do not have International Domain Name aware email clients willl need to send to the punycode equivalent address. If I tried to send to "test@dømain.dk", my email client tells me that there are invalid characters in the To address field.
However, most modern web browsers support the punycode conversion.
For fun, click this address
www.ta¿¿de¿¿.gr
you will find that it is the same as the punycode version below....
www.xn--mxagdoy8a2b5a.gr
It's not the best example, because it has a diversion to another site completely ( a greek travel site ), but you will see that both the original and punycode go to the same place. www.ta¿¿de¿¿.gr was the only real example I could find off the top of my head so quickly :)
Unfortunately, while this is all possible, your client may need to come down to earth on a few practicality issues, because of the nature of how many email clients would require the punycode version, and I cant guarantee the availability of International Domain Name aware email clients in the native country, the client may be better advised to keep the international name for their website, and use something simpler for email.
Paul
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
Sorry, I just realised that the link to the greek travel website I gave above broke once it was published to EE ( the native greek language version ) .
Use the tools I gave above to convert www.xn--mxagdoy8a2b5a.gr to back native and check out the page
Use the tools I gave above to convert www.xn--mxagdoy8a2b5a.gr to back native and check out the page
Thanks! blew my mind :)
dezmaster: if your clients doesn't support it, there is no point in it.
If you use Outlook, you can download a free IDN plug-in here: http://www.idnnow.com/index.jsp?lang=en
... still, no garantuee of your recipients compatability...
dezmaster: if your clients doesn't support it, there is no point in it.
If you use Outlook, you can download a free IDN plug-in here: http://www.idnnow.com/index.jsp?lang=en
... still, no garantuee of your recipients compatability...
Thanks demazter for your input, the solution works within the bounds I described. Try the IDN plugins if you like.
:)
:)
I'm just saying it's pretty pointless if it cannot be used by anyone.
You will need to send out a little notice on all your e-mails "by the way if you can't see my e-mail address properly then download this IDN plugin"
Somehow I cannot see that working.
You will need to send out a little notice on all your e-mails "by the way if you can't see my e-mail address properly then download this IDN plugin"
Somehow I cannot see that working.
Thanks again demazter
They will see the email address, but the domain will appear as xn--dmain-vua.dk
This will allow sending and receiving to non IDN aware clients.
We also need to remember that the primary market will have users motivated to ensure that their email clients support their language.
As for the practicality of it, well, I think I already covered that well.
As a new EE user giving answers to questions, I appreciate your comments, especially given your Genius rating, to assist me in my early days here.
They will see the email address, but the domain will appear as xn--dmain-vua.dk
This will allow sending and receiving to non IDN aware clients.
We also need to remember that the primary market will have users motivated to ensure that their email clients support their language.
As for the practicality of it, well, I think I already covered that well.
As a new EE user giving answers to questions, I appreciate your comments, especially given your Genius rating, to assist me in my early days here.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
Have you tried running it in Exchange Management Shell?
New-AcceptedDomain -Name "dømain" -DomainName dømain.dk -DomainType Authoritative