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
Now the odd thing is, we are running in server mode, so the spool should
not be updated with X-UIDL or Status. 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.
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 and still trying to find one with
an active issue. The tech department is currently just
deleting the offending message from the spool and sending the
customer on their merry way. I'll post more info when
I can get them to stop doing that.
--
Michael Smith ... We build e-business infrastructure solutions
SysAdmin, DataFoundry.net ... www.datafoundry.net
