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: Fri, 31 Oct 2025 14:26:31 +0100
Message-ID: <aQS5BwiFBa3t1Ao2@neo> (raw)
In-Reply-To: <e88a5869-aed2-44ff-b8bb-4ca0c0f538c7@gyani.pro>
[-- Attachment #1.1: Type: text/plain, Size: 755 bytes --]
Hi Gyan
On Fri, Oct 31, 2025 at 02:56:20PM +0530, Gyan Doshi via ffmpeg-devel wrote:
>
>
> On 2025-10-31 07:01 am, Michael Niedermayer via ffmpeg-devel wrote:
> > Hi all
> >
> > I think ive finally found a way to fix the ffmpeg-devel-owners from
> > being unsubscribed/disabled due to spam bounces
>
> Lots of spam incoming to ffmpeg-devel.
Yes, thats unrelated,
ive banned their domains, deleted or blocked their accounts and
timo has deleted the spam from hyperkitty archieve and disabled teh apparent path
they used to post/subscribe
we will see if that fixes it
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Avoid a single point of failure, be that a person or equipment.
[-- 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-10-31 13:27 UTC|newest]
Thread overview: 3+ 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 [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=aQS5BwiFBa3t1Ao2@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