On Thu, Jul 15, 2004 at 08:47:49PM +0200, Aymeric MUNTZ wrote: > I got an error using qpopper with outlook as client. > I often got the error : > "A time-out occurred while communicating with the server. Account: > 'Aymeric', Server: 'pop.toto.com', Protocol: POP3, Port: 80, Secure(SSL): > No, Error Number: 0x800CCC19" > > On the qpopper server side, I got the error: > Jul 15 19:48:36.887 2004 [2041] new child for connection > Jul 15 19:48:36.887 2004 [2041] Set downcase-user to true > Jul 15 19:48:36.887 2004 [2041] Set server-mode to true > Jul 15 19:48:36.887 2004 [2041] Set timeout to 120 (0x78) > Jul 15 19:48:36.888 2004 [2041] Set chunky-writes to TLS (1) > Jul 15 19:52:38.359 2004 [2041] aymeric_home at pop.thrruss.org > (81.56.220.170): -ERR POP EOF or I/O Error > Jul 15 19:52:38.359 2004 [2041] Stats: aymeric_home 0 0 1 2774043 > pop.thrruss.org 81.56.220.170 > Jul 15 19:52:38.408 2004 [2041] exiting after Qpopper returned
Notice how the error is almost exactly 4 minutes after the connection opened? Outlook's "server timeout" option is probably set to 4 minutes. Increasing the timeout setting will help. I think Outlook will let you set it as high as 10 minutes. This can happen if you have anti-virus software that does transparent POP3 mail scanning. Norton 2003 and 2004 do this, and others probably do as well. They hook into the networking code of Windows and intercept all traffic on port 110/tcp so anything resembling an email message can be scanned. The problem is, they don't communicate anything to Outlook while the message is being downloaded and scanned, so as far as Outlook can tell, the server has stalled. Outlook eventually it just gives up, and you get the time-out error. Qpopper sees the EOF error because Outlook has abruptly terminated the connection. -James
