From: Junio C Hamano <gitster@pobox.com>
To: "Drew DeVault" <sir@cmpwn.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>, <git@vger.kernel.org>
Subject: Re: [PATCH] send-email: clarify SMTP encryption settings
Date: Sat, 10 Apr 2021 09:43:05 -0700 [thread overview]
Message-ID: <xmqqczv2jdk6.fsf@gitster.g> (raw)
In-Reply-To: CAJNUBUZNAXE.283NJ968IDN2X@taiga
"Drew DeVault" <sir@cmpwn.com> writes:
> On Fri Apr 9, 2021 at 9:39 PM EDT, brian m. carlson wrote:
>> Since I agree that "ssl/tls" may be a bit confusing, maybe we could call
>> that option "wrapped" or "tunneled"? Other names are possible, of
>> course.
>
> I would prefer to name the options after the terms we can expect the
> user to find in their mail service provider's documentation, hence
> SSL/TLS and STARTTLS. Though I can see the confusion in including the
> slash, I'll figure something else out.
OK.
* My e-mail provider [*] seems to label these two as SSL/TLS
(sometimes just TLS) and STARTTLS, but that is aligning how the
popular client programs call these two methods, so it may not be
a good datapoint.
* GMail help page [*] seems to use 'SSL' vs 'STARTTLS' (they seem
to support both).
* Outlook.live.com/ help page [*] says they want you to use
'STARTTLS' for SMTP, but they use 'SSL/TLS' to describe their
IMAP and POP offerings.
With the above limited samples, I agree that the choices between
'SSL/TLS' and 'STARTTLS' would appear familiar to our end-users.
[Reference]
* https://helpspot.pobox.com/index.php?pg=kb.page&id=118
https://helpspot.pobox.com/index.php?pg=kb.page&id=125
https://helpspot.pobox.com/index.php?pg=kb.page&id=399
* https://support.google.com/mail/answer/7126229?hl=en
* https://support.microsoft.com/en-us/office/pop-imap-and-stmp-settings-8361e398-8af4-4e97-b147-6c6c4ac95353
prev parent reply other threads:[~2021-04-10 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 21:18 [PATCH] send-email: clarify SMTP encryption settings Drew DeVault
2021-04-09 22:04 ` Eric Sunshine
2021-04-09 23:14 ` Georgios Kontaxis
2021-04-09 23:39 ` Drew DeVault
2021-04-10 0:52 ` Junio C Hamano
2021-04-10 0:57 ` Drew DeVault
2021-04-10 1:09 ` Junio C Hamano
2021-04-11 5:48 ` Bagas Sanjaya
2021-04-10 1:39 ` brian m. carlson
2021-04-10 1:42 ` Drew DeVault
2021-04-10 16:43 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqczv2jdk6.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
--cc=sir@cmpwn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).