[kmail2] [Bug 341681] New: Failure to transport message, must issue a STARTTLS command first. [Frameworks branch]

[Dan O.]

https://bugs.kde.org/show_bug.cgi?id=341681

            Bug ID: 341681
           Summary: Failure to transport message, must issue a STARTTLS
                    command first. [Frameworks branch]
           Product: kmail2
           Version: Git (master)
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: misc
          Assignee: kdepim-bugs at kde.org
          Reporter: dan at redchops.com

Trying to send any email using any server that requires authentication fails
immediately. Testing on my own server, port 25 works fine, as it doesn't
require STARTTLS from localhost clients. When I switch to port 587 it fails,
the TCP stack is as follows:

220 mail.redchops.com ESMTP Postfix
EHLO equinox.localnet
250-mail.redchops.com
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
AUTH PLAIN ************************ [base64 password removed, but it is
correct]
530 5.7.0 Must issue a STARTTLS command first

In the SMTP settings, the radio buttons for setting encryption doesn't seem to
do anything. If I set one, close the window then reopen it, all the radio icons
are cleared. That seems to me that it's not actually setting the encryption
level in some config file but I can't find where this setting saves to. Even if
I create a GMail account with the account wizard, the settings don't stick and
I can't send mail with that account either

Reproducible: Always

Steps to Reproduce:
1. Create an outgoing server that requires encryption
2. Try to send an email

Actual Results:  
Email fails to send with the issue stated above, smtp never issues STARTTLS
upon connection to the server

Expected Results:  
Mail is sent properly

-- 
You are receiving this mail because:
You are the assignee for the bug.