Nasty Co-existence Issue Exchange and Groupwise
Nasty Co-existence Issue Exchange and Groupwise
Author
Discussion

GregE240

Original Poster:

10,857 posts

297 months

Thursday 19th May 2005
quotequote all
Can someone help with this?

Got a customer who is migrating from Groupwise - Exchange.

In order to speed things up, it is been suggested that the Groupwise distribution lists be recreated in Exchange. This means that they will contain (during co-existence) both Groupwise and Exchange contact details. Synched the new group over via the Connector.

So we've set a test group up, as per the above. From Exchange (well, Outlook), no worries, the message goes to both Exchange and Groupwise recipients, but from Groupwise, the message goes to Exchange users okay, but we are seeing non-deliverable messages for the Groupwise users?

Any ideas? I think the problem lies at the Exchange end...but theres not much to configure.

Cheers,
Greg

BliarOut

72,863 posts

269 months

Thursday 19th May 2005
quotequote all
First thought, got any headers to see which server is rejecting it? (Tricky to tell from the post)

I'm just off out of the office, but if no-one replies, bump the thread tomorrow or mail me through the profile and I'll see if I can assist.

A bit of background on the connectors and Ex/GW versions might be useful...

Oh, and turn diagnostic logging up to the max on all the connectors in Ex and trowel through the event log, that might tell you what you need to know.

GregE240

Original Poster:

10,857 posts

297 months

Friday 20th May 2005
quotequote all
OK, header is as follows:

Your message did not reach some or all of the intended recipients.

Subject: Test 2 - GroupWise to Exchange
Sent: 5/19/2005 15:01:00

The following recipient(s) could not be reached:

POST OFFICE LOCATION.POST OFFICE NAME.DIST_GROUP 5/19/2005 15:01:00
Message cancelled because it was looping through the network [MAPI Reason Code: 1, MAPI Diagnostic Code 3]
c=GB;a= ;p=Customer;l=FB296A625D8D8F4AA94F78750B45433B

POST OFFICE LOCATION.OTHER POST OFFICE NAME.ADMIN ID 5/19/2005 15:01:00
Message cancelled because it was looping through the network [MAPI Reason Code: 1, MAPI Diagnostic Code 3]
c=GB;a= ;p=CUSTOMER NAME;l=FB296A625D8D8F4AA94F78750B45433B


It seems like the message is going from Groupwise - Exchange okay (because the Exchange members of the group receive the mail okay). From there I'd have thought Exchange would see there are two GW users in the group, and send the messages back over the Connector to be resolved by Groupwise. It seems Groupwise is having trouble with this?

Thanks in advance for any help.

Greg

BliarOut

72,863 posts

269 months

Friday 20th May 2005
quotequote all
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q195055

Although it relates to Notes it looks suspiciously like the culprit. Can you adapt that solution to the groupwise connector?

GregE240

Original Poster:

10,857 posts

297 months

Friday 20th May 2005
quotequote all
Thanks, will have a look at the .ini file and see what can be done.

Greg