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, 7 Nov 2025 15:03:50 +0100
Message-ID: <aQ38RoridFehkN3m@phare.normalesup.org> (raw)
In-Reply-To: <CAMM0M5-KfN0nodhtRT3YFnjodXtH4GEdmjVV-NgRKzH2GTLo1w@mail.gmail.com>
Pavel Roslyy via ffmpeg-devel (HE12025-11-04):
> The headers that are signed for DKIM can be configured. It is not
> recommended, but if needed you can remove Subject from the list of
> signed headers.
“Eh, Google, can I edit your DKIM settings to exclude the Subject
header, so that we can add ‘[ffmpeg-devel]’ in it?”
I doubt they will let us.
> I had a similar situation at $dayjob where we wanted the From to have
> the user's email but the mail to be sent from our server. The solution
> I found was to include a Sender header after the From, in this case
> it should probably be "Sender: ffmpeg-devel@ffmpeg.org". This should
> cause the SPF lookup to happen to ffmpeg.org instead of
> their-domain.org. Note that if the From is already ffmpeg-devel@ffmpeg.org then
> you should not add a Sender header, according to RFC 5322.
Too bad, DMARC killed that loophole.
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-07 14:04 UTC|newest]
Thread overview: 5+ 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 [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=aQ38RoridFehkN3m@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