Hi all

On Thu, Oct 16, 2025 at 06:25:00PM +0200, Michael Niedermayer via ffmpeg-devel wrote:
> Hi everyone
> 
> As we all certainly know, this ML since a few months rewrites
> all "From:" headers to "X Y via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>"
> We changed this because neither me nor timo nor rather unhelpfull AI
> could fix the bounce & dmarc issue
> 
> 33 @outlook and 19 @hotmail subscribers got deleted on october 8th
> because their accounts where disabled from earlier bounces and they
> did not re-enable their accounts.
> 
> Other mailing lists from other projects seem to survive without
> universal rewriting.
> 
> Should we try to switch this list back to only rewrite the
> addresses that need it ?
> 
> mailman3 has a list where we can manually add domains which need it
> 
> hotmail.com and outlook.com both have a DMARC policy of none
> so they would not automatically fall under DMARC mitigations
> and it seems noone added them to the mailman3 list
> nor was outlook in the postfix list we had from mailman2 days
> 
> Both me and timo want to try reducing the from rewriting again.
> We seem to disagree a bit on if we try with the mailman3 manual
> DMARC list empty first or starting with outlook and all entries from
> the sender_canonical rewrite list.
> 
> Are there any people reading this, who have some information / experiencees
> they can share about mailman3 DMARC settings ?
> (so we can benefit of your experience and can skip some trial and error :)
> 
> What do people think ?
> any other thing we are missing ?
> 
> PS: we now have a DMARC setup, ARC signing and mailman3

verp_probes are now enabled, thus people should receive a mail from mailman
now before having their account disabled/removed after several bounces.

And only if that last mail bounces would their account be disabled/removed

This is a mitigation to reduce the annoyance of bounces, not a final solution
Ive also enabled that bounced messages will be sent to the list owners so
I can see what exactly bounces and why. Iam not sure why this was disabled

From rewriting / DMARC mitigation is still unchanged.

thx

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Breaking DRM is a little like attempting to break through a door even
though the window is wide open and the only thing in the house is a bunch
of things you dont want and which you would get tomorrow for free anyway