Version: 1.12.2 (using KDE 4.3.2) OS: Linux Installed from: Ubuntu Packages The auto-discovery mechanism of KMail is unable to discover the available authentication mechanisms when they are presented only after a STARTTLS connection. Once the "Check what the server supports" button is used, TLS is correctly recognised but in the "Advanced" tab everything is grayed out and the message "This server does not support authentication" is displayed. This means that the user cannot change the authentication settings after the button has been pressed. One of the server that I use requires STARTTLS on the submission port. Here is the output for an EHLO command _before_ STARTTLS: EHLO example.com 250-out.example.com 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN This is the output of EHLO _after_ STARTTLS: EHLO example.com 250-out.example.com 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.