From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: sndanailov@wired4ever.net, git@vger.kernel.org, aaron@schrab.com,
philipoakley@iee.email
Subject: Re: [PATCH v3] docs: git-send-email: difference between ssl and tls smtp-encryption
Date: Wed, 12 Oct 2022 14:38:17 -0700 [thread overview]
Message-ID: <xmqqy1tkiuye.fsf@gitster.g> (raw)
In-Reply-To: <Y0cxPHNZjTqZR5XE@tapette.crustytoothpaste.net> (brian m. carlson's message of "Wed, 12 Oct 2022 21:27:24 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> On 2022-10-12 at 15:06:19, sndanailov@wired4ever.net wrote:
>> diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
>> index 3290043053..765b2df853 100644
>> --- a/Documentation/git-send-email.txt
>> +++ b/Documentation/git-send-email.txt
>> @@ -178,9 +178,18 @@ Sending
>> for `sendmail` in `/usr/sbin`, `/usr/lib` and $PATH.
>>
>> --smtp-encryption=<encryption>::
>> - Specify the encryption to use, either 'ssl' or 'tls'. Any other
>> - value reverts to plain SMTP. Default is the value of
>> - `sendemail.smtpEncryption`.
>> + Specify in what way encrypting begins for the SMTP connection.
>> + Valid values are 'ssl' and 'tls'. Any other value reverts to plain
>> + (unencrypted) SMTP, which defaults to port 25.
>> + Despite the names, both values will use the same newer version of TLS,
>> + but for historic reasons have these names. 'ssl' refers to "implicit"
>> + encryption (sometimes called SMTPS), that uses port 465 by default.
>> + 'tls' refers to "explicit" encryption (often known as STARTTLS),
>> + that uses port 25 by default. Other ports might be used by the SMTP
>> + server, which are not the default. Commonly found alternative port for
>> + 'tls' and unencrypted is 587. You need to check your provider's
>> + documentation or your server configuration to make sure
>> + for your own case. Default is the value of `sendemail.smtpEncryption`.
>
> I'm happy with this as it stands. Thanks for taking my suggestions and
> sending a patch to improve the docs.
I marked it as "Expecting a reroll" in the latest issue of "What's
cooking" report, but I do not mind taking it to 'next' as-is,
without adding an extra reference to --smtp-server-port. The
reference to port numbers here are there to help readers identify
which one is which, not because it is common to use randomly
numbered ports.
Thanks.
next prev parent reply other threads:[~2022-10-12 21:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 15:06 [PATCH v3] docs: git-send-email: difference between ssl and tls smtp-encryption sndanailov
2022-10-12 16:49 ` Philip Oakley
2022-10-12 21:27 ` brian m. carlson
2022-10-12 21:38 ` Junio C Hamano [this message]
2022-10-13 10:54 ` Sotir Danailov
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=xmqqy1tkiuye.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=aaron@schrab.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.email \
--cc=sandals@crustytoothpaste.net \
--cc=sndanailov@wired4ever.net \
/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).