[FFmpeg-devel] Mailman3 Upgrade

[Timo Rothenpieler via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>]

[-- Attachment #1.1: Type: text/plain, Size: 1288 bytes --]

Hi!

As you might have noticed, a bunch of big Mail-Hosters have introduced 
new, even stricter, requirements. Primarily it's Microsoft, but others 
seem to already have followed suit.
So we had to configure the list to send all mails as coming from the 
list itself.

At least to me this seems highly annoying and makes it hard at times to 
immediately see who the mail is even from.

mailman2 has no good way to deal with that in a more reasonable way.
Mailman3 is already set up, and can be migrated to at a moments notice.
The only problem with it is that I really don't like the new archives.
It has ways to better deal with it, like better DMARC/SPF/... support in 
general, and support for ARC signing.

As an example, I already migrated nut-devel:
https://lists.ffmpeg.org/archives/list/nut-devel@ffmpeg.org/latest

Sooner or later, we will have to migrate no matter what.
Python2 is on its way out, and we will have to upgrade to an OS version 
that does not ship it anymore eventually.

So the question is, should I just migrate ffmpeg-devel, and if that goes 
well, pull over all the other lists as well?

In theory the migration should go without anyone noticing. It worked for 
nut-devel, but that's not exactly the most active list.



Timo

[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4742 bytes --]

[-- Attachment #2: Type: text/plain, Size: 251 bytes --]

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".