[FFmpeg-devel] Mailman3 Upgrade

[FFmpeg-devel] Mailman3 Upgrade

[Timo Rothenpieler via ffmpeg-devel]

[-- 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".

Re: [FFmpeg-devel] Mailman3 Upgrade

[James Almer via ffmpeg-devel]

[-- Attachment #1.1.1: Type: text/plain, Size: 1863 bytes --]

On 8/18/2025 7:08 PM, Timo Rothenpieler via ffmpeg-devel wrote:
> 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?

IMO yes. The archive, while ugly, should not be a blocker to make the 
mailing list more usable for everyone (Plus it allows us to update the 
server distro).

> 
> In theory the migration should go without anyone noticing. It worked for 
> nut-devel, but that's not exactly the most active list.
> 
> 
> 
> Timo
> 
> _______________________________________________
> 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".


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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".

Re: [FFmpeg-devel] Mailman3 Upgrade

[Martin Storsjö via ffmpeg-devel]

On Tue, 19 Aug 2025, Timo Rothenpieler via ffmpeg-devel wrote:

> 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.

Can the old archives be kept in their current location (assuming they 
don't fully alias the new URLs?) even if they don't get updates, in order 
to keep current references working? References to old mails through such 
URLs is quite common.

Judging from nut-devel, the old archives for that seem to be intact and 
available, so hopefully this is not an issue.

// Martin

_______________________________________________
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".

Re: [FFmpeg-devel] Mailman3 Upgrade

[Timo Rothenpieler via ffmpeg-devel]

On 19/08/2025 08:55, Martin Storsjö via ffmpeg-devel wrote:
> On Tue, 19 Aug 2025, Timo Rothenpieler via ffmpeg-devel wrote:
> 
>> 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.
> 
> Can the old archives be kept in their current location (assuming they 
> don't fully alias the new URLs?) even if they don't get updates, in 
> order to keep current references working? References to old mails 
> through such URLs is quite common.
> 
> Judging from nut-devel, the old archives for that seem to be intact and 
> available, so hopefully this is not an issue.

Yeah, the old archives are just plain HTML generated by pipermail.
As long as nobody deletes that HTML, they won't go anywhere.
_______________________________________________
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".