[ANN] Mailing list migration to lists.u-boot-project.org

[ANN] Mailing list migration to lists.u-boot-project.org

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 829 bytes --]

Hey all,

As I've mentioned in previous release emails, we'll be migrating our
lists over to lists.u-boot-project.org. The news now is that we have a
date. This coming Monday the 20th of July, we'll be turning off the
receiving side of lists.denx.de and then importing everything over to
lists.u-boot-project.org.

What do you need to do? Nothing much. All active subscribers and their
preferences will be moved. This includes how lore and patchwork are
linked, so all of that will work. We are going to try and ensure no new
emails get lost in the migration.

Based on feedback from the test migration, we believe we know what was
missing to ensure that the archive links are stable, and so that should
be the case when we go live again.

I'll send out a reminder about this Sunday.

Thanks all!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]

On Wed, Jul 15, 2026 at 11:31:19AM -0600, Tom Rini wrote:

> Hey all,
> 
> As I've mentioned in previous release emails, we'll be migrating our
> lists over to lists.u-boot-project.org. The news now is that we have a
> date. This coming Monday the 20th of July, we'll be turning off the
> receiving side of lists.denx.de and then importing everything over to
> lists.u-boot-project.org.
> 
> What do you need to do? Nothing much. All active subscribers and their
> preferences will be moved. This includes how lore and patchwork are
> linked, so all of that will work. We are going to try and ensure no new
> emails get lost in the migration.
> 
> Based on feedback from the test migration, we believe we know what was
> missing to ensure that the archive links are stable, and so that should
> be the case when we go live again.
> 
> I'll send out a reminder about this Sunday.

As a reminder, it's Sunday, and the plan is for this to happen Monday,
late afternoon Europe, morning west coast US.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Mark Kettenis via U-Boot]

> Date: Wed, 15 Jul 2026 11:31:19 -0600
> From: Tom Rini <trini@konsulko.com>

Hi Tom,

> Hey all,
> 
> As I've mentioned in previous release emails, we'll be migrating our
> lists over to lists.u-boot-project.org. The news now is that we have a
> date. This coming Monday the 20th of July, we'll be turning off the
> receiving side of lists.denx.de and then importing everything over to
> lists.u-boot-project.org.
> 
> What do you need to do? Nothing much. All active subscribers and their
> preferences will be moved. This includes how lore and patchwork are
> linked, so all of that will work. We are going to try and ensure no new
> emails get lost in the migration.
> 
> Based on feedback from the test migration, we believe we know what was
> missing to ensure that the archive links are stable, and so that should
> be the case when we go live again.
> 
> I'll send out a reminder about this Sunday.
> 
> Thanks all!

Sadly it seems that the new list is (mis)configured to rewrite the
From: header to something like:

  "John Doe via U-Boot <u-boot@lists.u-boot-project.org>"

Does it have to be that way?

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Tom Rini via U-Boot]

[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]

On Mon, Jul 20, 2026 at 08:24:34PM +0200, Mark Kettenis wrote:
> > Date: Wed, 15 Jul 2026 11:31:19 -0600
> > From: Tom Rini <trini@konsulko.com>
> 
> Hi Tom,
> 
> > Hey all,
> > 
> > As I've mentioned in previous release emails, we'll be migrating our
> > lists over to lists.u-boot-project.org. The news now is that we have a
> > date. This coming Monday the 20th of July, we'll be turning off the
> > receiving side of lists.denx.de and then importing everything over to
> > lists.u-boot-project.org.
> > 
> > What do you need to do? Nothing much. All active subscribers and their
> > preferences will be moved. This includes how lore and patchwork are
> > linked, so all of that will work. We are going to try and ensure no new
> > emails get lost in the migration.
> > 
> > Based on feedback from the test migration, we believe we know what was
> > missing to ensure that the archive links are stable, and so that should
> > be the case when we go live again.
> > 
> > I'll send out a reminder about this Sunday.
> > 
> > Thanks all!
> 
> Sadly it seems that the new list is (mis)configured to rewrite the
> From: header to something like:
> 
>   "John Doe via U-Boot <u-boot@lists.u-boot-project.org>"
> 
> Does it have to be that way?

So the answer is kinda. Whereas back on DENX we never "munged" emails
this is also why we likely often had big piles of unsubscribed due to
bounces (which was due to rejection from being incorrectly set as spam)
on the big providers. So now mailman is configured to munge the headers
*only* from senders which have a enforcing DMARC policy set, which
xs4all.nl has. And because we're on shared resources our lists not
following the DMARC rules would mess up all of the other lists.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Maciej W. Rozycki via U-Boot]

On Mon, 20 Jul 2026, Tom Rini via U-Boot wrote:

