Skip to main content

NDR for non-existent domain (5.4.4)

By default, NDR (5.4.4) of an email sent to a user with non-existent domain is sent to postmaster's mailbox. If you want your users to get NDR when they send email to a wrong email address (domain in this case), you need to remove 5.4.4 code from Transport Configuration.

In Exchange 2010:


  • go to Organization > Hub transport > Global settings > Transport settings
  • remove code 5.4.4 from the list


In Exchange 2013/16

  • Get-transportConfig to check settings
  • Find GenerateCopyOfDSNFor and the codes (if 5.4.4 is on the list)
  • Example: {5.4.8, 5.4.4, 5.4.6, 5.2.4, 5.2.0, 5.1.4}
  • Copy ALL codes (from bracket to bracket)
  • Paste into Notepad
  • Remove 5.4.4 from the list (remove 5.4.4, )
  • Set-transportConfig -GenerateCopyOfDSNFor "5.4.8, 5.4.6, 5.2.4, 5.2.0, 5.1.4"
Users will get NDR immediately.

Labels:

Comments

Post a Comment

Popular posts from this blog

Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}]

 If you got this error checking the mail flow for a distribution group, it means the distribution group is closed and only internal senders can send e-mail to this group. When outside user sends e-mail to this group you get  Reason: [{LED=250 2.1.5 RESOLVER.GRP.Expanded; distribution list expanded};{MSG=};{FQDN=};{IP=};{LRT=}] Set Delivery for this group to internal and external users and your problem will be solved. 
Read more

Netscaler vs Exchange 2019 "time out during ssl handshake stage

If you are using Citrix Netscaler as load balancer in front of Exchange 2019 server you must know this: Microsoft Exchange 2019 is secured by default and allows only TLS 1.2. Therefore default schannel settings are as follows (using IISCrypto tool from Nartac Software): While Citrix Netscaler offers following Cipher Suites: TLS_RSA_WITH_AES_256_CBC_SHA TLS_RSA_WITH_AES_128_CBC_SHA TLS_DHE_RSA_WITH_AES_256_CBC_SHA TLS_DHE_RSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_DES_CBC_SHA TLS_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 TLS_DHE_DSS_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT1024_WITH_DES_CBC_SHA TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA TLS_DHE_RSA_WITH_DES_CBC_SHA TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA TLS_RSA_EXPORT1024_WITH_RC2_CBC_56_MD5 TLS_DH_anon_WITH_DES_CBC_SHA TLS_DH_anon_WITH_AES_128_CBC_SHA TLS_DH_anon_WITH_AES_256_CBC_SHA TLS_DH_anon_EXPORT_WITH_DES40_CBC_SHA Now, you will fi...
1 comment
Read more

Apple iPhone Text responses go to wrong country code

A user wrote: Recently I went to Portugal and when I was there I bought a sim card and put it in my iPhone 11 Pro, with my primary e-sim still in it. When I got home to Australia, I deactivated the Portugal sim-card, deleted it and took the sim card out. Now when someone call me I respond with text, my iPhone changes the calling numbers country code to +31. I had the same problem. Despite turning "Dial assist" on/off, checking Country, Language and all the suggested stuff it did not work for me. What I did at the end was deleting country prefix from contact numbers --> Save --> Added country prefix again . It works now.
Post a Comment
Read more