From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: List stripping out cc's Date: Sun, 19 Aug 2007 15:53:46 -0400 Message-ID: <46C89FCA.3010802@garzik.org> References: <46BC8B39.6050202@bull.net> <200708131615.42643.borntraeger@de.ibm.com> <46C06885.3020908@qumranet.com> <200708131626.36275.borntraeger@de.ibm.com> <46C06CA2.8010303@qumranet.com> <20070813204023.GA10283@osiris.ibm.com> <46C80E40.9@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Laurent Vivier , linux-kernel , virtualization , Christian Borntraeger To: Avi Kivity Return-path: In-Reply-To: <46C80E40.9-atKUWr5tajBWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Avi Kivity wrote: > Heiko Carstens wrote: >>> The only thing remotely relevant in the list config is that 'Filter >>> out duplicate messages to list members (if possible)' is set as a >>> default for new members. Maybe this means that if a cc is also part >>> of the list, that cc is stripped (which seems a wierd >>> implementation; I'd have expected that cc be kept and just one copy >>> sent out). >>> >>> Anybody have a clue? >>> >> >> I got also removed when I was cc'ed. IIRC that started when I >> subscribed to >> the list. So it looks like people who are subscribed to the list get >> removed from the cc list. >> That's very annoying btw. ;) >> > > I think I see what is happening. The list gets a message that you are > copied on. It sees you have opted not to receive duplicates, it strips > you from the cc list, since it knows that you will receive another copy > by direct routing (outside the list). Well, there is also /quite/ the problem with the Mail-Followup-To header, which causes most mailers to ignore the preferences of the community in favor of the preferences of the message author -- which totally screws up traditional To/CC handling on LKML. Jeff ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/