From: Leif Lindholm <leif.lindholm@linaro.org>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: EDK II Development <edk2-devel@lists.01.org>,
"Cetola, Stephano" <stephano.cetola@intel.com>
Subject: Re: ** NOTICE ** edk2-devel mailing list configuration changes
Date: Mon, 29 Oct 2018 20:40:16 +0000 [thread overview]
Message-ID: <20181029204016.yeweqvts2cnsbulz@bivouac.eciton.net> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B8B1D593@ORSMSX113.amr.corp.intel.com>
Hi Mike,
When I try to "reply-to", the email from Paul A Lohr, sent 10 minutes
after your one below, he does not show up in either "to" or "cc".
OK, I missed the excitement during the plugfest. I'll go back and see
what I can find there.
Regards,
Leif
On Mon, Oct 29, 2018 at 08:23:43PM +0000, Kinney, Michael D wrote:
> Leif,
>
> I have enabled a different configuration setting
> that should be better.
>
> Please try some emails and let me know if there
> are any impacts.
>
> The reason for these changes is the DMARC related
> issue that occurred on 10-19-2018 that required a
> number of users to be disabled. The goal of these
> changes is to enable those users to be re-activated.
>
> Thanks,
>
> Mike
>
> > -----Original Message-----
> > From: Leif Lindholm [mailto:leif.lindholm@linaro.org]
> > Sent: Monday, October 29, 2018 12:54 PM
> > To: EDK II Development <edk2-devel@lists.01.org>
> > Cc: Kinney, Michael D <michael.d.kinney@intel.com>;
> > Cetola, Stephano <stephano.cetola@intel.com>
> > Subject: Re: [edk2] ** NOTICE ** edk2-devel mailing list
> > configuration changes
> >
> > Hi Mike,
> >
> > On Mon, Oct 29, 2018 at 06:42:44PM +0000, Kinney,
> > Michael D wrote:
> > > Some configuration changes have been made to
> > > the edk2-devel mailing list to handle posts from
> > > a domain with a DMARC Reject/Quarantine policy
> > > enabled. If this is detected then the from address
> > > is now munged.
> > >
> > > One side effect of this setting is that the
> > > behavior of Reply has changed. Instead of being
> > > a reply to the poster of the message, the Reply
> > > address is the edk2-devel mailing list.
> >
> > The behaviour looks somewhat broken, since as far as I
> > can tell,
> > replies now longer include the person you're replying
> > to.
> > (This doesn't happen when replying specifically to
> > _you_, because you
> > cc yourself on everything).
> >
> > > If you wish to send a private reply to only the
> > > poster of the message, you may have to perform
> > > some manual steps.
> > >
> > > Please let me know if you have any concerns about
> > > these changes or if these configuration changes
> > > cause any other side effects.
> >
> > Can we make sure the person being replied to is at least
> > on cc?
> > Otherwise, we've just broken the workflow for anyone
> > filtering on
> > whether they are on "to" or "cc".
> >
> > Why was this change necessary?
> >
> > Regards,
> >
> > Leif
next prev parent reply other threads:[~2018-10-29 20:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 18:42 ** NOTICE ** edk2-devel mailing list configuration changes Kinney, Michael D
2018-10-29 19:54 ` Leif Lindholm
2018-10-29 20:23 ` Kinney, Michael D
2018-10-29 20:40 ` Leif Lindholm [this message]
2018-10-29 20:49 ` Kinney, Michael D
2018-10-29 21:10 ` Leif Lindholm
2018-10-29 22:11 ` Carsey, Jaben
2018-10-29 22:40 ` Kinney, Michael D
2018-10-30 8:49 ` Leif Lindholm
2018-10-30 14:58 ` Brian J. Johnson
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-list 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=20181029204016.yeweqvts2cnsbulz@bivouac.eciton.net \
--to=devel@edk2.groups.io \
/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