Message delay between Exch 5.5 and Exchange 2003

[lbicher]

Hello All,
I have a problem I hope you all will be able to help me with. I am in the middle of a project to migrate users from Ex 5.5 to Ex 2003. I have the Ex 2003 server installed and the IT department's mailboxes have already been migrate. There was no problem with the mailbox move or logging in the next day.
We have discoverred today that there are times that messages going from the Ex 5.5 server are held up in the MTA queue for a little while, so far for up to 20 minutes. It isn't all the time and so far I can not see anything in the event logs that would correspond to this.
The Ex 5.5 server is at SP4 and is running on W2k Server, SP4. The Ex 2003 is at SP1 and is running on W2K3.
Thanks in advance.

 

[lbicher]

Here is some more information that I have gatherred regarding the problem I am having. It is still happening but I have found that if a message is sent from teh Ex 2003 server to the Ex 5.5 server, all messages queued up for delivery from 5.5 to 2003 are then transferred immediately.

 

[zbnet]

Are the servers in the same site, or different sites?

 

[lbicher]

zbnet,
They are in the same site.

 

[msinger]

I'm having the exact same problem, and so far haven't been able to find any explanation.

 

[lbicher]

I wish I could say I had an answer, but I still don't know what the cause is. Since I can jumpstart the process by sending an e-mail from 2k3 to 5.5, my workaround was to create a script that sends an e-mail from the 2k3 server to a mailbox on the 5.5 server every 5 minutes. That has been working, although I realize it is a work-around and not a solution. I am fortunate that I am almost done with my migration and will be retiring my 5.5 server very soon.

 

[lovalles]

i have same problems every user has an internal and a external pop3 account, sometimes more that one.

Before they didnt have to select the account to use, now with the 2003 if we fordwar an external email to internal account it will be sent throw pop3 and it wont be reachable.

Is there a solution to work this around?