> > Sadly it seems that the new list is (mis)configured to rewrite the
> > From: header to something like:
> > 
> >   "John Doe via U-Boot <u-boot@lists.u-boot-project.org>"
> > 
> > Does it have to be that way?
> 
> So the answer is kinda. Whereas back on DENX we never "munged" emails
> this is also why we likely often had big piles of unsubscribed due to
> bounces (which was due to rejection from being incorrectly set as spam)
> on the big providers. So now mailman is configured to munge the headers
> *only* from senders which have a enforcing DMARC policy set, which
> xs4all.nl has. And because we're on shared resources our lists not
> following the DMARC rules would mess up all of the other lists.

 That's going to break patch submissions, isn't it?

  Maciej

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Tom Rini via U-Boot]

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

On Tue, Jul 21, 2026 at 05:27:41AM +0100, Maciej W. Rozycki wrote:
> On Mon, 20 Jul 2026, Tom Rini via U-Boot wrote:
> 
> > > Sadly it seems that the new list is (mis)configured to rewrite the
> > > From: header to something like:
> > > 
> > >   "John Doe via U-Boot <u-boot@lists.u-boot-project.org>"
> > > 
> > > Does it have to be that way?
> > 
> > So the answer is kinda. Whereas back on DENX we never "munged" emails
> > this is also why we likely often had big piles of unsubscribed due to
> > bounces (which was due to rejection from being incorrectly set as spam)
> > on the big providers. So now mailman is configured to munge the headers
> > *only* from senders which have a enforcing DMARC policy set, which
> > xs4all.nl has. And because we're on shared resources our lists not
> > following the DMARC rules would mess up all of the other lists.
> 
>  That's going to break patch submissions, isn't it?

Looks like it's working:
https://patchwork.ozlabs.org/project/uboot/patch/20260721063050.18756-1-dinesh.maniyam@altera.com/

Not my favorite that it's going to have "... via U-Boot" in patchwork
only. And we already have "... via B4 Relay" in others. We aren't the
only project OSU OSL is hosting mailman for, so I'd assume this is a
solved problem.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Maciej W. Rozycki via U-Boot]

On Tue, 21 Jul 2026, Tom Rini wrote:

