locked
External DSN configured, but not working RRS feed

  • Question

  • We recently determined that no external DSN messages were being sent.  I checked and there were none configured, so I added some for testing; however, I am still only receiving internal DSN messages.  Our DRN is enabled and I setup a postmaster account.  What else do I have to do to allow for external DSN?  We need to send DSN's for bad email addresses (against recommendations I know) and over sized messages/attachments.

    We're running Exchange 2010 SP3 in a simple setup:  one CAS and one MBS. 

    [PS] C:\Windows\system32>Get-ExchangeServer | Format-Table Name, *Version*

    Name                                    AdminDisplayVersion                     ExchangeVersion
    ----                                    -------------------                     ---------------
    CAS01                                 Version 14.3 (Build 123.4)              0.1 (8.0.535.0)
    MBS01                                 Version 14.3 (Build 123.4)              0.1 (8.0.535.0)


    [PS] C:\Windows\system32>get-TransportConfig


    ClearCategories                     : True
    ConvertDisclaimerWrapperToEml       : False
    DSNConversionMode                   : UseExchangeDSNs
    ExternalDelayDsnEnabled             : True
    ExternalDsnDefaultLanguage          : en-US
    ExternalDsnLanguageDetectionEnabled : True
    ExternalDsnMaxMessageAttachSize     : 10 MB (10,485,760 bytes)
    ExternalDsnReportingAuthority       :
    ExternalDsnSendHtml                 : True
    ExternalPostmasterAddress           : PostMaster@PSystems.com
    GenerateCopyOfDSNFor                : {}
    HygieneSuite                        : Standard
    InternalDelayDsnEnabled             : True
    InternalDsnDefaultLanguage          :
    InternalDsnLanguageDetectionEnabled : True
    InternalDsnMaxMessageAttachSize     : 10 MB (10,485,760 bytes)
    InternalDsnReportingAuthority       :
    InternalDsnSendHtml                 : True
    InternalSMTPServers                 : {}
    JournalingReportNdrTo               : <>
    LegacyJournalingMigrationEnabled    : False
    MaxDumpsterSizePerDatabase          : 18 MB (18,874,368 bytes)
    MaxDumpsterTime                     : 7.00:00:00
    MaxReceiveSize                      : 19.77 MB (20,725,760 bytes)
    MaxRecipientEnvelopeLimit           : 5000
    MaxSendSize                         : 19.77 MB (20,725,760 bytes)
    MigrationEnabled                    : False
    OpenDomainRoutingEnabled            : False
    Rfc2231EncodingEnabled              : False
    ShadowHeartbeatRetryCount           : 12
    ShadowHeartbeatTimeoutInterval      : 00:15:00
    ShadowMessageAutoDiscardInterval    : 2.00:00:00
    ShadowRedundancyEnabled             : True
    SupervisionTags                     : {Reject, Allow}
    TLSReceiveDomainSecureList          : {}
    TLSSendDomainSecureList             : {}
    VerifySecureSubmitEnabled           : False
    VoicemailJournalingEnabled          : True
    HeaderPromotionModeSetting          : NoCreate
    Xexch50Enabled                      : True

    [PS] C:\Windows\system32>Get-RemoteDomain | select identity, NDREnabled

    Identity                                                                                                     NDREnabled
    --------                                                                                                     ----------
    Default                                                                                                            True

    [PS] C:\Windows\system32>Get-SystemMessage

    Identity                  Text
    --------                  ----
    en\Internal\5.1.1         Delivery Failure
    en\External\5.1.1         Delivery Failure
    en\External\5.1.0         Delivery Failure Code 5.1.0, sender denied.
    en\External\5.1.2         Delivery Failure Code 5.1.2, SMTP 500 Host unknown.
    en\External\5.1.3         Delivery Failure Code 5.1.3, invalid recipient address.
    en\External\5.1.4         Delivery Failure Code 5.1.4, address ambiguous.
    en\External\5.1.5         Delivery Failure Code 5.1.5, invalid destination address.
    en\External\5.1.6         Delivery Failure Code 5.1.6, home issue.
    en\External\5.1.7         Delivery Failure Code 5.1.7, invalid address.
    en\External\5.1.8         Delivery Failure Code 5.1.8, sender address issue.
    en\External\5.2.1         Delivery Failure Code 5.2.1- mailbox cannot be accessed.
    en\External\5.2.2         Delivery Failure Code 5.2.2- mailbox quota exceeded.
    en\External\5.2.3         Delivery Failure Code 5.2.3- message size exceeds maximum.
    en\External\5.2.4         Delivery Failure Code 5.2.4- error.

    Any help would be much appreciated.

    Thanks,

    -Melody


    Wednesday, October 2, 2013 8:32 PM

