Bug 270536 - Configure/Sending (Add Transport): When adding a new outgoing mail account, "Check What the Server Supports" only checks port 25
Summary: Configure/Sending (Add Transport): When adding a new outgoing mail account, "...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.12.2
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-09 23:42 UTC by ar-bugs.kde.org
Modified: 2018-09-04 18:17 UTC (History)
1 user (show)

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 ar-bugs.kde.org 2011-04-09 23:42:55 UTC
Version:           1.12.2 (using KDE 1.2) 
OS:                Linux

In the "Add Transport" dialog when adding a new outgoing mail account, "Check What the Server Supports" only checks port 25 - even if 'Port' has been specifically set to a different value. This causes problems if the outgoing SMTP service on the remote server is running on a different port (e.g. mail submission port 587) - for example if the server is providing port 25 for incoming mail (MX mail receipt) and port 587 for outgoing mail (mail submission). The former may not provide authentication (SMTP AUTH) or encryption (like SMTP STARTTLS) whilst the latter does.

The workaround is to enter the port and settings manually, but this defeats the object of having an autoconfigure button (Check What the Server Supports) - as well as being confusing since this button gives the wrong result.

Since the port value is apparently ignored for this test, it would be better to have the dialog offer the autoconfigure option _OR_ select port & encryption manually; in it's current form it looks like the autoconfigure button will check the port value entered.

Alternatively it may be worth improving the 'Check what the server supports' capability: Instead of checking just port 25, it could be changed to check the selected port - or it could be changed to check common SMTP ports: 25, 465 and 587 being obvious candidates, as well as the selected port.

Reproducible: Always

Steps to Reproduce:
Setup an SMTP service on a port other than port 25. Optionally also provide a separate SMTP service on port 25 (with different capabilities). Now set the 'Port' value to the non-port 25 SMTP port number and click on 'Check What the Server Supports'. The capabilities of the SMTP service running on port 25 will be shown.

Capturing the traffic to the SMTP port(s) on the server makes the fault more obvious.

Actual Results:  
The capabilities of the SMTP service running on port 25 will be shown. If no SMTP service is running on port 25, 'None' will be shown for Encryption.

Expected Results:  
See 'Details' section

I still think kmail's a great product (and I know I'm running an older version, upgrading is on my todo list...)
Comment 1 ar-bugs.kde.org 2011-04-09 23:59:21 UTC
To clarify what kmail does on pressing 'Check what the server supports': kmail issues an EHLO to the remote server [on port 25] - capture port 25 traffic on the server to see this - kmail acts on seeing AUTH or STARTTLS as capabilities (probably others too).
Comment 2 Christophe Marin 2011-04-10 00:14:13 UTC
>Version:           1.12.2 

Please retry with KMail 1.13.6 from kdepim 4.4.10
Comment 3 Andrew Crouthamel 2018-09-04 18:17:49 UTC
Hello! Sorry to be the bearer of bad news, but this version of Kmail has been unmaintained for many years so I am closing this bug. Please try using the latest version of Kmail to see if your issue persists. If it does, please submit a new bug in "kmail2". Thank you!