> >  That's going to break patch submissions, isn't it?
> 
> Looks like it's working:
> https://patchwork.ozlabs.org/project/uboot/patch/20260721063050.18756-1-dinesh.maniyam@altera.com/

 It breaks for `git am' though, such as for picking up patches directly 
from the mailing list via the MUA (hmm, why hasn't this particular patch 
arrive here?).  There are other issues with the rewrite, such as the 
inability to sort messages by authors in the mailbox, but the former is 
possibly the most painful.

> Not my favorite that it's going to have "... via U-Boot" in patchwork
> only. And we already have "... via B4 Relay" in others. We aren't the
> only project OSU OSL is hosting mailman for, so I'd assume this is a
> solved problem.

 Yep, GNU toolchain lists I'm on that are used for patch distribution 
(such as <binutils@sourceware,org>, <gcc-patches@gcc.gnu.org>, but not 
<gcc-help@gcc.gnu.org>) simply disabled such rewriting, after numerous 
discussions (not sure what OSU OSL is though).

 Up to you to decide, I just wanted to share my concern.

  Maciej

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Quentin Schulz via U-Boot]

Hi Tom,

On 7/15/26 7:31 PM, Tom Rini wrote:
> Hey all,
> 
> As I've mentioned in previous release emails, we'll be migrating our
> lists over to lists.u-boot-project.org. The news now is that we have a
> date. This coming Monday the 20th of July, we'll be turning off the
> receiving side of lists.denx.de and then importing everything over to
> lists.u-boot-project.org.
> 
> What do you need to do? Nothing much. All active subscribers and their
> preferences will be moved. This includes how lore and patchwork are
> linked, so all of that will work. We are going to try and ensure no new
> emails get lost in the migration.
> 

OK but does that mean that whatever mail sent to the old mailing list 
won't make it to the new one once that cut off date is met (that is, 
yesterday... yes I'm really asking at the perfect time :) ). Essentially 
my question is: will we lose mails if they are *now* sent to the old 
mailing list. I'm assuming at some point in the future they will be? Is 
there a cut-off date for that?

> Based on feedback from the test migration, we believe we know what was
> missing to ensure that the archive links are stable, and so that should
> be the case when we go live again.
> 

I think we're missing an update to lore.kernel.org to monitor the new 
mailing list now? b4 shazam doesn't pick the trailers reviewers provide 
on the mailing list since that date unfortunately (due to the mails not 
appearing on lore.kernel.org I'm assuming).

I **think** there may be an issue with patchwork as well since I don't 
see my answers in there either, see 
https://patchwork.ozlabs.org/project/uboot/patch/af0ac32e2bf603c39f490f15fe62319fd73c5282.1784423864.git.daniel@makrotopia.org/, 
https://lore.kernel.org/u-boot/af0ac32e2bf603c39f490f15fe62319fd73c5282.1784423864.git.daniel@makrotopia.org/T/#u 
and 
https://lists.u-boot-project.org/pipermail/u-boot/2026-July/625465.html 
for an example.

Cheers,
Quentin

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Tom Rini via U-Boot]

[-- Attachment #1: Type: text/plain, Size: 2597 bytes --]

On Tue, Jul 21, 2026 at 04:52:17PM +0200, Quentin Schulz wrote:
> Hi Tom,
> 
> On 7/15/26 7:31 PM, Tom Rini wrote:
> > Hey all,
> > 
> > As I've mentioned in previous release emails, we'll be migrating our
> > lists over to lists.u-boot-project.org. The news now is that we have a
> > date. This coming Monday the 20th of July, we'll be turning off the
> > receiving side of lists.denx.de and then importing everything over to
> > lists.u-boot-project.org.
> > 
> > What do you need to do? Nothing much. All active subscribers and their
> > preferences will be moved. This includes how lore and patchwork are
> > linked, so all of that will work. We are going to try and ensure no new
> > emails get lost in the migration.
> > 
> 
> OK but does that mean that whatever mail sent to the old mailing list won't
> make it to the new one once that cut off date is met (that is, yesterday...
> yes I'm really asking at the perfect time :) ). Essentially my question is:
> will we lose mails if they are *now* sent to the old mailing list. I'm
> assuming at some point in the future they will be? Is there a cut-off date
> for that?

The good news is that we were able to setup forwarding correctly, so
there's nothing being lost at the moment. A final date is something we
need to talk about off-list with the people that have access to denx.de
infrastructure still.

Nothing is being missed in *our* archives.

> > Based on feedback from the test migration, we believe we know what was
> > missing to ensure that the archive links are stable, and so that should
> > be the case when we go live again.
> > 
> 
> I think we're missing an update to lore.kernel.org to monitor the new
> mailing list now? b4 shazam doesn't pick the trailers reviewers provide on
> the mailing list since that date unfortunately (due to the mails not
> appearing on lore.kernel.org I'm assuming).

Yes. I've been trying to reach out to helpdesk@kernel.org for a while
and not had luck, unfortunately.

> I **think** there may be an issue with patchwork as well since I don't see
> my answers in there either, see https://patchwork.ozlabs.org/project/uboot/patch/af0ac32e2bf603c39f490f15fe62319fd73c5282.1784423864.git.daniel@makrotopia.org/, https://lore.kernel.org/u-boot/af0ac32e2bf603c39f490f15fe62319fd73c5282.1784423864.git.daniel@makrotopia.org/T/#u
> and https://lists.u-boot-project.org/pipermail/u-boot/2026-July/625465.html
> for an example.

We also had a small window where patchwork wasn't updated (and I'm
talking with Jeremy to backfill that).

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Quentin Schulz via U-Boot]

On 7/21/26 5:05 PM, Tom Rini wrote:
> On Tue, Jul 21, 2026 at 04:52:17PM +0200, Quentin Schulz wrote:
>> Hi Tom,
>>
>> On 7/15/26 7:31 PM, Tom Rini wrote:
>>> Hey all,
>>>
>>> As I've mentioned in previous release emails, we'll be migrating our
>>> lists over to lists.u-boot-project.org. The news now is that we have a
>>> date. This coming Monday the 20th of July, we'll be turning off the
>>> receiving side of lists.denx.de and then importing everything over to
>>> lists.u-boot-project.org.
>>>
>>> What do you need to do? Nothing much. All active subscribers and their
>>> preferences will be moved. This includes how lore and patchwork are
>>> linked, so all of that will work. We are going to try and ensure no new
>>> emails get lost in the migration.
>>>
>>
>> OK but does that mean that whatever mail sent to the old mailing list won't
>> make it to the new one once that cut off date is met (that is, yesterday...
>> yes I'm really asking at the perfect time :) ). Essentially my question is:
>> will we lose mails if they are *now* sent to the old mailing list. I'm
>> assuming at some point in the future they will be? Is there a cut-off date
>> for that?
> 
> The good news is that we were able to setup forwarding correctly, so
> there's nothing being lost at the moment. A final date is something we
> need to talk about off-list with the people that have access to denx.de
> infrastructure still.
> 

Understood.

> Nothing is being missed in *our* archives.
> 

OK, that is good news :)

>>> Based on feedback from the test migration, we believe we know what was
>>> missing to ensure that the archive links are stable, and so that should
>>> be the case when we go live again.
>>>
>>
>> I think we're missing an update to lore.kernel.org to monitor the new
>> mailing list now? b4 shazam doesn't pick the trailers reviewers provide on
>> the mailing list since that date unfortunately (due to the mails not
>> appearing on lore.kernel.org I'm assuming).
> 
> Yes. I've been trying to reach out to helpdesk@kernel.org for a while
> and not had luck, unfortunately.
> 

Konstantin was on holidays until yesterday, maybe we need to poke again 
now that he's back (he's generally active on Mastodon too but I'm not 
sure that's good etiquette to ping him there :) ).

>> I **think** there may be an issue with patchwork as well since I don't see
>> my answers in there either, see https://patchwork.ozlabs.org/project/uboot/patch/af0ac32e2bf603c39f490f15fe62319fd73c5282.1784423864.git.daniel@makrotopia.org/, https://lore.kernel.org/u-boot/af0ac32e2bf603c39f490f15fe62319fd73c5282.1784423864.git.daniel@makrotopia.org/T/#u
>> and https://lists.u-boot-project.org/pipermail/u-boot/2026-July/625465.html
>> for an example.
> 
> We also had a small window where patchwork wasn't updated (and I'm
> talking with Jeremy to backfill that).
> 

Thanks!

Cheers,
Quentin

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 1470 bytes --]

On Tue, Jul 21, 2026 at 03:29:23PM +0100, Maciej W. Rozycki wrote:
> On Tue, 21 Jul 2026, Tom Rini wrote:
> 
> > >  That's going to break patch submissions, isn't it?
> > 
> > Looks like it's working:
> > https://patchwork.ozlabs.org/project/uboot/patch/20260721063050.18756-1-dinesh.maniyam@altera.com/
> 
>  It breaks for `git am' though, such as for picking up patches directly 
> from the mailing list via the MUA (hmm, why hasn't this particular patch 
> arrive here?).  There are other issues with the rewrite, such as the 
> inability to sort messages by authors in the mailbox, but the former is 
> possibly the most painful.
> 
> > Not my favorite that it's going to have "... via U-Boot" in patchwork
> > only. And we already have "... via B4 Relay" in others. We aren't the
> > only project OSU OSL is hosting mailman for, so I'd assume this is a
> > solved problem.
> 
>  Yep, GNU toolchain lists I'm on that are used for patch distribution 
> (such as <binutils@sourceware,org>, <gcc-patches@gcc.gnu.org>, but not 
> <gcc-help@gcc.gnu.org>) simply disabled such rewriting, after numerous 
> discussions (not sure what OSU OSL is though).
> 
>  Up to you to decide, I just wanted to share my concern.

