asked on

Delayed email delivery

I am having delayed emails to all our clients. Are setup is Exchange 5.5 with serice pack 4, NT 4.0 SP 5, NAV mse 2.1. The mail that arrives at the clients desktop cannot be viewed until the user interacts with outlook. Then 3 or 4 emails come at once. We were seeing this problem when we were running mapi/vapi in norton but after switching back to mapi only the problem disappeared forward a few weeks now it has retuned. This leads me to believe that it is not norton related. Has anyone got a clue?

ASKER CERTIFIED SOLUTION

bluezoo7

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SunBow

You might compare intranet vs internet receipts, and mail format/attachments (conversions that may be necessary). Ours has Norton on a server in front of exchange that always delays incoming mail, usually based on quantity in queue, not on time for delivery. Its clock is goofy (not on time) so results can be deceptive.

We have Norton on PC as well. It slows machines down, and breaks nearly every install, but I don't see it slowing down eMail like that. Or how it would.

I suggest it (slowdown) is between Exchange and your firewall. What else is gateway doing? etc.

SunBow

ditto bluezoo7 on the abhorrent timestamp behavior. Obviously something wrong, and in my case, I found Norton on server a prime culprit. Same for viruses (ditto). Either they are stopped at firewall or they get through (as new) everything.

I don't see tuning NT as helpful in this case, except, one should have general rule to not try to run every application on one NT server, rather - try no more than one per server, and things run better. If you using same server to share printing and other files, well, uh, consider alternatives.

Printing to HP printers directly, using IP and Jetdirect, running JetAdmin, is really not such a bad deal, free up your print servers, they more often provide more pain than value (IMO for Netware as well as for NT).

bluezoo7

Check to be sure your not doing this:

http://support.microsoft.com/support/kb/articles/Q263/9/24.ASP

rlarrea

ASKER

We tried your suggestion but we also reinstalled the winsock proxy client. One of these two methods worked but we don't know which. And since it is working fine I am not going to find out.

rlarrea

ASKER

Our problem seems to have reared it's ugly head again. There have been no changes to the box except the new virus defs from yesterday.