From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
sound-open-firmware@alsa-project.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: DMARC (Was: Re: [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe])
Date: Wed, 10 May 2023 00:58:58 -0300 [thread overview]
Message-ID: <ZFsWgnAQy5Y/rwyb@geday> (raw)
In-Reply-To: <ZFr8B5UFx16sz7S0@finisterre.sirena.org.uk>
On Wed, May 10, 2023 at 11:05:59AM +0900, Mark Brown wrote:
> AFAICT the only other option is munging the From without enclosing the
> message in a wrapper? That's potentially marginally less harmful but
> it's still going to break things badly enough that I'm not sure it's a
> worthwhile improvement.
The readymade mitigations for DMARC in mailman 3 are
"munge_from" and "wrap_message". The fact "wrap_message" messes
around with signatures in mutt is definitely not a good sign,
and "munge_from" will change the author's email and name from
the perspective of git-am.
The middle way could be to patch mailman 3 to "munge_from" while adding
the correct "From:" as the first thing in the body of the message if it
doesn't contain one already. This will make git-am pickup the correct
author's details and it should be some simple logic.
If Jaroslav is brave enough to maintain this supposed patch to mailman 3
in case it doesn't get picked-up upstream by the FSF folks...
I understand the maintainers needs must come first but it will be
terrible to get the GMail bouncing behaviour again, I don't want to
press the point since Jaroslav already made the speech I think it
was needed.
Thanks,
Geraldo Nascimento
next prev parent reply other threads:[~2023-05-10 4:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 1:09 [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe] Mark Brown
2023-05-04 7:35 ` Takashi Iwai
2023-05-04 7:58 ` Takashi Iwai
2023-05-08 7:52 ` Takashi Iwai
2023-05-09 7:12 ` DMARC (Was: Re: [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe]) Jaroslav Kysela
2023-05-09 9:37 ` Mark Brown
2023-05-09 9:54 ` Jaroslav Kysela
2023-05-09 14:35 ` Mark Brown
2023-05-09 18:03 ` Jaroslav Kysela
2023-05-09 18:26 ` Konstantin Ryabitsev
2023-05-10 2:05 ` Mark Brown
2023-05-10 3:33 ` Chen-Yu Tsai
2023-05-10 3:58 ` Geraldo Nascimento [this message]
2023-05-10 6:17 ` Jaroslav Kysela
2023-05-10 15:13 ` Konstantin Ryabitsev
2023-05-10 17:15 ` Geraldo Nascimento
2023-05-09 18:22 ` Konstantin Ryabitsev
2023-05-10 7:50 ` Jaroslav Kysela
2023-05-10 15:34 ` Konstantin Ryabitsev
2023-05-10 16:19 ` Jaroslav Kysela
2023-05-10 16:43 ` Konstantin Ryabitsev
2023-05-10 18:38 ` Jaroslav Kysela
2023-05-11 5:58 ` Mark Brown
2023-05-09 17:51 ` Geraldo Nascimento
2023-05-10 3:01 ` Chen-Yu Tsai
2023-05-10 6:46 ` Jaroslav Kysela
2023-05-05 20:38 ` [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe] Geraldo Nascimento
2023-05-06 0:13 ` Mark Brown
2023-05-06 2:17 ` Geraldo Nascimento
2023-05-07 23:33 ` Mark Brown
2023-05-07 23:38 ` Geraldo Nascimento
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=ZFsWgnAQy5Y/rwyb@geday \
--to=geraldogabriel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=sound-open-firmware@alsa-project.org \
--cc=tiwai@suse.de \
/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