Externals recipients don't get customized DSNs
Hi everyone,
I tried to create customized DSNs with the New-SystemMessage cmdlet. I have created both en\internal\5.2.3 and en\external\5.2.3 on my Hub Transport server. When I send an oversized message within the organization my customized DSN works flawlessly. But when someone sends a large message from outside the organization, all they get back is the standard English 5.2.3 DSN.Do I need to set anything else for external NDRs to work?
Thanks,
Marton
November 13th, 2007 10:51pm
probably a -internal $true mix up.
Check out the syntax here:
http://technet.microsoft.com/en-us/library/aa998878.aspx
Free Windows Admin Tool Kit Click here and download it now
November 13th, 2007 11:58pm
I'm not sure what you mean by mix up, but here's how I got it set up.
Output of Get-SystemMessage | Format-List is as follows:
Text : Blah blah blah, my custom textInternal : FalseLanguage : enDsnCode : 5.2.3QuotaMessageType :AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : 5.2.3DistinguishedName : CN=5.2.3,CN=External,CN=9,CN=DSN Customization,CN=Transport Settings,CN=MYORG,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=localIdentity : en\External\5.2.3Guid : ffd503b9-19a4-47cf-9a71-ea37198505a1ObjectCategory : domain.local/Configuration/Schema/ms-Exch-DSN-MessageObjectClass : {top, msExchDSNMessage}WhenChanged : 2007. 11. 13. 17:06:06WhenCreated : 2007. 11. 13. 16:16:56OriginatingServer : dc2.domain.localIsValid : True
Text : Blah blah blah, my custom textInternal : TrueLanguage : enDsnCode : 5.2.3QuotaMessageType :AdminDisplayName :ExchangeVersion : 0.1 (8.0.535.0)Name : 5.2.3DistinguishedName : CN=5.2.3,CN=Internal,CN=9,CN=DSN Customization,CN=Transport Settings,CN=MYORG,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=localIdentity : en\Internal\5.2.3Guid : ba53e410-0e56-4ed4-987c-3a94df3c2905ObjectCategory : domain.local/Configuration/Schema/ms-Exch-DSN-MessageObjectClass : {top, msExchDSNMessage}WhenChanged : 2007. 11. 13. 16:24:22WhenCreated : 2007. 11. 13. 16:24:01OriginatingServer : dc2.domain.localIsValid : True
This seems correct to me.
November 14th, 2007 12:15am
by mix-up i simply meant if you had entered the new-systemmessage cmdlet with -internal $true
Looking at this output, it seems like it should work....sorry, unless i'm missing something i'm stumped.
Free Windows Admin Tool Kit Click here and download it now
November 14th, 2007 12:23am