Exchange Server TechCenter >
Exchange Server Forums
>
Transport
>
Outgoing mail delayed in remote delivery queue for 20 - 80 minutes in Exchange 2007 SP1
Outgoing mail delayed in remote delivery queue for 20 - 80 minutes in Exchange 2007 SP1
- Outbound email is taking a very long time to leave the organization. Depending on load, it seems, the delay can be 20 - 80 minutes. Even late in the day, when most people have left, there can still be 15 items in the queue, some of which have been there for greater than 20 minutes. Inbound email appears unaffected. We have a very simple architecture and no configuration changes have been made in quite some time. The problem seems to have appeared out of no where, but obviously something caused it.
We have two non-Exchange edge servers. Below that we have two Exchange 2007 SP1 hub transport servers. There are redundant paths to and from each of these servers. Below that we have one Exchange 2007 SP1 mailbox server and two E7SP1 client access servers. On each hub server, we have two connectors--one for each edge server, for a total of four connectors. The purpose is so I can shut down a channel, if I need to do maintenance. I have enabled verbose logging on all four connectors.
There are no errors in the event viewer. In all the Exchange logs I've seen, it appears when the messages are finally picked up and transported to the edge servers, they reach their final destination within a minute or so (even halfway around the world). All the logs on the edge servers show that as soon as a message becomes known, it moves quickly. This suggests the problem is on the hub transports, but I'm open to the idea that the edge servers aren't accepting messages quickly, so they queue up on the hubs.
I've restarted services, rebooted services, rebuilt the apps on the edge servers, changed added patches on the edge servers, rolled back patches on the edge servers... I'm still left with this problem. I read about PipeLineTracing and thought I enabled it, but I never saw that folder created. I was hoping to enable it for myself and watch a message travel. Is that a good idea? What's the best way to determine where messages are being held up and why? I don't consider myself an Exchange master, but I do think I know my way around pretty well and I'm at a loss.
I'd be happy to provide any requested information, but I didn't want to unload too much in an initial request. Any help would be greatly appreciated.
-Tim
Answers
- Problem was OfficeScan client running on the server. Not sure why Trend support didn't investigate that. I was on the phone with them for hours. OSCE had previously been running for years. It may have been updated recently.
- Marked As Answer byTim Ahearn Thursday, October 29, 2009 5:29 PM
All Replies
- Problem was OfficeScan client running on the server. Not sure why Trend support didn't investigate that. I was on the phone with them for hours. OSCE had previously been running for years. It may have been updated recently.
- Marked As Answer byTim Ahearn Thursday, October 29, 2009 5:29 PM
- Hi,
Thanks for your sharing.
Allen
