linux-kernel - Re: List stripping out cc's

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <46C8A3BB.5020505@qumranet.com>
Date:	Sun, 19 Aug 2007 23:10:35 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Jeff Garzik <jeff@...zik.org>
CC:	Heiko Carstens <heiko.carstens@...ibm.com>,
	Christian Borntraeger <borntraeger@...ibm.com>,
	kvm-devel@...ts.sourceforge.net,
	Laurent Vivier <Laurent.Vivier@...l.net>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	virtualization <virtualization@...ts.linux-foundation.org>,
	cotte@...ibm.com
Subject: Re: List stripping out cc's

Jeff Garzik wrote:
> 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.
>

Sorry, this was about kvm-devel, not lkml -- I should have taken
linux-kernel off the cc list here to avoid increasing confusion. 
Somehow that felt wrong in an email about the evils of stripping out the
cc list.

I don't think there's an issue with M-F-T: here.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/