At 1:04 PM +0100 9/2/02, Trey A Mujakporue wrote: > When downloading files with SSL enabled, we get this error in the logs > This is not a chunky write problem as my qpopper configuration file is made > up of the following > > set tls-support = alternate-port > set tls-server-cert-file = /etc/mail/certs/cert.pem > set chunky-writes = always
There really isn't a "chunky write problem" but it is true that if your network is already congested, having chunky-writes set to any value other than "never" could exacerbate the situation and lead to timeouts. The way to check this is to try setting chunky-writes to never, or, better yet, run a packet trace of a failing session. > After looking through the archives, i found this > > When SSL_write is called again after another function, SSL_ERROR_WANT_..., > it must get exactly the same buffer because parts of the buffer contents may > already have been encrypted and wait in interal buffers while others may not > yet have been looked at. What's really important is that buffer *contents* > stay the same, but as a sanity check to avoid application bugs the OpenSSL > library checks whether the buffer *address* is not changed. This check can > be disabled by setting SSL_MODE_ACCEPT_MOVING_WRITE_BUFFER for that SSL > object, using SSL_set_mode (or SSL_CTX_set_mode > on the SSL_CTX before SSL_new is called). I don't think this is the situation here.
