Bug 172532 - Can't specify port, and/or can't disable TLS
Summary: Can't specify port, and/or can't disable TLS
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-10 18:33 UTC by Mike_Fontenot
Modified: 2009-03-19 01:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike_Fontenot 2008-10-10 18:33:24 UTC
Version:            (using KDE 3.5.10)
Compiler:          Dell Inspiron 530 
OS:                Linux
Installed from:    Mandriva RPMs

When I try to receive incoming email in kmail, it pops up the messgage: "Could not connect to Host. Your POP3 server does not support TLS. Disable TLS, if you want to connect without incryption.".  My ISP is Comcast. I tried unclicking "Enable TLS support if supported by the server" (under KDE Control Center -> Security -> Crypto), but still get the popup error message.  Perhaps another possible reason for the failure is that Comcast has always told me that I need to specify specific port numbers for incoming and outgoing mail: 110 for incoming, and 587 for outgoing, but I was never given that opportunity during kmail setup.
Comment 1 Mike_Fontenot 2008-10-10 19:50:59 UTC
I was able to get incoming mail to work by changing the encryption from TSL to SSL.  Apparently, Comcast tells kmail that it DOES support TSL, but when kmail tries to use that, Comcast apparently says it DOESN'T support it.  Outgoing mail also worked with SSL, and in that case, the "Check what server supports" returns SSL (as it apparently should).  When it succeeded, I was using the default port numbers (which seem to be determined once the encryption is specified), which were both different from what Comcast tells me to use...maybe the port numbers they give are for no encrpytion.
Comment 2 Thomas McGuire 2009-03-19 01:07:29 UTC
Closing as WORKSFORME, since that seems to be a server bug (advertising TLS even though it doesn't support it)