I have qpopper 4.0.3 running from inetd on an alternate port and using OpenSSL. Some users seem to be able to connect fine, but others are having intermittent problems. One in particular is using the latest Eudora, and sometimes when she tries to get mail I see a string of errors in the logs. For instance:
Dec 11 07:56:14 fiat qpopper[30455]: (v4.0.3) TLSv1/SSLv3 handshake with client at dial-xx-xx.ots.utexas.edu (128.83.xx.xx); new session-id; cipher:DES-CBC3-SHA (DES-CBC3-SHA SSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1), 168 bits Dec 11 07:56:15 fiat qpopper[30455]: (v4.0.3) POP login by user "someone" at (dial-xx-xx.ots.utexas.edu) 128.83.xx.xx Dec 11 08:05:09 fiat qpopper[30455]: I/O Error Dec 11 08:05:09 fiat qpopper[30455]: Error writing to client Dec 11 08:05:09 fiat qpopper[30455]: someone at dial-xx-xx.ots.utexas.edu (128.83.xx.xx): -ERR SIGHUP or SIGPIPE flagged Dec 11 08:05:09 fiat qpopper[30455]: OpenSSL Error during write Dec 11 08:05:09 fiat qpopper[30455]: ...SSL error: error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry Dec 11 08:05:09 fiat qpopper[30455]: Error writing to client Dec 11 08:05:09 fiat qpopper[30455]: someone at dial-xx-xx.ots.utexas.edu (128.83.xx.xx): -ERR POP hangup from fiat.gslis.utexas.edu Dec 11 08:05:09 fiat qpopper[30455]: OpenSSL Error during write Dec 11 08:05:09 fiat qpopper[30455]: ...SSL error: error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry Dec 11 08:05:09 fiat qpopper[30455]: Error writing to client Dec 11 08:05:09 fiat qpopper[30455]: Stats: someone 0 0 27 3898866 dial-xx-xx.ots.utexas.edu 128.83.xx.xx Dec 11 08:05:09 fiat qpopper[30455]: OpenSSL Error during write Dec 11 08:05:09 fiat qpopper[30455]: ...SSL error: error:1409F07F:SSL routines:SSL3_WRITE_PENDING:bad write retry Dec 11 08:05:09 fiat qpopper[30455]: Error writing to client So a TLS login seems to go OK, but then almost 10 minutes later, there's an IO error. Now, looking at the FAQ, I suspect this may be solved by changing the chunky write option, but the FAQ suggests setting it to TLS. Since my problem occured while using TLS, I've changed it to never. So, the questions are: 1. Is this a network congestion problem or something else? and 2. Is setting chunky-writes to never a good idea or am I inviting other problems by doing this? Thanks for any insight, and feel free to ask for more info if that would help. -- Public key #7BBC68D9 at | Shane Williams http://pgp.mit.edu/ | Systems Administrator UT-GSLIS =----------------------------------+------------------------------- All syllogisms contain three lines | [EMAIL PROTECTED] Therefore this is not a syllogism | www.gslis.utexas.edu/~shanew
