[exim-dev] [Bug 97] outgoing tls_on_connect

Top Page
Delete this message
Reply to this message
Author: Simon Arlott
Date:  
To: exim-dev
Subject: [exim-dev] [Bug 97] outgoing tls_on_connect
------- You are receiving this mail because: -------
You are the QA contact for the bug.

http://bugs.exim.org/show_bug.cgi?id=97




--- Comment #6 from Simon Arlott <bugzilla.exim.simon@???> 2011-02-06 09:55:08 ---
(In reply to comment #5)
> My first inclination is to accept this patch, as part of "suffering through
> working in the real world"; it doesn't interfere with the operation of the
> standards version.


There are a lot of MUAs that support SMTPS despite it being deprecated over a
decade ago... it's in Thunderbird and I've seen it on different types of mobile
phone OS.

> Against this, there's an argument that supporting smtp/ssl-on-connect outbound
> takes away from the incentive to deploy Submission. In 2006 that was a
> justifiable concern, but over the past few years even some of the behemoths
> have come around to accepting Submission,
> port-filtering-25-on-home-connections, etc. So I think that Submission is safe
> and here to stay.


tejing on IRC needed to connect using SMTPS as port 25 was rerouted by the ISP
and the destination(s) don't support TLS on port 587. Having this in Exim is
better than using stunnel (it makes auth configuration easier) and the change
is relatively simple.

I can't see anyone deploying SMTPS instead of STARTTLS because of Exim. The
intended user of port 587 is MUAs, not other MTAs (which would be expected to
use port 25).


--
Configure bugmail: http://bugs.exim.org/userprefs.cgi?tab=email