From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "André Draszik" <git@andred.net>,
"Ross Burton" <ross.burton@intel.com>,
"Andreas Müller" <schnitzeltony@gmail.com>,
"Nicolas Dechesne" <nicolas.dechesne@linaro.org>
Cc: Michael Halstead <mhalstead@linuxfoundation.org>,
yocto@lists.yoctoproject.org
Subject: Re: [yocto] mailing list mangling name?
Date: Mon, 13 Jan 2020 13:52:02 +0000 [thread overview]
Message-ID: <eb80ac740d24bcea10dfe56d4816062f515bfbe5.camel@linuxfoundation.org> (raw)
In-Reply-To: <ef7a6099ca79e3032ee02d912e5b953c5ba1a720.camel@andred.net>
On Sun, 2020-01-12 at 08:01 +0000, André Draszik wrote:
> On a related note,
>
> It appears groups.io is generating a new Message-Id header:
>
> Message-Id: <15E914A621406CC1.15008@lists.yoctoproject.org>
> X-Orig-Message-Id: <
> f868f741ae07674cb99e2b0c4ea6f7621ca16474.camel@andred.net>
>
> Is this behaviour expected?
If the lists reprocess the message (which they have to when sending
email back to yourself for example), the ID would change. A lot of the
behaviour now depends on the sender domain policies in place, one
reason we needed to move to groups.io as this is all getting too
complex to maintain as a project :(
Cheers,
Richard
prev parent reply other threads:[~2020-01-13 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15E744ED02F41EEB.31817@lists.yoctoproject.org>
2020-01-08 14:45 ` mailing list mangling name? Andr? Draszik
2020-01-10 17:28 ` [yocto] " Nicolas Dechesne
2020-01-11 12:26 ` Andreas M?ller
2020-01-11 22:43 ` Ross Burton
2020-01-11 22:54 ` pfl
2020-01-12 7:57 ` André Draszik
[not found] ` <15E914A621406CC1.15008@lists.yoctoproject.org>
2020-01-12 8:01 ` André Draszik
2020-01-13 13:52 ` Richard Purdie [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=eb80ac740d24bcea10dfe56d4816062f515bfbe5.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=git@andred.net \
--cc=mhalstead@linuxfoundation.org \
--cc=nicolas.dechesne@linaro.org \
--cc=ross.burton@intel.com \
--cc=schnitzeltony@gmail.com \
--cc=yocto@lists.yoctoproject.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.