From: Peter Korsgaard <peter@korsgaard.com>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] Buildroot patchwork strange Submitter
Date: Sun, 10 Oct 2021 10:17:27 +0200 [thread overview]
Message-ID: <87k0ils38o.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <9a43025b2c5eb6be4848e07ff761e6a86080e50c.camel@ozlabs.org> (Jeremy Kerr's message of "Sun, 10 Oct 2021 10:54:32 +0800")
>>>>> "Jeremy" == Jeremy Kerr <jk@ozlabs.org> writes:
Hi,
> Hi Baruch,
>> You can see that the 'From' header shows the correct sender:
>>
>> From: Yair Ben-Avraham via buildroot <buildroot@buildroot.org>
> That's not really the correct sender; it's been modified by the list
> software.
>> I see the same in this email from my archive.
>>
>> Still, patchwork previously used my name as "Submitter", and now
>> Christian's. So I think something is wrong with patchwork.
> Yep, we try to find the correct sender if the From: header reports the
> list address as the sender.
> However, the buildroot list has changed back-and-forth between
> buildroot@lists.buildroot.org and buildroot@buildroot.org a couple of
> times recently. The list address was set to
> buildroot@lists.buildroot.org, which didn't match that 'via' header.
> I've since set it to buildroot@buildroot.org, so the reverse-dmarc-fix
> should work again - let me know how it goes.
Yes, sorry about that all of you, it should all be back stable again.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-10-10 8:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 5:13 [Buildroot] Buildroot patchwork strange Submitter Baruch Siach via buildroot
2021-10-07 6:01 ` Yann E. MORIN
2021-10-09 19:26 ` Baruch Siach via buildroot
2021-10-10 2:54 ` Jeremy Kerr
2021-10-10 8:17 ` Peter Korsgaard [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=87k0ils38o.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=jk@ozlabs.org \
--cc=yann.morin.1998@free.fr \
/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