Software

Ask something
Question Locked

Exchange 2007 Migration

0 helpful
4 replies

by jallen

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm planning a migration from our simple SMTP-based solution (IPSwitch IMail) to Exchange 2007. The migration process will be slow, so both mail systems will need to be accessible at the same time, sharing the same domain space.

Let's say Joe@company.com is already on Exchange, and wants to send an email to sally@company.com, who is on IMail. How do I set up Exchange so that it first checks for the existence of sally's mailbox in Exchange, and if it doesn't find it, it sends the mail to IMail for delivery?

At first, I thought Internal Mail Relay was the answer, but after more reading, this is apparently only for email coming *from* the Internet.

4 replies

by jallen

Turns out Internal Mail Relay was the answer! When I tried to get it working last time, I was still getting NDR's. This was because I was testing with a mailbox that I had deleted from Exchange (guess there were still some remnants there)...when I tested with an email address that had never been set up on Exchange, it worked.

by dcole_cody

Would you mind if I asked what you did in more detail? I have IMail and moving to Ex 07 and have the same issue. Plus any else you may have run into since then would be great.
Thank you for any help

by jallen

For our company:

- Our email domain is company.com
- Our new AD domain is corp.company.com

Let's say user "juser@company.com" needs to be migrated from IMail to Exchange. In IMail, we go into his account, and set up a forward to "juser@corp.company.com". So any mail destined for "juser@company.com" is basically forwarded to his Exchange account. We configured Exchange to basically listen on both "company.com" and "corp.company.com" with the former being relayed back to IMail. Once we get all users on Exchange, we'll change the external MX record to point to Exchange.

The biggest downside of doing it this way is the double-account maintenance -- Since all mail is still going through IMail, every user will need both an IMail and an Exchange account. Another downside revolves around permissions with mailing lists.

As many details as I can remember are below:

In Exchange:
1. Since our AD domain is corp.company.com, that is the default SMTP address it tries to use -- I changed the default to be simply "company.com", BUT I left "corp.company.com" as a secondary SMTP address.
2. Set up a "Send Connector" from our Hub Transport server to our external SMTP server (in our case, our spam filter - both IMail and Exchange are using it for sending external mail).
3. Also under the "Hub Transport" node, configured "company.com" as an "Internal Relay Domain".
-- Exchange is now relaying "company.com" mail to our external SMTP server

In IMail:
1. For each account, simply set up a forward to the "corp.company.com" address.

This discussion is closed to new replies.