will do. Actually that's probably the best bet for me anyway, since I wonder
whether US crypto regulations would prevent me from releasing more invasive
SSL support...
----- Original Message -----
From: Thomas Roessler <[EMAIL PROTECTED]>
To: Brendan Cully <[EMAIL PROTECTED]>
Cc: David Thorburn-Gundlach <[EMAIL PROTECTED]>; Mutt Users' List
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Monday, August 23, 1999 10:30 AM
Subject: Re: ssl-imap and mutt
> Possibly, you can implement this using some wrapper tools. I seem
> to recall that you can use ssl-wrap to "sslify" software which
> doesn't support SSL as is. Please investigate this path further
> before starting to add OpenSSL to mutt. ;-)
>
> Thanks.
>
> On 1999-08-23 09:49:27 -0400, Brendan Cully wrote:
> > From: "Brendan Cully" <[EMAIL PROTECTED]>
> > To: "David Thorburn-Gundlach" <[EMAIL PROTECTED]>
> > Cc: "Mutt Users' List" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
> > Subject: Re: ssl-imap and mutt
> > Date: Mon, 23 Aug 1999 09:49:27 -0400
> >
> > > Will mutt talk ssl-imap to my ssl-imap-capable server? Is there
> > > anything specific to set up, or will it just happen automagically?
> >
> > I don't think so. But I don't know anything about the SSL-IMAP protocol.
If
> > anyone has any docs or pointers to this protocol, I'll investigate
adding
> > support for this.
> >
> >
>
>
