• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 547
  • Last Modified:

BH server generates NDR 5.1.1

Hi,
We have got a problem on one of Exchange Bridge-Head Server which is generating NDR 5.1.1 only for the users of another domain in the same forest. We have 3 BH Servers out of which we have issue with one BH Server. When users are sending email to a DL, the NDR generates randomly for different set of users at random instances. We have increased the diag. logging to maximum, but can not see any errors other than the NDRs. We have checked all the DCs as well and no issues.

Basic Infrastructure:
BH Server is in Domain A which is separate tree domain of the forest X. The users resides in Domain B which is a child Domain under the Root Domain X. The mailboxes resides on the mailbox servers of Domain A.

Only difference we can identify on this particular server that:
When we are searching some of the users of Domain B under Entire Directory on ADUC, it is not able to search the user. Whereas we are able search the same user when we specifically search the same user selecting the Domain B.

Urgent help is appreciated...
Thanks,
Sekhar
0
sekhar_kiit
Asked:
sekhar_kiit
2 Solutions
 
Satya PathakLead Technical ConsultantCommented:
Possible Cause:
The e-mail account does not exist at the organization the message was sent to. This issue may occur if there was a problem when users were moved between sites. For example, if a former Administrative_Group_1 user moves to Administrative_Group_2 and then replies to an old e-mail message, or if the user does not re-create his or her Outlook profile, an old Administrative Group style LegDN address will be used, and an NDR is generated.
The message was sent to obsolete personal address book entries.
The categorizer rejected delivery because you configured your SMTP contact with see comment SMTP RFC821 characters.

Reff..
http://www.petri.co.il/understanding-explaining-exchange-non-delivery-report-ndr.htm
0
 
sekhar_kiitAuthor Commented:
Thanks SatyaPathak for your valuable response.

We have identified the problem. The problem was with one of the GC on the root Domain X. The GC was not updating the replication data for the domain B and was having lingering objects. We have stopped the net logon service on this GC and now the email flow goes fine.

Cheers,
Sekhar
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

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