From: Mark Wielaard <mark@klomp.org>
To: Sam James <sam@gentoo.org>
Cc: Florian Weimer <fweimer@redhat.com>,
Jakub Jelinek <jakub@redhat.com>, Andreas Schwab <schwab@suse.de>,
Joseph Myers <joseph@codesourcery.com>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
libc-alpha@sourceware.org
Subject: Re: dmarc, dkim and From rewriting
Date: Fri, 8 Sep 2023 19:21:18 +0200 [thread overview]
Message-ID: <20230908172118.GB28313@gnu.wildebeest.org> (raw)
In-Reply-To: <20230906184940.GA19396@gnu.wildebeest.org>
On Wed, Sep 06, 2023 at 08:49:40PM +0200, Mark Wielaard wrote:
> On Mon, Sep 04, 2023 at 10:48:39AM +0200, Mark Wielaard wrote:
> > On irc people also seemed really enthousiastic about this. I did some
> > more analysis on the libc-alpha messages sent this year [*] and I
> > think things will work out fine. So I propose we just try it out.
> >
> > Lets flip the switch (there are actually multiple switches, I'll
> > document them in the bug) on Wednesday 18:00 UTC.
>
> This is now active. The mailinglist settings are as described in
> https://sourceware.org/bugzilla/show_bug.cgi?id=29713#c45
>
> > Then we can monitor
> > things and analyze whether things worked as expected after 48 hours at
> > the Overseers Open Office Hour this Friday at 18:00 UTC in #overseers
> > on irc.libera.chat.
In about an hour we'll evaluate this in #overseers on irc.libera.chat
Please let us know if this works/doesn't work and/or causes any mail
issues.
> > That might also be a good time to discuss any other glibc service
> > blockers. For example, it would be great to figure out how to use
> > builder.sourceware.org workers for patchwork.sourceware.org testing.
>
> And please feel free to drop by in #overseers whenever you like and/or
> to report issues through mail or bugzilla as described at:
> https://sourceware.org/mission.html#organization
>
> > [*] https://sourceware.org/bugzilla/show_bug.cgi?id=29713#c44
Every second Friday of the month is the Sourceware Overseers Open
Office hour in #overseers on irc.libera.chat from 18:00 till 19:00
UTC. That is today Friday September 8th.
Please feel free to drop by with any Sourceware services and hosting
questions. We will be evaluating switching off From rewriting for the
glibc libc-alpha list to see if other Sourceware mailinglist can adopt
that.
Feedback and questions about the Sourceware 25 Roadmap are also very
appreciated. https://sourceware.org/sourceware-25-roadmap.html
Of course you are welcome to drop into the #overseers channel at any
time and we can also be reached through email and bugzilla:
https://sourceware.org/mission.html#organization
If you aren't already and want to keep up to date on Sourceware
infrastructure services then please also subscribe to the overseers
mailinglist. https://sourceware.org/mailman/listinfo/overseers
We are also on the fediverse these days:
https://fosstodon.org/@sourceware
next prev parent reply other threads:[~2023-09-08 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 8:48 Mark Wielaard
2023-09-06 18:49 ` Mark Wielaard
2023-09-08 17:21 ` Mark Wielaard [this message]
[not found] <b84ea4a5-651a-1a4c-06c8-e9ade4b7d702@redhat.com>
2023-08-30 17:19 ` [Action Required] glibc decision to use CTI services Alexandre Oliva
2023-08-30 17:31 ` Joseph Myers
2023-08-31 19:59 ` Paul Eggert
2023-09-01 6:03 ` Sam James
2023-09-01 8:55 ` Florian Weimer
2023-09-01 9:02 ` Sam James
2023-09-01 9:21 ` dmarc, dkim and From rewriting Mark Wielaard
2023-09-01 11:52 ` Florian Weimer
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=20230908172118.GB28313@gnu.wildebeest.org \
--to=mark@klomp.org \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=sam@gentoo.org \
--cc=schwab@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).