Re: fetching message headers ...
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday, November 2 at 06:59 PM, quoth Ales Zemene:
>>> i would like to compile it myself, problem is that i use Mutt
>>> 1.5.9i
>>> (2005-03-13), for trivial reason - newer version makes problem with
>>> set imap_force_ssl='yes'
>>
>> Yes, it has been replaced by a more general approach. Read the
>> Changelog.
> yes it says :
> ! $imap_force_ssl has been replaced without synonym by $ssl_force_tls
> but if i replace it :
> #set imap_force_ssl='yes'
> set ssl_force_tls='yes'
> i get always :
> Could not connect to imap.mur.at (Connection refused).
>
> so far i am not sure if it is problem only with my config, or if it is
> involving also something from side of imap admin
Hmm. It would appear that we have an SSL-vs-TLS problem, maybe?
imap.mur.at appears to support imaps, but not imap. Make sure your
mailbox url is something that starts with imaps:// rather than
imap://. The difference is that imap:// tells mutt to connect to port
143, and imaps:// tells mutt to connect to port 993; imap.mur.at is
only listening on port 993. $ssl_force_tls merely tells mutt to make
sure that the connection is encrypted... it's possible that in
previous versions of mutt, it would attempt the port 143 connection
(with the intent of using the STARTTLS imap extension), and if that
failed, would try the port 993 connection. I think that the current
one doesn't fall back (probably for reasons of "if what I told it to
do fails, it shouldn't attempt other stuff behind my back!" or
something similar).
~Kyle
- --
It is a dogma of faith that the demons can produce wind, storms, and
rain of fire from heaven.
-- St. Thomas Aquinas
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iD8DBQFFSjriBkIOoMqOI14RArKTAKDifs8NCfCrwksfNWtmVl6vEX/brgCdH8xI
0QfxP5MUSyQFJEB1w99+VzQ=
=1fbl
-----END PGP SIGNATURE-----