On 07/10/15 18:36, Jordan Justen wrote: > On 2015-07-10 04:29:11, Laszlo Ersek wrote: >> On 07/10/15 10:40, Wu, Jiaxin wrote: >>> Yes, edk2-devel will strip it. You can check version2 for those >>> series patches, I had added someone with cc tag to the commit >>> message, but it haven't actually cc to those people. >> >> (3) Laszlo will get a copy directly from you, and another copy >> *reflected* from the mailing list server. (Laszlo has mail filters in >> place that file the direct copy into his INBOX, and the reflected copy >> into his edk2-devel folder.) >> >> The copy that Laszlo directly gets from Jiaxin will have the following >> headers: >> >> From: Jiaxin >> To: edk2-devel >> Cc: Laszlo >> >> The copy that Laszlo gets from the mailing list server will have the >> following headers: >> >> From: Jiaxin >> To: edk2-devel >> >> This is because the mailing list server is *stupid*. It sees, in its >> internal database, that Laszlo is subscribed, and therefore thinks >> (completely incorrectly) that Laszlo should not be Cc:-d on messages >> reflected from the list, "because he gets them anyway". > > I found that mailman has a 'nodupes' setting that causes the Cc > stripping. I've disabled it for the new edk2-devel list. Hopefully > that is the setting we want...
I do know about a similarly named mailman feature. It is related, but not the same thing. The "nodupes" setting (if it is indeed the one I have in mind, and have used several times before) controls whether the mailing list software *reflects* the message to someone at all. That is, in bullet (3) above, with nodupes=off, Laszlo gets two copies (one from Jiaxin directly, and another from the list). With nodupes=on, Laszlo would get *no* copy from the list -- the list software would see that Laszlo was Cc'd on the original message, and therefore forego reflecting the message to Laszlo *at all*. Obviously, this would wreak havoc with Laszlo's email filters; those really depend on getting *two* copies. But, others like to get one copy only, under similar circumstances. This is why, in my understanding, the "nodupes" setting is actually subscriber-level: the list may have a top-level default, but each subscriber can change that setting for himself, after logging in with his password on the list web GUI. So, I very much agree that the nodupes default should be "off" for the new list. However, the current list has a different problem. It does work correctly as far as "nodupes=off" is concerned (ie. it does reflect messages to originally Cc'd people as well). The problem is that it mangles those reflected messages: it strips the Cc fields that designate subscribers. > Unfortunately, disabling it on the current list would be a hassle. I guess. :) ... Apologies about the verbiage. Thanks! Laszlo ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
