I'm afraid that I don't have any solution but I too have been seeing this problem for about a year now. I've noticed that several other people have also posted emails regarding this same problem.
What I've discovered with this problem is that it does not actually appear to be a qpopper problem or even a openssl problem. I believe that it is actually an Outlook problem. I'm guessing that you are using Outlook 2000 because I get the same problem often. What I've noticed is this: 1) The problem is ssl related because when I get the error, I can still retrieve the email if I try using non-ssl. 2) I have several MUA's on the same computer with the same network connection and even though I get the error with Outlook, I can still retrieve email with Eudora, Mozilla, etc. 3) I can replicate this problem more consistently when the Outlook client is not on the same segment as the qpopper server. 4) I've called Microsoft about it but they were unwilling to help me, since I was using qpopper. An interesting thing I noticed was that if I flood the Outlook client with network traffic and simulate congestion on that segment with something like a ping -f outlookclient, the email will slowly start to work. LOL. Although, it's not a great solution, you can always try a different MUA. Paul. Keith Smith wrote: > All: > > I have been using SSL/TLS encryption with success for a while now, > however just today, I tried to receive a piece of email from my > mailbox which was about 20MB in size. The POP server returned the > following error on each attempt. The only way around this was to > retrieve the message without using SSL (i.e. in the clear). > > My mail client is outlook. Any idea why this error might be > occurring? I am directly connected to the pop server over a dedicated > 10M Ethernet, so no traffic issues. Is there a file size limit in > OpenSSL? I noticed that the mailbox was successfully copied to the > temp file before the errors appeared. Lots of disk space available on > the server too, my client timeout is set to a minute (not the > issue).... thoughts? > > Thanks > Keith > > May 5 15:50:59 mcleod popper[32153]: (v4.0.3) POP login by user > "fire_ksmith" at (192.168.0.2) 192.168.0.2 > May 5 15:51:02 mcleod popper[32153]: I/O Error > May 5 15:51:02 mcleod popper[32153]: Error writing to client > May 5 15:51:02 mcleod popper[32153]: fire_ksmith at 192.168.0.2 > (192.168.0.2): -ERR SIGHUP or SIGPIPE flagged > May 5 15:51:02 mcleod popper[32153]: OpenSSL Error during write > May 5 15:51:02 mcleod popper[32153]: ...SSL error: error:1409F07F:SSL > routines:SSL3_WRITE_PENDING:bad write retry > May 5 15:51:02 mcleod popper[32153]: Error writing to client > May 5 15:51:02 mcleod popper[32153]: fire_ksmith at 192.168.0.2 > (192.168.0.2): -ERR POP hangup from mcleod.firesnacks.com > May 5 15:51:02 mcleod popper[32153]: OpenSSL Error during write > May 5 15:51:02 mcleod popper[32153]: ...SSL error: error:1409F07F:SSL > routines:SSL3_WRITE_PENDING:bad write retry > May 5 15:51:02 mcleod popper[32153]: Error writing to client > May 5 15:51:02 mcleod popper[32153]: Stats: fire_ksmith 0 0 1 > 22750638 192.168.0.2 192.168.0.2 > May 5 15:51:04 mcleod popper[32153]: OpenSSL Error during write > May 5 15:51:04 mcleod popper[32153]: ...SSL error: error:1409F07F:SSL > routines:SSL3_WRITE_PENDING:bad write retry > May 5 15:51:04 mcleod popper[32153]: Error writing to client > May 5 15:51:05 mcleod popper[32153]: (v4.0.3) Timing for > [EMAIL PROTECTED] (error) auth=0 init=8 clean=2 >
