Bug 70464 - when configuring account : imap port not detected correctly
Summary: when configuring account : imap port not detected correctly
Status: RESOLVED DUPLICATE of bug 70463
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-15 03:03 UTC by Arnaud Burlet
Modified: 2007-09-14 12:17 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arnaud Burlet 2003-12-15 03:03:33 UTC
Version:            (using KDE KDE 3.1.94)
Installed from:    Gentoo Packages
Compiler:          gcc 3.2.3 gcc version 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r3, propolice)
OS:          Linux

I configured 2 imap accounts in kmail :

- first on a kolab server, only imaps port (993) is accessible (143 blocked by firewall).
 When I configure this account, I choose the tab security, and click "Check what the server supports", ssl is selected. And when I go back to the general tab port 993 is configured instead of 143, perfect !

- second imap account, both ports 143 and 993 are accessible. I configure the host, and under the security tab choose "check what ..." : TLS is choosed with PLAIN authentication method. Back to the general tab, port 143 is still there as the port to be used.

with that setup, kmail can't access my mails in the 2nd account an shows error "Starting TLS failed".

I think that if TLS is choosed by the user, port should be automatically changed into 993. Even if both ports are accessible.

BTW, when clearing the port field and clicking "OK", port is set to 0, couldn't it be better ?
Comment 1 Thiago Macieira 2003-12-15 03:09:58 UTC
Filed twice.
Comment 2 Ingo Klöcker 2003-12-15 17:47:18 UTC
reopened in order to properly mark it as duplicate.
Comment 3 Ingo Klöcker 2003-12-15 17:48:17 UTC

*** This bug has been marked as a duplicate of 70463 ***