From: Mark Brown <broonie@kernel.org>
To: Sebastian Reichel <sre@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-spi@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] spi updates for v5.2
Date: Wed, 8 May 2019 19:27:36 +0900 [thread overview]
Message-ID: <20190508102736.GO14916@sirena.org.uk> (raw)
In-Reply-To: <20190508101301.lxwt4e6eziujdfit@earth.universe>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
On Wed, May 08, 2019 at 12:13:01PM +0200, Sebastian Reichel wrote:
> On Wed, May 08, 2019 at 03:09:36PM +0900, Mark Brown wrote:
> > I'd have to send all mail out via kernel.org to do that, or persuade a
> > MTA to route mail differently based on contents which seems interesting
> > - I inject most of my mail via /usr/sbin/sendmail rather than SMTP
> > (including a bunch of scripts).
> I have a locally installed postfix in sender dependent relay
> configuration, which does that for me:
> http://www.postfix.org/SOHO_README.html#client_sasl_sender
I'm using exim on the central relay box which is much more painful to
configure than postfix sadly (one of these days I'll get round to
converting to Postfix since I prefer it and already use it on my client
boxes but the DKIM stuff is painful enough and there's enough stuff
using the box that it'll require me to actually sit down properly to do
something as substantial as cutting over MTAs). It's also not clear to
me that Postfix can be configured based on From rather than envelope
sender, I have used the configuration options you're pointing at for
envelope senders before but at least at that time Postfix didn't support
setting envelope sender via /usr/sbin/sendmail.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-08 10:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 14:33 [GIT PULL] spi updates for v5.2 Mark Brown
2019-05-06 19:01 ` Linus Torvalds
2019-05-07 2:18 ` Mark Brown
2019-05-07 2:34 ` Linus Torvalds
2019-05-07 3:09 ` Mark Brown
2019-05-07 3:02 ` Mark Brown
2019-05-07 3:13 ` Linus Torvalds
2019-05-07 11:03 ` Mark Brown
2019-05-07 12:07 ` Sebastian Reichel
2019-05-08 6:09 ` Mark Brown
2019-05-08 10:13 ` Sebastian Reichel
2019-05-08 10:27 ` Mark Brown [this message]
2019-05-08 10:20 ` Brian Masney
2019-05-07 15:08 ` Linus Torvalds
2019-05-08 6:11 ` Mark Brown
2019-05-07 15:10 ` pr-tracker-bot
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=20190508102736.GO14916@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=sre@kernel.org \
--cc=torvalds@linux-foundation.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