M
Milhouse Van Houten
I've noticed a curiosity with OL2007 final:
Upon OL startup (and only then), and only when there's mail waiting, the
usual automatic delivery of POP3 doesn't happen. Instead this shows in the
lower-right part of Outlook almost immediately (it's not timing out since
it's so quick):
Task 'Main - Receiving' reported error (0x800CCC0F) : 'The connection to the
server was interrupted. If this problem continues, contact your server
administrator or Internet service provider (ISP).'
However, if I then immediately hit F5 to deliver, the mail comes right down
(I'm on a fast connection). Furthermore, it'll never happen again until the
next time I start OL with mail waiting. Dozens of automatic deliveries a day
work fine.
Looking it up, I came here (http://support.microsoft.com/kb/813514), but
I've accounted for those things (no AV, firewall, etc), and nothing's
changed from my previous setup a day ago anyway (B2TR, and before that B2),
which didn't show the problem.
Anyone else seeing this? It's pretty minor, but it appears that OL is
getting ahead of itself when started up.
Upon OL startup (and only then), and only when there's mail waiting, the
usual automatic delivery of POP3 doesn't happen. Instead this shows in the
lower-right part of Outlook almost immediately (it's not timing out since
it's so quick):
Task 'Main - Receiving' reported error (0x800CCC0F) : 'The connection to the
server was interrupted. If this problem continues, contact your server
administrator or Internet service provider (ISP).'
However, if I then immediately hit F5 to deliver, the mail comes right down
(I'm on a fast connection). Furthermore, it'll never happen again until the
next time I start OL with mail waiting. Dozens of automatic deliveries a day
work fine.
Looking it up, I came here (http://support.microsoft.com/kb/813514), but
I've accounted for those things (no AV, firewall, etc), and nothing's
changed from my previous setup a day ago anyway (B2TR, and before that B2),
which didn't show the problem.
Anyone else seeing this? It's pretty minor, but it appears that OL is
getting ahead of itself when started up.