Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1152
  • Last Modified:

Configuring DSNs in transport settings

Hi,

I'd like to know a common way to configure "transport settings" properties in Exchange 2007. More specifically I would like to hear how to configure the option "enter the DSN codes. DSN messages that have these DSN codes will be forwarded to the Microsoft Exchange Recipient" on the tab "message delivery".
For some reason we are not receiving DSN messages when we mail something to users in other companies that don't exist. I think it might be cause the above setting is configured badly.

Right now I have only the following codes in that setting :

5.1.1
5.1.4
5.2.0
etc.

Or is there a way to enter all possible DSN codes ?
0
vinden
Asked:
vinden
  • 2
1 Solution
 
rr1968Commented:
Sometimes it's too much of a hassle when you try to monitor all DSN's.
In our servers, we have:
5.1.4
5.2.0
5.2.4
5.4.4
5.4.6
5.4.8
You can review this link.
http://www.petri.co.il/monitor-exchange-2007-non-delivery-reports-ndr.htm

0
 
vindenAuthor Commented:
Ok thanks.
Apparently I did configure DSNs correctly. Which still leaves me wondering why we are not receiving "no such user" DSNs. Any ideas ?
0
 
vindenAuthor Commented:
update :

i've been able to find traces of non-delivery reports with "no such user" on our Edge server (using message tracking). For some reason it has a column SourceContext with value "failure" on every NDR with "no such user". I can't find a trace of these messages on the Hub transport server. Something is going wrong with these messages on the Edge server.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now