Hi Ken, Yes i would like the patch sent to me. or can i simply insert the usleep command in the right place and recompile?
Err, developers of qpopper, how easy would it be to add a option in the config file to allow this to happen? sleep = x (ms) or something very simple. then in the FAQ add a thing that says Outlook XP is a pile of crud: you need to do this to get around the problem. (or is it already there and i'm an idiot and can't read the manual properly?) :) any thoughts ppl? ta Matt -----Original Message----- From: Ken Lalonde [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 1:44 AM To: [EMAIL PROTECTED] Subject: Re: Outlook XP timeout issue with 4.0.5 Here's what I did about it: > From: Ken Lalonde <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: Re: I/O error flushing output to client > Date: Tue Feb 4 13:47:43 2003 > > We saw this problem fairly frequently. The clients in question > were running Outlook XP, connecting to a qpopper-4.0.4 server > on the same very lightly loaded LAN. Diddling with chunky-writes > or Outlook's timeout values did no good. > > A google search pointed to a bug in Outlook XP (shocking!), > wherein Outlook gets confused if the server responds "too quickly". > See the "I frequently get a timeout" question at: > http://www.workgroupmail.com/faq_area.asp?area=Client%20Setup&id=34 > and: > http://home.hetnet.nl/~ojb-hamster/EnWIP/EnWeb/html/faq18om.htm > > The URLs above both suggest configuring the server to > pause for 50ms between POP commands. I changed qpopper to do that, > which boils down to a "usleep(50*1000)" call in popper.c, > just before the pop_get_command() call. > > Haven't seen the problem since. > > I can provide a patch on request. > > Cheers, -- Ken Lalonde, Global Remittance Network, Toronto
