All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaroslav Kysela <perex@perex.cz>
To: Takashi Iwai <tiwai@suse.de>
Cc: Mark Brown <broonie@kernel.org>,
	alsa-devel@alsa-project.org,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	sound-open-firmware@alsa-project.org
Subject: DMARC (Was: Re: [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe])
Date: Tue, 9 May 2023 09:12:55 +0200	[thread overview]
Message-ID: <e76c1395-5eb2-849e-120d-1b7389fc97c7@perex.cz> (raw)
In-Reply-To: <87wn1jdzuq.wl-tiwai@suse.de>

On 08. 05. 23 9:52, Takashi Iwai wrote:
> On Thu, 04 May 2023 09:58:44 +0200,
> Takashi Iwai wrote:
>>
>> On Thu, 04 May 2023 09:35:38 +0200,
>> Takashi Iwai wrote:
>>>
>>> On Thu, 04 May 2023 03:09:45 +0200,
>>> Mark Brown wrote:
>>>>
>>>> Hi,
>>>>
>>>> Here's another mail (one of several in this series) that got completely
>>>> mangled by the alsa-project.org mailman to the point of unusability.  I
>>>> didn't see any response to my last mail about this, is there any news on
>>>> fixing mailman to not do this?  It's extremely disruptive to working
>>>> with lore.
>>>
>>> It seems that alsa-project.org mailman re-sends the post with
>>> xxx@alsa-project.org address sometimes, indeed.  I don't know the
>>> condition, but now I noticed it while checking the pending approvals.
>>
>> And, I guess it happens when a post comes from a non-subscriber.
>> (But not sure whether this happens always...)
>> It waits for approval, but also mangles the sender address and co.
>> This behavior is new after the mail server update.
> 
> Jaroslav, could you investigate it?  I checked again, and it seems
> that all "approved" posts from non-subscribers are modified to the
> sender addresses with alsa-project.org.  I guess there must be some
> option to prevent it.

The answer is DMARC. And the "mangling" applies only to senders which domains 
have restricted DMARC settings (reject or quarantine) - collabora.com has 
quarantine. More information:

https://lore.kernel.org/alsa-devel/6f003598-4cae-a521-233f-2c19eb439359@perex.cz/

I am open to any suggestions, but the default mailman settings (do not do 
anything) causes that some (mostly gmail) users do not receive their e-mails 
because the ALSA's mail server has a bad reputation. Many companies are using 
the google mail service for their domains nowadays.

The information is not lost - the original e-mail is just encapsulated (as an 
attachmnent) to new with the "allowed from" header for DMARC. But yes, it 
requires some more work (reply to the attachment, update scripts).

					Jaroslav

-- 
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.


  reply	other threads:[~2023-05-09  7:14 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       ` Jaroslav Kysela [this message]
2023-05-09  9:37         ` DMARC (Was: Re: [alsa-devel@alsa-project.org: [PATCH 3/5] ASoC: mediatek: mt8195-afe-pcm: Simplify runtime PM during probe]) 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
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=e76c1395-5eb2-849e-120d-1b7389fc97c7@perex.cz \
    --to=perex@perex.cz \
    --cc=alsa-devel@alsa-project.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=broonie@kernel.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 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.