All replies

  • What about your remote domains?

    get-remotedomain | ft name, ndrenabled


    --- Rich Matheisen MCSE&I, Exchange MVP

    Thursday, October 3, 2013 1:21 AM
  • Hi,

    I suggest we use the following example to create the DSN message:

    http://technet.microsoft.com/en-us/library/aa998878(v=exchg.150).aspx

    Thanks,

    If you have feedback for TechNet Subscriber Support, contact tnsfl@microsoft.com


    Simon Wu
    TechNet Community Support

    Thursday, October 3, 2013 9:38 AM
    Moderator
  • It's enabled

    [PS] C:\Windows\system32>get-remotedomain | ft name, ndrenabled

    Name                                                                                                         NDREnabled
    ----                                                                                                         ----------
    Default                                                                                                            True

    Monday, October 7, 2013 2:41 PM
  • I did that already, but it's still not working for external

    PS] C:\Windows\system32>Get-SystemMessage

    Identity                  Text
    --------                  ----
    en\Internal\5.1.1         Delivery Failure
    en\External\5.1.1         Delivery Failure
    en\External\5.1.0         Delivery Failure Code 5.1.0, sender denied.
    en\External\5.1.2         Delivery Failure Code 5.1.2, SMTP 500 Host unknown.
    en\External\5.1.3         Delivery Failure Code 5.1.3, invalid recipient address.
    en\External\5.1.4         Delivery Failure Code 5.1.4, address ambiguous.
    en\External\5.1.5         Delivery Failure Code 5.1.5, invalid destination address.
    en\External\5.1.6         Delivery Failure Code 5.1.6, home issue.
    en\External\5.1.7         Delivery Failure Code 5.1.7, invalid address.
    en\External\5.1.8         Delivery Failure Code 5.1.8, sender address issue.
    en\External\5.2.1         Delivery Failure Code 5.2.1- mailbox cannot be accessed.
    en\External\5.2.2         Delivery Failure Code 5.2.2- mailbox quota exceeded.
    en\External\5.2.3         Delivery Failure Code 5.2.3- message size exceeds maximum.
    en\External\5.2.4         Delivery Failure Code 5.2.4- error.

    Any help would be much appreciated.

    Monday, October 7, 2013 2:42 PM
  • Is there any additional information I can provide that would be helpful?  We're in a sticky situation over this and need to get the external DSNs working. 

    Thanks again,

    -Melody

    Monday, October 7, 2013 3:25 PM
  • Just so I understand, if you use a SMTP client within your LAN to send e-mail to a non-existent address in an authoritative domain in your Exchange organization's "accepted domains" there's a NDR sent?

    Is the NDR sent if the sender's domain is not one of your authoritative "accepted domains"?

    Is the NDR sent only if the sender's domain is in your "accepted domains" list?

    How are you making the determination that no NDR is being sent? Is a NDR being sent but never being received? Are you looking at the message tracking logs? Are you looking at the SMTP protocol logs? Are you looking at a network monitor trace?

    BTW, it's normal to not see anything returned when you use the "Get-SystemMessage" unless you've created your own customize system messages. This has nothing to do with your organization not sending DSNs.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Monday, October 7, 2013 9:43 PM
  • Rich,

    If I send to a bad email address internally, example:  bademail@PeopleSystems.com, I get a the non-deliverable error.  If I send to the same bad email address externally, example: from my gmail, I do not get any thing back (tested this with other bad emails from gmail and I did).  This works for valid email addresses with over sized attachments as well.

    Our setup uses a single domain and it seems to only work if the sender is in the domain.  To see that no message is going back I look through our Barracuda, which we use to block spam.  I can see all of the messages going into Barracuda, but do not see any messages going back in response for external messages.  The consultant who setup our email indicated the same results when looking into the exchange logs.

    As for the "Get-SystemMessage", when I ran the "Get-SystemMessage -Original" command I saw that only internal messages were configured, so I setup custom external messages to see if that would fix it.

    Thank you for taking the time to look into this- is there any additional information I can provide?

    Many thanks,

    -Melody

    Tuesday, October 8, 2013 2:47 PM
  • Can you be more specific about what you see in the message tracking logs when a message reaches your HT server with a recipient address that doesn't exist in your directory?

    Just the sequence (in order of appearance) of "EventId", "Source", "Recipients", and "Recipient Status" for the message should be enough to see what's happening.


    --- Rich Matheisen MCSE&I, Exchange MVP

    Wednesday, October 9, 2013 1:50 AM