git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] send-email: allow sendmail binary to be used instead of SMTP
Date: Sun, 14 May 2006 22:52:12 -0700	[thread overview]
Message-ID: <7vpsifx2b7.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1147660345772-git-send-email-normalperson@yhbt.net> (Eric Wong's message of "Sun, 14 May 2006 19:32:25 -0700")

Eric Wong <normalperson@yhbt.net> writes:

> This should make local mailing possible for machines without
> a connection to an SMTP server.

Which is a good thing, but

> It'll default to using /usr/sbin/sendmail or /usr/lib/sendmail
> if no SMTP server is specified (the default).  If it can't find
> either of those paths, it'll fall back to connecting to an SMTP
> server on localhost.

I do not know if it is OK to change the default to first prefer
local MDA executable and then "localhost".  That is, ...

> @@ -179,8 +180,14 @@ if (!defined $initial_reply_to && $promp
>  	$initial_reply_to =~ s/(^\s+|\s+$)//g;
>  }
>  
> -if (!defined $smtp_server) {
> -	$smtp_server = "localhost";
> +if (!$smtp_server) {
> +	foreach (qw( /usr/sbin/sendmail /usr/lib/sendmail )) {
> +		if (-x $_) {
> +			$smtp_server = $_;
> +			last;
> +		}
> +	}
> +	$smtp_server ||= 'localhost'; # could be 127.0.0.1, too... *shrug*
>  }
>  
>  if ($compose) {

Without this hunk, people who did not specify --smtp-server=host
could get away with having anything that listens to 25/tcp on
the localhost that is not either of the above two paths; now
they have to explicitly say --smtp-server=localhost to defeat
what this hunk does.  I do not know if it is a big deal, though.

> +	if ($smtp_server =~ m#^/#) {

I like this if(){}else{} here, but have a feeling that the
logging part should be placed outside it to be shared.

While we are at it, we might want to enhance $smtp_server parsing
to take host:port notation so that people can use message
submission port 587/tcp (RFC 4409) instead.

  parent reply	other threads:[~2006-05-15  5:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15  2:32 [PATCH] send-email: allow sendmail binary to be used instead of SMTP Eric Wong
2006-05-15  2:34 ` Eric Wong
2006-05-15  2:38 ` [PATCH] send-email: quiet some warnings Eric Wong
2006-05-15  6:04   ` Junio C Hamano
2006-05-15  9:41     ` [PATCH] send-email: quiet some warnings, reject invalid addresses Eric Wong
2006-05-15  5:52 ` Junio C Hamano [this message]
2006-05-15  9:27   ` [PATCH] send-email: allow sendmail binary to be used instead of SMTP Eric Wong
2006-05-15  9:34     ` Eric Wong
2006-05-15  9:47     ` Junio C Hamano
2006-05-15 10:11       ` Eric Wong
2006-05-15 10:37         ` Martin Langhoff
2006-05-15 16:25           ` Junio C Hamano
2006-05-15 19:10           ` Eric Wong
2006-05-15 21:01       ` Ryan Anderson
2006-05-15 21:13         ` Junio C Hamano
2006-05-15 21:52           ` Ryan Anderson
2006-05-15 22:07           ` Martin Langhoff

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=7vpsifx2b7.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.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).