Re: SSL versus TLS?

--===============0998792473==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Boundary-02=_ZM/dAXBMaZEr9CE"
Content-Transfer-Encoding: 7bit

--Boundary-02=_ZM/dAXBMaZEr9CE
Content-Type: text/plain;
  charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 08 April 2004 07:24, Casey Allen Shobe wrote:
> If I use KMail 1.6.50 to detect what settings the server supports
> when both an imap and imaps service are running, it show me that
> None, SSL, and TLS are available, with only a Clear Text login.  If I
> choose SSL, the port changes to 993, and everything works.  If I
> choose TLS, the port remains 143, and communication does not work.
>
> It would seem that Binc is advertising a method it does not actually
> support.
>
> If I stop the imap server on port 143 with imaps still running, KMail
> detects only SSL being available, but with Clear Text, LOGIN, and
> PLAIN available.  I would guess this to be a KMail bug where it uses
> the imap supported auth methods to limit the imaps supported auth
> methods.

In a first reply which doesn't seem to have arrived I wrote:
> KMail currently doesn't handle different authentication methods for=20
> different encryption methods correctly.
>=20
> At least here KMail prints the answer that it receives from the server=20
> during the "Check what the server supports" run to stdout. So if you=20
> run KMail (compiled with debug information) from Konsole then you=20
> should get something like the following:
> kmail: IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN=20
> LANGUAGE STARTTLS XSENDER X-NETSCAPE XSERVERINFO AUTH=3DPLAIN
>=20
> kmail: IMAP4 IMAP4rev1 ACL QUOTA LITERAL+ NAMESPACE UIDPLUS CHILDREN=20
> LANGUAGE XSENDER X-NETSCAPE XSERVERINFO AUTH=3DPLAIN
>=20
> The first line is for port 143 and the second one for port 993. KMail=20
> will only use the first line. This should explain the behavior that=20
> you've noticed.

In the meantime I should have fixed this problem. Please update to the=20
latest cvs version of KMail (see http://kmail.ingo-kloecker.de in case=20
you need instructions) and check whether the problem is fixed for you.

Regards,
Ingo

--Boundary-02=_ZM/dAXBMaZEr9CE
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBAd/MZGnR+RTDgudgRAkuEAJ9LnyvaxTdVmNieVAqfxkbw0vN60gCdEHR5
oEKPqsvrZMhcz80BerUuW0k=
=MmkU
-----END PGP SIGNATURE-----

--Boundary-02=_ZM/dAXBMaZEr9CE--

--===============0998792473==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
KMail developers mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kmail-devel

--===============0998792473==--