From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.u-boot-project.org,
u-boot-board-maintainers@lists.u-boot-project.org,
u-boot-custodians@lists.u-boot-project.org
Subject: Re: [ANN] Further mailman updates
Date: Wed, 19 Aug 2026 09:53:29 -0600 [thread overview]
Message-ID: <20260819155329.GA1507897@bill-the-cat> (raw)
In-Reply-To: <20260813201711.GH3297518@bill-the-cat>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
On Thu, Aug 13, 2026 at 02:17:11PM -0600, Tom Rini wrote:
> Hey all,
>
> As some people have noticed, with the move to lists.u-boot-project.org
> (and OSU OSL hosting), there's been some behavior changes for how people
> who use an email provider with a DMARC policy set to reject (for when
> certain actions happen). This in turn lead to some rewrites, and then
> things like patchwork (now updated I think) or lore (is append-only) not
> seeing posts as expected (but seeing them as the email policy wanted
> them to be seen). The good news here is that we can get the lists
> changed to the same behavior we used to have (which also means that
> gmail might see us as spam more often, but... who knows). For the two
> low traffic list (board-maintainers, custodians) this change has been
> done now. For the main list itself, this should happen sometime Monday
> morning pacific, and monitored for problems.
A few updates. First, this has gone live now for the main mailing list
now. Second, after a report from E Shattow we found two other
configuration problems with the overall email policies, and they've now
also been resolved.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-08-19 15:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-13 20:17 [ANN] Further mailman updates Tom Rini
2026-08-14 2:39 ` Marek Vasut via U-Boot
2026-08-19 15:53 ` Tom Rini [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=20260819155329.GA1507897@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot-board-maintainers@lists.u-boot-project.org \
--cc=u-boot-custodians@lists.u-boot-project.org \
--cc=u-boot@lists.u-boot-project.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.