Exchange & GroupWise

[timmoat]

Continuing to test out a phased migration from GroupWise to Exchange and have a question i'm hoping someone can answer.

If I send an email from a GroupWise user to an External Hotmail user, and CC an Exchange user when the hotmail.com user receives the email the Exchange user appears as:

name.first administrative group.exchange

as opposed to the Internet address. This of course is useless for the period of interop between the two systems!

I'm following the Exchange.Org guide, and have the GW API and Exchange Connectors working well.

Does anyone know a way around this?

 

[terry712]

there isnt

the api and connector are crap at this.

i assume that groupwise user straight to outside is ok as it's going via gwia

but as you have a cc to get to exchange it's routing via connector and hence the funny address

all messages coming in hitting exchange smtp and gwia just out ?

 

[timmoat]

I hadnt even started playing with inbound at this stage. In previous tests I had inbound into Exchange which worked well although HTML was stripped out in that direction.

I decided against the whole co-exist thing. The tools just are not up to it and there are to many issues/bugs with each approach.

Its only 65 users so I'm going to provision new mailboxes and then post-fill them with around 1 months emails using Quest and archive the rest to PST which will then be uploaded to our 3rd party Email Filtering. This also means we do not need to have a temporary Exchange 2003 box in the mix overcomplicating matters. We are moving to a new AD environment so this can be done as phase one, and then Exchange can be done a few weeks later at the weekend. Much easier for Internet bound mail as its simply the firewall forwarding which needs to change.

I had conerns about moving everyone at once to a new box as email is so mission critical but our email filtering actually provides 30 days business continuity so if it does all go tits up then users can still access their work email and send which to the recipient is seamless.

 

[xmsre]

Third part tools are the way to do this cleany. I used to use Wingra, now owned by Quest. Seriously, look into the Quest migration tools.