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 ?
LVL 3
vindenAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.