From: Junio C Hamano <gitster@pobox.com>
To: Glenn Rempe <glenn@rempe.us>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add ability to specify SMTP server port when using git-send-email.
Date: Mon, 24 Sep 2007 23:24:33 -0700 [thread overview]
Message-ID: <7v8x6v6z4u.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1190666058-10969-1-git-send-email-glenn@rempe.us> (Glenn Rempe's message of "Mon, 24 Sep 2007 13:34:18 -0700")
Glenn Rempe <glenn@rempe.us> writes:
> git-send-email.perl | 48 +++++++++++++++++++++++++++++++++++++-----------
> 1 files changed, 37 insertions(+), 11 deletions(-)
>
> diff --git a/git-send-email.perl b/git-send-email.perl
> index 4031e86..7c9c302 100755
> --- a/git-send-email.perl
> +++ b/git-send-email.perl
> @@ -79,6 +79,10 @@ Options:
> --smtp-server If set, specifies the outgoing SMTP server to use.
> Defaults to localhost.
>
> + --smtp-server-port If set, specifies the port on the outgoing SMTP
> + server to use. Defaults to port 25 unless --smtp-ssl is set in
> + which case it will default to port 465.
> +
This paragraph look inconsistent with different indentation
for second and subsequent lines.
> @@ -375,6 +381,14 @@ if (!defined $smtp_server) {
> $smtp_server ||= 'localhost'; # could be 127.0.0.1, too... *shrug*
> }
>
> +if (!defined $smtp_server_port) {
> + if ($smtp_ssl) {
> + $smtp_server_port = 465 # SSL port
> + } else {
> + $smtp_server_port = 25 # Non-SSL port
> + }
> +}
> +
> if ($compose) {
> # Note that this does not need to be secure, but we will make a small
> # effort to have it be unique
> @@ -604,20 +618,32 @@ X-Mailer: git-send-email $gitversion
> } else {
> if ($smtp_ssl) {
> require Net::SMTP::SSL;
> - $smtp ||= Net::SMTP::SSL->new( $smtp_server, Port => 465 );
> + $smtp ||= Net::SMTP::SSL->new( $smtp_server, Port => $smtp_server_port );
> }
> else {
> require Net::SMTP;
> - $smtp ||= Net::SMTP->new( $smtp_server );
> + $smtp ||= Net::SMTP->new( $smtp_server . ":" . $smtp_server_port );
> }
This change suggests that, although undocumented, existing users
could have already been using
--smtp-server=smtp.myisp.com:26
to specify a nonstandard port, and this patch, while bringing in
the support for a nonstandard port as an official feature, would
break such a setup. I wonder how real the issue is, and if we
can work it around easily. For example,
(1) drop the "default to 25 for smtp if undefined" part we saw
earlier;
(2) redo this part as
if ($smtp_ssl) {
... as you have it ...
} else {
require Net::SMTP;
$smtp ||= Net::SMTP->new((defined $smtp_server_port) ?
"$smtp_server:$smtp_server_port" :
$smtp_server);
}
> - $smtp->auth( $smtp_authuser, $smtp_authpass )
> - or die $smtp->message if (defined $smtp_authuser);
> ...
> +
> + # we'll get an ugly error if $smtp was undefined above.
> + # If so we'll catch it and present something friendlier.
> + if ($smtp) {
> +
> + if ((defined $smtp_authuser) && (defined $smtp_authpass)) {
> + $smtp->auth( $smtp_authuser, $smtp_authpass ) or die $smtp->message;
> + }
> + ...
> + } else {
> + die "Unable to initialize SMTP properly. Is there something wrong with your config?";
> + }
I'd prefer the check done the opposite order, like
if (!$smtp) {
die ...
}
without an else clause.
next prev parent reply other threads:[~2007-09-25 6:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 20:34 [PATCH] Add ability to specify SMTP server port when using git-send-email Glenn Rempe
2007-09-25 6:24 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-25 22:38 Glenn Rempe
2007-09-25 23:05 ` Johannes Schindelin
2007-09-25 23:12 ` Junio C Hamano
2007-09-25 23:25 ` Junio C Hamano
2007-09-26 0:23 ` Glenn Rempe
2007-09-26 0:27 ` Junio C Hamano
2007-09-26 1:15 ` Glenn Rempe
2007-09-26 1:42 ` Johannes Schindelin
2007-09-26 7:18 ` Andreas Ericsson
2007-09-26 10:31 ` Johannes Schindelin
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=7v8x6v6z4u.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=glenn@rempe.us \
/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).