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@pere...
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