From: "Wesley J. Landaker" <wjl@icecavern.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCHv2 2/2] Documentation: git-send-email: correct statement about standard ports
Date: Fri, 31 Jul 2009 11:45:00 -0600 [thread overview]
Message-ID: <200907311145.01759.wjl@icecavern.net> (raw)
In-Reply-To: <7vzlaku9d4.fsf@alter.siamese.dyndns.org>
On Friday 31 July 2009 10:04:39 Junio C Hamano wrote:
> As you noted, port 465 has been used as a well-known de-facto port to run
> SMTP over SSL at many places. I do not think it would help anybody by
> clarifying that it is a "non-standard" port here. This is not a place to
> educate people on which port they should run their SMTP servers.
>
> But I do not care deeply enough, and I can let it pass.
>
> I have much more trouble with that "like 465" than I have with "non
> standard".
If you don't like the phrasing, how about this revised patch? I call it a
"common SSL smtp port", and refer directly to 465. I think should make everyone
happy:
---
>From f0f6d41705f51f198c7cd87cbbf4ffdbe3fdf84e Mon Sep 17 00:00:00 2001
From: Wesley J. Landaker <wjl@icecavern.net>
Date: Thu, 30 Jul 2009 14:53:29 -0600
Subject: [PATCH 2/2] Documentation: git-send-email: correct statement about standard ports
The current documentation states that servers typically listen on port
465 and calls this "ssmtp". While it's true that many mail servers use
port 465 for SSL smtp, this is non-standard, and hails from the days
before smtp and submission TLS support, that arrived in RFC2487 and
RFC3207. Port 465 is actually assigned by IANA for unrelated purposes,
and is mostly still used by mail servers today only to support Outlook
Express.
In any case, this patch helps the documentation better reflect both
standards and reality, while still helpfully mentioning ports numbers
that a user may wish to specify.
Signed-off-by: Wesley J. Landaker <wjl@icecavern.net>
---
Documentation/git-send-email.txt | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index 1c94351..767cf4d 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -142,8 +142,9 @@ user is prompted for a password while the input is masked for privacy.
--smtp-server-port=<port>::
Specifies a port different from the default port (SMTP
- servers typically listen to smtp port 25 and ssmtp port
- 465); symbolic port names (e.g. "submission" instead of 587)
+ servers typically listen to smtp port 25, but may also listen to
+ submission port 587, or the common SSL smtp port 465);
+ symbolic port names (e.g. "submission" instead of 587)
are also accepted. The port can also be set with the
'sendemail.smtpserverport' configuration variable.
--
1.6.3.1
next prev parent reply other threads:[~2009-07-31 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-30 23:08 [PATCH 1/2] Documentation: git-send-email: fix submission port number Wesley J. Landaker
2009-07-30 23:08 ` [PATCH 2/2] Documentation: git-send-email: correct statement about standard ports Wesley J. Landaker
2009-07-31 16:04 ` Junio C Hamano
2009-07-31 17:45 ` Wesley J. Landaker [this message]
2009-07-31 18:19 ` [PATCHv2 " Junio C Hamano
2009-08-05 22:40 ` [PATCH " Tony Finch
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=200907311145.01759.wjl@icecavern.net \
--to=wjl@icecavern.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.