From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
sound-open-firmware@alsa-project.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 12:43:27 -0400 [thread overview]
Message-ID: <20230510-raked-loft-bureau-1c87fb@meerkat> (raw)
In-Reply-To: <41443193-1c4a-bfea-f81c-e6658b7addee@perex.cz>
On Wed, May 10, 2023 at 06:19:15PM +0200, Jaroslav Kysela wrote:
> On 10. 05. 23 17:34, Konstantin Ryabitsev wrote:
>
> > So, I'm just going to repeat this: operating a mailing list and remaining
> > DMARC compliant is perfectly possible, provided:
> >
> > - the original message is DKIM-signed
> > - all existing headers are unmodified
> > - the message body is unmodified
>
> Example of e-mail which is rejected by google's mx servers:
>
> https://lore.kernel.org/alsa-devel/20230510142227.32945-1-vitalyr@opensource.cirrus.com/raw
Thank you for this example -- it plainly illustrates the problem, which is
that Mailman 3 mangles messages.
If you compare the above message with the message that passed via vger, you
will notice what went wrong:
-CC: <alsa-devel@alsa-project.org>, <patches@opensource.cirrus.com>,
- <linux-kernel@vger.kernel.org>,
- Vitaly Rodionov <vitalyr@opensource.cirrus.com>
+CC: alsa-devel@alsa-project.org, patches@opensource.cirrus.com,
+ linux-kernel@vger.kernel.org, Vitaly Rodionov <vitalyr@opensource.cirrus.com>
For some bizarre reason Mailman-3 decided to make the CC header "more pretty"
by stripping the angle brackets around addresses. Since it's a DKIM-signed
header, this invalidates the signature and results in DMARC violations.
The answer, unfortunately, is to stop using Mailman-3. It's not usable for
patch-based workflows.
-K
next prev parent reply other threads:[~2023-05-10 17:31 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
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 [this message]
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=20230510-raked-loft-bureau-1c87fb@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=perex@perex.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.