[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Oinkage in the 'post' command SSL handling...

From: Ken Hornstein
Subject: Re: [Nmh-workers] Oinkage in the 'post' command SSL handling...
Date: Tue, 03 Jan 2012 11:09:38 -0500

>So I had occasion to post an email that contained a data file, about 1M in
>size, averaging maybe 15 bytes/line (it was basically e-mail addresses from an
>extract, one per line).  I hit 'send', and I'm watching gkrellm report 300K/sec
>going out my cable connection to our mail hub.. and after 3 seconds it's not
>done sending.  After a minute it's still blasting at 300K/sec.  6 minutes or so
>later, it finally finishes.

... aw, crap, I guess this is my fault.

In my defense, the SSL_write man page is misleading; the implication is that
it might do buffering depending on the underlying BIO.  But I guess now
that I dig down into it ... yeah, every call to SSL_write is unbuffered.
And it turns out we do that a lot, because we call SSL_write() every
time we have a new line.

It looks like an easy fix, actually.  I found some example code which creates
a BIO stack which adds buffering.  Let me chew on it a bit and see if I
can make it work.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]