Friday, September 3, 2010

Localized language in NDR's, in Exchange 2010

Hi,
In Exchange 2010, there's a configuration parameter called "ExternalDsnLanguageDetectionEnabled"
In my situation, it meant that most of the error messages, the so called NDR's (Non Delivery Reports) or DSN's (Delivery Status Notification) was sent in Danish.
In an international Company, this is not what we want.

So I had to change the default language of the NDR's to be English instead of Danish.
 
This can be done by using the set-transportconfig command.
I did this:
get-transportconfig | set-transportconfig -ExternalDsnLanguageDetectionEnabled $false -ExternalDsnDefaultLanguage en-us -InternalDsnLanguageDetectionEnabled $false -InternalDsnDefaultLanguage en-us

So the autmatic language detection is turned of, and the default language is set to English

Please notice, in Exchange 2007, you can use set-transportserver instead.

13 comments:

  1. great it really helped me :)

    ReplyDelete
  2. Thanks! I've been looking for this!

    Great help!

    ReplyDelete
  3. Thank you very much!

    ReplyDelete
  4. I cant get this working... I still got the NDR in Danish, also after reboot of the server,

    any ideas?

    ReplyDelete
  5. Hi,
    Can I get some more info?
    Are you running Exchange 2010, and can you confirm that the parameter is correctly set, when you run get-transportconfig?

    BR,
    Lasse I.

    ReplyDelete
  6. i tried it but it doesnt work . has anyone a solution ?

    ReplyDelete
  7. Worked fro me!

    Thanks you.

    ReplyDelete
  8. I running on a Exchange 2010 Sp1
    All settings are correct but it does not work

    ReplyDelete
  9. Running version 14.2 (build 247.5) Settings look correct as above, but ndr's still in local language...
    Any ideas?

    ReplyDelete
    Replies
    1. If you want to change all mailbox setting, you can use this cmdlet:
      get-mailbox | set-mailbox -languages en-us

      perhaps client side

      Delete
  10. Thanks, it worked! For those who could not make it, did you ran the command within Exchange Mgmt Shell as Admin? At first I tried to run it Windows powershell and it failed.

    ReplyDelete
  11. Yes that's correct - Always run the EMS as admin, otherwise you wont have the correct permissions or CMDlets :-)

    ReplyDelete