On Tue, 18 Jan 2000, Tommi Komulainen wrote:
> On Tue, Jan 18, 2000 at 01:12:58PM -0800, Jeremy Katz wrote:
> > Actually, I have no clue why it was trying to connect to port 143 at
> > the time. It is now connecting to 993, but saying it is unable to get
> > certificate from peer.
>
> Eh.. you didn't touch a thing but it just started working?
Either that or I was just doing something weird (I removed the port
refernce, it did as above, I put it back, and it still did... *shrug*)
> > strace output:
>
> Thanks, it revealed the IP so I quickly made my own tests:
Knew there'd be an unexpected benefit somehow of including that :)
[snip]
>
> Which means it should work fine if you just disable the TLS protocol.
> There's no way to do this in mutt right now, so you're out of luck
> unless you can persuade your server administrator to change their
> configuration. Or you could try using stunnel or something, I think
> they can be configured to disable some protocols.
>
> Maybe we need to introduce a new variable allow disabling/enabling
> certain SSL protocols, or even better, modify the connection logic to
> notice unsupported protocols and try again without them. I'm not sure
> if the latter is even possible. I was under the impression that
> there's no harm in enabling all protocols and that if one isn't
> supported, another on would be tried. Apparently, I was wrong.
Guess I might be taking the time to read more on SSL in the near
future... probably not a bad plan (and more likely to get results than
convincing the admin to enable TLS ;)
Jeremy
--
Jeremy Katz http://linuxpower.org
Personal: [EMAIL PROTECTED]
School: [EMAIL PROTECTED]
GPG fingerprint: 367E 8B6B 5E57 2BDB 972A 4D73 C83C B4E8 89FE 392D
QOTD:
Chemist who falls in acid is absorbed in work.
