At 10:00 AM -0500 4/18/01, Michael Smith wrote:
> I'm still running LX4.0b16 (I know...upgrade), however, I'm seening
> some oddities on the spool files. First we are getting complaints from
> some customers that they are having problems retrieving their email.
> That it gets "stuck" when trying to retrieve certain messages, and
> always the same message. They seem to be showing up in the logs with
>
> Timeout (120 secs) during nw read from user at x.x.x.x (x.x.x.x)
> user at x.x.x.x (x.x.x.x): -ERR POP timeout from popserver.com
This may be a combination of congestion in your network, small
timeout values in the clients, and Qpopper 4.0's default behavior
of aggregating small network writes into a large one. You can
adjusting 'chunky-writes' and see if this makes the problem go
away. See the FAQ entry at
<http://www.eudora.com/qpopper/faq.html#timeout>. Note that you
can set chunky-writes per-user if you like.
> Now the odd thing is, we are running in server mode, so the spool should
> not be updated with X-UIDL or Status.
Server mode is orthogonal to updating the spool with Status: and
X-UIDL. See the GUIDE.pdf file for details.
> For the most part this seems
> to be how it is opperating. No spools are being re-written with the
> Status line, however the customers reporting problems are having their
> spools rewritten with the X-UIDL lines.
Why would adding X-UIDL lines cause a problem?
> Anyone have any thoughts or suggestions. I'm still trying to get
> our tech people to get more information on these customers, like
> what client they are using
My guess is Outlook or Outlook Express, because of the small
timeouts by default. If you run packet traces during the problems
you may see dropped and retransmitted packets during the time
period.
