From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=134.134.136.31; helo=mga06.intel.com; envelope-from=michael.d.kinney@intel.com; receiver=edk2-devel@lists.01.org Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 3C15521A00AE6 for ; Mon, 29 Oct 2018 15:40:07 -0700 (PDT) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Oct 2018 15:40:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,441,1534834800"; d="scan'208";a="104330214" Received: from orsmsx109.amr.corp.intel.com ([10.22.240.7]) by orsmga002.jf.intel.com with ESMTP; 29 Oct 2018 15:40:07 -0700 Received: from orsmsx113.amr.corp.intel.com ([169.254.9.125]) by ORSMSX109.amr.corp.intel.com ([169.254.11.196]) with mapi id 14.03.0415.000; Mon, 29 Oct 2018 15:40:07 -0700 From: "Kinney, Michael D" To: Leif Lindholm , "Kinney, Michael D" CC: EDK II Development , "Cetola, Stephano" Thread-Topic: [edk2] ** NOTICE ** edk2-devel mailing list configuration changes Thread-Index: AdRvtv/s64HfbFm7QEKQKyRPm2vo2gARNf2AAA4YZWD//5wYAIAAdO1A//+TZYCAAG6gYA== Date: Mon, 29 Oct 2018 22:40:06 +0000 Message-ID: References: <20181029195415.t63zjpz6byuveqne@bivouac.eciton.net> <20181029204016.yeweqvts2cnsbulz@bivouac.eciton.net> <20181029211003.4sz5vwzvldveiev5@bivouac.eciton.net> In-Reply-To: <20181029211003.4sz5vwzvldveiev5@bivouac.eciton.net> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.22.254.139] MIME-Version: 1.0 Subject: Re: ** NOTICE ** edk2-devel mailing list configuration changes X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2018 22:40:08 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Leif, I can put the reply_goes_to_list option back to "Poster". In that configuration, a user that has a DMARC policy of reject will still have their from address munged. But I noticed that the edk2-devel mailing list is not present when anyone does a Reply-all to an email with a munged from address. That implied to me that everyone would need to check if the edk2-devel mailing has been removed from a Reply-all and add it back manually. This also seems like a non-ideal configuration option. However, the behavior I am seeing could be due to some of my client settings. So I will put the reply_goes_to_list option back to "Poster". Mike > -----Original Message----- > From: Leif Lindholm [mailto:leif.lindholm@linaro.org] > Sent: Monday, October 29, 2018 2:10 PM > To: Kinney, Michael D > Cc: EDK II Development ; > Cetola, Stephano > Subject: Re: [edk2] ** NOTICE ** edk2-devel mailing list > configuration changes >=20 > Hi Mike, >=20 > I could hypothesise about which email client you may be > using :) >=20 > But let me instead mention that the two email clients I > have (mutt and > gmail web interface) behave identically - neither adds > the original > sender to cc when the list server forces a reply-to > header. >=20 > Regards, >=20 > Leif >=20 > On Mon, Oct 29, 2018 at 08:49:09PM +0000, Kinney, > Michael D wrote: > > Leif, > > > > Very strange. When I do the same on that email, it > > shows Paul on the To address line. > > > > Mike > > > > > -----Original Message----- > > > From: Leif Lindholm > [mailto:leif.lindholm@linaro.org] > > > Sent: Monday, October 29, 2018 1:40 PM > > > To: Kinney, Michael D > > > Cc: EDK II Development ; > > > Cetola, Stephano > > > Subject: Re: [edk2] ** NOTICE ** edk2-devel mailing > list > > > configuration changes > > > > > > 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 > > > > > Cc: Kinney, Michael D > ; > > > > > Cetola, Stephano > > > > > 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