A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients

We have some distribution groups in our AD. These groups includes many individuals. Some individuals are users in AD, some are contacts in AD.

Recently (on sporadic occassions) when users send an e-mail to these groups they encounter error messages such as...

comdev@bcf.org on 3/21/2007 10:18 AM

A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients.  Contact your administrator.The MTS-ID of the original message is:c=us;a= ;p=BCF-Exch;l=BCFEXCHANGE-070321141716Z-2373.

MSEXCH:MSExchangeMTA:First Administrative Group:BCFEXCHANGE

The message goes thru ok (we have confirmed on occassion with a few of the intended recipients), but the message does appear.

Any ideas?
bnrtechAsked:
Who is Participating?
 
EE_AutoDeleterCommented:
bnrtech,
Because you have presented a solution to your own problem which may be helpful to future searches, this question is now PAQed and your points have been refunded.

EE_AutoDeleter
0
 
bnrtechAuthor Commented:
This is sort of spooky. This is the first time I have posted a question and no one has responsded. Should I close the question or maybe reassign it more points?
0
 
bnrtechAuthor Commented:
Well I should have known there was a reason that the Expert Exchange forum was not getting back to me...because this one was a weird one. I had a credit from Microsoft so I caved in and called support. Told them the I tried all the prescribed options to resolve this matter and nothing worked. The support guy went thru the diagnostic process and confirmed that the usual suspects were ok.

After further review we went in to System Manager. Drilled down the ADMINISTRATIVE GROUPS -> FIRST ADMIN GROUP -> FOLDERS -> PUBLIC FOLDERS (right click and view system folders) -> OFFLINE ADDRESS BOOK -> FIRST FOLDER (long awkard folder name) -> reviewed each of the OAB folders. Went in to PROPERTIES of each OAB folder and reviewed the REPLICATION tab. Discovered that the OAB VERSION 2 folder was not set to replicate with Exchange Server. We set up the necessary replication and problem was solved

Hope this helps someone else down the road

Please close this question. Thanks.
0
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.

All Courses

From novice to tech pro — start learning today.