On Sat, Jan 20, 2001 at 12:28:53AM +0200, Tommi Komulainen wrote:
> > SSL connection using (NONE)
>
> This is not an error message, it's an informational message telling you
> the SSL parameters used on the connection. Seeing 'NONE' there means that
> the connection is *unencrypted*, and we all k
On Fri, Jan 19, 2001 at 04:13:55PM -0700, Tres Hofmeister wrote:
> I've already tried all of Mutt's ssl_use_* options in various
> combinations, with no difference in the behaviour. The "openssl"
> tests all seem to be about the same, looks like there's a handshaking
> problem. The results
On 2001-01-20, Tommi Komulainen <[EMAIL PROTECTED]> wrote:
:
: IIRC the reason for 'NONE' is that there's a slight mismatch between
: client and server SSL protocols and versions. See below.
Ah, thanks. That's helpful.
: In this case the FM would be README.SSL:
I've already
On Fri, Jan 19, 2001 at 02:13:57PM -0700, Tres Hofmeister wrote:
> The build goes fine, but when I attempt to connect to our
> SSL-wrapped IMAP server, I get an error immediately after accepting
> the site certificate. For example:
>
> tres$ mutt -f '{imap/ssl}'
> [I see:
> -- Mutt: SSL
I've compiled Mutt 1.2.5 on a Debian 2.2 (potato) system,
using the following configure options:
--enable-imap --with-ssl --enable-pop
The build goes fine, but when I attempt to connect to our
SSL-wrapped IMAP server, I get an error immediately after accepting
the site certif
