Exchange 2010 internal non-delivery reports question

We are currently looking at changes to the recipient filtering on our email gateway to simply drop incoming emails from the internet that are going to an invalid recipient.  it's a new gateway, and we thought it was configured to drop invalid recipient messages.  Researching that issue led me to a question I thought would be simple, but haven't found any documentation.

In looking at the Remote Domain settings in Exchange 2010, under Organization Config, Hub Transport, Remote Domains,  Default, I see the checkbox to uncheck, or select, to allow NDRs to external domains.  So, silly me, when I right clicked to view the Properties under the Accepted Domains, I expected to see similar setting choices about delivery reports, non-delivery reports, out of office notificiations etc that could be selected and disabled (I don't know why someone would, but...), but there are none.

I don't see a need disable such things for internal mail in an Exchange organization, but I was getting some questions from a manager who was worried that if we adjust any settings to Remote Domains,, like disable NDRs, that INTERNAL senders would not receive an NDR if they manually type in an INTERNAL recipient address that is misspelled.    I assured him the Remote Domains doesn't affect internal NDRs already, but in looking at all these settings I started assuming NDRs, delivery reports, Out of Office notices appear to all be on by default and also are not manageable internally - but I can't find any documentation that clearly states such.  

And so my question:  "Would there ever be a need where one would even want to adjust internal NDRs, DR, and Office notifications on an internal mail organization, and if so, is there somewhere in Exchange 2010 that one would do such?"  I don't see a need, but my Exchange experience is limited.

As stated I don't see a reason or a need myself.  I'm also not finding any docs that state something like "NDRs or Office notifications are always "on" for internal mail exchanges.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Simon Butler (Sembee)ConsultantCommented:
Recipient filtering on Exchange 2007 and higher is part of the anti-spam filtering. However if you have a gateway in front of Exchange that actually accepts the email (rather than just pass the traffic through) then that should be doing the filtering.

The NDR settings within Exchange should be left alone.
A lot of people think it helps spammers, it does not, because they don't see the messages.
If you change the settings then legitimate senders will not always get non-delivery reports which can mean that important emails are lost.

If internal people send to an invalid recipient, then the message should bounce immediately no matter what the setting because Exchange will be unable to resolve the recipient. Do you have users manually entering addresses? Most people will select from the GAL.


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
DarthywAuthor Commented:
Thanks Simon.  That's pretty much what I thought.  Most folks email from the GAL, so manual messages aren't and issue, and I've seen those bounce back when a bad internal address is manually typed in as recipient.

My current plan all along is to simply set the gateway in front of our email servers to drop mail incoming for invalid recipients, and not mess with disabling the NDRs on our remote domain.  Our security admin seems too focused on the NDRs being turned on or off, when the recipient filtering should do all we need.
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

From novice to tech pro — start learning today.