On Tue, May 09, 2023 at 09:12:55AM +0200, Jaroslav Kysela wrote: > On 08. 05. 23 9:52, Takashi Iwai wrote: [alsa-devel rewriting mails in a way that renders them useless with b4] > > 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@xxxxxxxx/ > 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). Copying in Konstantin - as I said this is massively disruptive to using b4 with anything that's been mangled, to the point where the messages are unusable without substantial manual mangling (and signature verification fails too). It'd be more usable to just not have the messages from the list getting to lore and manually bounce patches to the list. Is it possible to take steps to improve the reptuation of the ALSA servers so this isn't needed, or could we migrate the lists elsewhere (I know we set up linux-sound@vger at one point with the idea of migrating).
Attachment:
signature.asc
Description: PGP signature
