I believe you can ignore them... The messages are caused by misbehaving client programs. (Timeouts too low on the client side, I believe.)
> -----Original Message----- > From: Kai Lanz [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 13, 2005 8:38 PM > To: Subscribers of Qpopper > Subject: Broken pipe and timeout errors > > > We've just switched over to the new Qpopper v4.0.8; we were previously > using v2.53. Our server is an Alpha platform running Tru64 > v4.0G. In the > log file, I now notice lots of "Broken pipe" messages: > > Oct 13 16:48:55 geo-host popper[22043]: I/O error flushing > output to client > joeuser at my-mac-g5.Stanford.EDU [123.45.67.89]: Broken pipe (32) > > We get these about once a minute. Other messages logged by > the same popper > process, like "Servicing request", "POP login", and "Stats", > look okay. > > We also see timeout notices, though much less frequently: > > Oct 13 14:28:56 pangea popper[4268]: (v4.0.8-krb-V) Timeout > (120 secs) > during nw read from johndoe at pc17.yale.edu (98.765.43.21) > > What do these messages mean? Can we fix them? Can we ignore them? >
