git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Cc: Jim Meyering <jim@meyering.net>
Subject: Re: [PATCH] hooks--update: new, required, config variable: hooks.envelopesender,
Date: Fri, 23 Mar 2007 16:15:26 +0000	[thread overview]
Message-ID: <200703231615.28350.andyparkins@gmail.com> (raw)
In-Reply-To: <87lkho6ky8.fsf@rho.meyering.net>

On Friday 2007 March 23 15:25, Jim Meyering wrote:
> Andy Parkins <andyparkins@gmail.com> wrote:
> > On Friday 2007 March 23 13:29, Jim Meyering wrote:
> >> It works for me using the sendmail from sendmail, and I have tested
> >> this with the one from postfix, too.
> >
> > Is your user set as a trusted user for sendmail though?
>
> No.  There is no need for that.
>
> > As a normal user wouldn't be allowed to do it.
>
> You mean with exim's sendmail?
> sendmail -f alt-envelope-sender works just fine when run by a
> non-privileged user when it's Sendmail's sendmail or the one from Postfix.
> It's a shame if it doesn't work with exim's implementation.

Okay; I went and found a sendmail manpage:

"-fname       Sets the name of the ``from'' person (i.e., the sender of the
              mail).  -f can only be used by ``trusted'' users (normally
              root,  daemon, and network) or if the person you are trying to
              become is the same as the person you are."

Seems the same as exim to me.  Perhaps your distribution sets it up to allow 
if for anyone?

> case.  FYI, the first case was to allow commit email to be sent from
> the GNU coreutils git repository in a vserver on savannah.gnu.org.
> The second was at work last night.

> Not the *final* recipient, of course.
> Some *internal* MX servers are very careful about sender addresses
> in outbound mail, verifying them before forwarding the message on.

Fair enough.

> Thanks for the explanation of how email works, but you may
> assume that I know a little more than the average hacker :-)

My apologies; I didn't mean to be patronising - I wrongly assumed you were 
just confused about who was authenticating whom.

So; in short: I don't have a good answer to offer you, and it seems that "-f" 
is working for you.  However, I'm still not convinced that this is the 
correct thing to do in the default hook.  My main gripe is still all 
these "trusted user" paragraphs in the MTA manual pages.



Andy
-- 
Dr Andy Parkins, M Eng (hons), MIET
andyparkins@gmail.com

  reply	other threads:[~2007-03-23 16:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23 12:11 [PATCH] hooks--update: new, required, config variable: hooks.envelopesender, Jim Meyering
2007-03-23 12:58 ` Andy Parkins
2007-03-23 13:29   ` Jim Meyering
2007-03-23 14:05     ` Jakub Narebski
2007-03-23 14:12     ` Andy Parkins
2007-03-23 15:25       ` Jim Meyering
2007-03-23 16:15         ` Andy Parkins [this message]
2007-03-24 11:27           ` Jim Meyering
2007-03-24 12:16             ` Andy Parkins
2007-03-24 19:58               ` [PATCH] hooks--update: new, optional, config variable: hooks.envelopesender Jim Meyering

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=200703231615.28350.andyparkins@gmail.com \
    --to=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jim@meyering.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).