At 4:18 PM +0200 5/16/02, Martin Kellermann wrote: >>> popper[]: I/O error flushing output to client blah at blah >>> [blah]: Operation not permitted (1) >>> >>> what does this really mean, and when will it occur? >> >> Client (remote machine) closed the connection, qpopper tried to >> write to the socket, but the TCP session was already closed by the >> kernel on the server in response to the close from the client. > > ok, sounds good :) thanks. > so i can safely ignore this messages, because the connection is ALWAYS > closed by the remote machine? > or can this error also be generated by a messed up local tcp socket or > another weird local problem?
It could be generated in response to some network problem, yes. Most likely it is just a client that closes the connection without sending 'quit'. > can i suppress the "-ERR POP EOF or I/O Error" (that occurs, for example > when client telnets port 110, logs in and then kills telnet session without > logging out) without patching the sources? Not currently.
