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: mailman3 ffmpeg-devel-owner bounce mitigation
Date: Sat, 1 Nov 2025 13:02:35 +0100
Message-ID: <aQX220y9ZjwC5TJJ@neo> (raw)
In-Reply-To: <aQQRVkn8ZFf-NO7e@neo>
[-- Attachment #1.1: Type: text/plain, Size: 839 bytes --]
Hi all
On Fri, Oct 31, 2025 at 02:31:02AM +0100, Michael Niedermayer via ffmpeg-devel wrote:
[...]
> Of course bounces from normal mailing list mail still can get your
> account disabled.
also as iam currently looking at all the bounces for ffmpeg-devel ive
noticed that the most common bounce reason ATM is
"The email account that you tried to reach does not exist"
to save myself and the other admins from seeing these 5? people bounce daily
for the next 2 weeks until they get automatically disabled,
I will delete them manually. No point in delivering mail to non existing accounts
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
When you are offended at any man's fault, turn to yourself and study your
own failings. Then you will forget your anger. -- Epictetus
[-- 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
prev parent reply other threads:[~2025-11-01 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 1:31 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-31 9:26 ` [FFmpeg-devel] " Gyan Doshi via ffmpeg-devel
2025-10-31 13:26 ` Michael Niedermayer via ffmpeg-devel
2025-11-01 12:02 ` 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=aQX220y9ZjwC5TJJ@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