Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [RFC] mailing list From mangling and bounces and DMARC
Date: Tue, 21 Oct 2025 13:41:46 +0200
Message-ID: <aPdxeq8qBCM5bwUG@neo> (raw)
In-Reply-To: <aPEcXITqkLMU59cJ@neo>


[-- Attachment #1.1: Type: text/plain, Size: 2488 bytes --]

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

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

      reply	other threads:[~2025-10-21 11:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-16 16:25 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-21 11:41 ` Michael Niedermayer via ffmpeg-devel [this message]

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=aPdxeq8qBCM5bwUG@neo \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    /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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git