From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: icon@mricon.com, tools@linux.kernel.org, mjg59@srcf.ucam.org
Subject: Re: executable sendemail.smtpserver and b4 --reflect
Date: Fri, 28 Apr 2023 14:46:12 -0400 [thread overview]
Message-ID: <20230428-guidance-unvented-692ee1@meerkat> (raw)
In-Reply-To: <CAKwvOd=h2TeX6_WqHtK8Tf1MqmOB_ao+JfJpnoSmwXUB0qkaug@mail.gmail.com>
On Fri, Apr 28, 2023 at 11:34:23AM -0700, Nick Desaulniers wrote:
> > I don't think it's b4 that is doing this. I think Matthew mentioned that
> > sendgmr will rewrite some headers to match your internal authentication,
> > perhaps that's what is replacing the From: header?
>
> I see:
>
> $ b4 send
> ...
> Sending via "/usr/bin/sendgmr -i -f ndesaulniers@google.com"
>
> Should this be using `/usr/bin/sendgmr -i -f 'Nick Desaulniers
> <ndesaulniers@google.com>'`?
No, the addresses passed via -f are for the envelope-from, not for the message
headers (the envelope-from is used during the SMTP negotiation and this is
where the message should bounce to if it's not delivered).
That said, I don't know how sendgmr works internally, and since it doesn't
claim to be sendmail-compatible, the flags and how it treats them can be
anything, really.
-K
next prev parent reply other threads:[~2023-04-28 18:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 19:00 executable sendemail.smtpserver and b4 --reflect Nick Desaulniers
2023-04-12 19:02 ` Nick Desaulniers
2023-04-12 19:24 ` Konstantin Ryabitsev
2023-04-12 19:26 ` Kernel.org Bugbot
2023-04-12 19:39 ` Konstantin Ryabitsev
2023-04-19 18:15 ` b4: " Kernel.org Bugbot
2023-04-19 18:30 ` Konstantin Ryabitsev
2023-04-28 18:34 ` Nick Desaulniers
2023-04-28 18:46 ` Konstantin Ryabitsev [this message]
2023-04-19 18:31 ` b4: " Kernel.org Bugbot
2023-05-15 21:44 ` Kernel.org Bugbot
2023-05-15 21:49 ` Konstantin Ryabitsev
2023-05-15 23:02 ` Nick Desaulniers
2023-05-16 22:58 ` Kernel.org Bugbot
2023-08-03 20:56 ` Kernel.org Bugbot
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=20230428-guidance-unvented-692ee1@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=icon@mricon.com \
--cc=mjg59@srcf.ucam.org \
--cc=ndesaulniers@google.com \
--cc=tools@linux.kernel.org \
/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).