From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Nicolas George <george@nsup.org>
Subject: [FFmpeg-devel] Re: [RFC] mailing list From mangling and bounces and DMARC
Date: Fri, 21 Nov 2025 13:09:25 +0100
Message-ID: <aSBWdaHnrvD2hnwQ@phare.normalesup.org> (raw)
In-Reply-To: <CAMM0M5-C+syBN1krc-S5c82+Mfp5UBQs0vugh1Lx6=jwbpkB8Q@mail.gmail.com>
Hi.
Pavel Roslyy via ffmpeg-devel (HE12025-11-11):
> I was misunderstanding what mailman does, so my statement was nonsense
> and can be disregarded.
This thing is a maze of contradictory information and fallacies, many
eyes on it is best to have a chance to find a solution.
> I did some digging and have come to the conclusion you are right.
> Setting "From: developer@their-domain.org" with
> "Sender: ffmpeg-devel@ffmpeg.org" will cause SPF and DKIM to pass but
> DMARC will fail because neither SPF or DKIM will be in "alignment"
> with the mail From header.
>
> ARC (Authenticated Received Chain) could theoretically help but
> basically requires mail operators to put ffmpeg.org on a whitelist as
> a trusted signer, assuming they even support ARC.
They pretend they implement a solution, but beyond all the
over-engineered shit we realize it is useless.
> Setting From: to be @ffmpeg.org seems to be the only practical
> solution. Sorry for the noise.
If we both arrive to the conclusion…
Regards,
--
Nicolas George
_______________________________________________
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-21 12:09 UTC|newest]
Thread overview: 7+ 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 ` [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-11-04 19:12 ` Nicolas George via ffmpeg-devel
2025-11-05 3:47 ` Pavel Roslyy via ffmpeg-devel
2025-11-07 14:03 ` Nicolas George via ffmpeg-devel
2025-11-11 23:35 ` Pavel Roslyy via ffmpeg-devel
2025-11-21 12:09 ` Nicolas George 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=aSBWdaHnrvD2hnwQ@phare.normalesup.org \
--to=ffmpeg-devel@ffmpeg.org \
--cc=george@nsup.org \
/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