So, thank you both, Maciej and Mark for bringing this up. I relayed this
back to OSU OSL again and it was indeed really a misconfiguration on the
migration and not a policy that we had to keep. It's now been fixed.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

Re: [ANN] Mailing list migration to lists.u-boot-project.org

[Tom Rini]

[-- Attachment #1: Type: text/plain, Size: 1765 bytes --]

On Wed, Jul 22, 2026 at 04:01:20PM -0600, Tom Rini wrote:
> On Tue, Jul 21, 2026 at 03:29:23PM +0100, Maciej W. Rozycki wrote:
> > On Tue, 21 Jul 2026, Tom Rini wrote:
> > 
> > > >  That's going to break patch submissions, isn't it?
> > > 
> > > Looks like it's working:
> > > https://patchwork.ozlabs.org/project/uboot/patch/20260721063050.18756-1-dinesh.maniyam@altera.com/
> > 
> >  It breaks for `git am' though, such as for picking up patches directly 
> > from the mailing list via the MUA (hmm, why hasn't this particular patch 
> > arrive here?).  There are other issues with the rewrite, such as the 
> > inability to sort messages by authors in the mailbox, but the former is 
> > possibly the most painful.
> > 
> > > Not my favorite that it's going to have "... via U-Boot" in patchwork
> > > only. And we already have "... via B4 Relay" in others. We aren't the
> > > only project OSU OSL is hosting mailman for, so I'd assume this is a
> > > solved problem.
> > 
> >  Yep, GNU toolchain lists I'm on that are used for patch distribution 
> > (such as <binutils@sourceware,org>, <gcc-patches@gcc.gnu.org>, but not 
> > <gcc-help@gcc.gnu.org>) simply disabled such rewriting, after numerous 
> > discussions (not sure what OSU OSL is though).
> > 
> >  Up to you to decide, I just wanted to share my concern.
> 
> So, thank you both, Maciej and Mark for bringing this up. I relayed this
> back to OSU OSL again and it was indeed really a misconfiguration on the
> migration and not a policy that we had to keep. It's now been fixed.

... in the case of domains (most of them, but *not* xs4all.nl) which
don't enforce DMARC but instead either aren't strict (most) or are
quarantine (kernel.org for example).

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]