Link to home
Start Free TrialLog in
Avatar of ptuttle1319
ptuttle1319Flag for United States of America

asked on

exchange 5.5 - 2003 migration - mail routing setup

I'm a little confused at the moment. We are in the middle of an exchange 5.5 to 2003 migration. 2 exchange 5.5 servers, 1 exchange 2003 server. 1 site, all servers are on the same LAN.  Most of the mailboxes are now on the 2003 server, there are about 250 mailboxes still on the exchange 5.5 server (one of the 5.5's does not have any mailboxes) the other 1400 are on the 2003. In between now and when I move the rest of the mailboxes, and finally make the switch over to 2003 completely, how can I tell how the mail routing is setup, ie which box is sending all the mail. Also, how can I set it up to where the exchange 2003 server is the one sending all the mail. I never see any of the messages hit either of the queue's (on the 2003 or the 5.5) and I am trying to implement a spam appliance, where I will use it as a smart host, sending all messages to the appliance from exchange 2003. Let me know what info I should provide.
ASKER CERTIFIED SOLUTION
Avatar of ocon827679
ocon827679
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ptuttle1319

ASKER

Is there some way, in the current configuration, to actually track a message, and see if it has gone out a queue? I just have the mail server pointed directly out to the internet.
In E2K3 there is the Message Tracking tool in the administrator console.  You  can track the message until it leaves your network.  Once off the network, it on its own.  Exchange 5.5 has logs that can be used to track a message, but I have never tried using them, so I don't know the process to determine what has happened.  Articles that I saw on it a while back made it look like you would be perusing the logs to detrmine what happened to the message.