From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>,
	ffmpeg-devel-owner@ffmpeg.org
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] mailman3 ffmpeg-devel-owner bounce mitigation
Date: Fri, 31 Oct 2025 02:31:02 +0100
Message-ID: <aQQRVkn8ZFf-NO7e@neo> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2331 bytes --]
Hi all
I think ive finally found a way to fix the ffmpeg-devel-owners from
being unsubscribed/disabled due to spam bounces
Let me first explain what the problem is, then how we solved it.
The problem:
1. spam hits ffmpeg-devel-owners
2. our spam filters remove alot but not all spam
3. spam to ffmpeg-devel-owners is processed my mailman3
4. mailman3 forwards the spam to all the people on ffmpeg-devel-owners
5. some of this spam bounces because it is spam
6. the bounce is now indistingishable from a ffmpeg-devel subscriber
7. the bounce hits our server and is routed to mailman
8. mailman3 increases the bouce score for the address that bounced the spam (if theres a matching subscriber)
9. once the bouce score reaches the threshold the person has his subscription disabled
10. If you followed along, you will realize that mailman now disabled an account
   but that account was never involved in the bounce
mailman2 did not have this issue
What we tried:
1. Improve spam filtering, we did not run *-owner through all our
   spam filters, now we do, but its not enough.
   future plan here is to install rspamd
2. verp_probes = yes & probe_add_dsn: no
   This should prevent primary bounces from disabling accounts by
   having a final test message send (which should ideally not bounce
   as spam) sadly these seem to be able to bounce too
3. postfix
   we simply handle the ffmpeg-devel-owner in postfix now
   and now as mailman doesnt forward it, the return
   address is distinct from mailing list subscriber mail and thus any
   bounces from owners dont get counted as subscriber bounces.
ATM this is used only for ffmpeg-devel-owner,
i intend to enable the same thing for other mailing lists
what this also means, you can now again subscribe with the same mail
address to the list as used in ffmpeg-devel-owner without being
unsubscribed/disabled due to ffmpeg-devel-owner bounces.
Of course bounces from normal mailing list mail still can get your
account disabled.
thx
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
If you fake or manipulate statistics in a paper in physics you will never
get a job again.
If you fake or manipulate statistics in a paper in medicin you will get
a job for life at the pharma industry.
[-- 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
next             reply	other threads:[~2025-10-31  1:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31  1:31 Michael Niedermayer via ffmpeg-devel [this message]
2025-10-31  9:26 ` [FFmpeg-devel] " Gyan Doshi via ffmpeg-devel
2025-10-31 13:26   ` Michael Niedermayer via ffmpeg-devel
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=aQQRVkn8ZFf-NO7e@neo \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=ffmpeg-devel-owner@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