From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stan Hoeppner Subject: Re: Best configuration for bcache/md cache or other cache using ssd Date: Tue, 24 Sep 2013 21:44:45 -0500 Message-ID: <52424E1D.5050007@hardwarefreak.com> References: <523A60DF.5040702@hardwarefreak.com> <523AAC1F.6050006@hardwarefreak.com> <523B1D1C.2070807@mpstor.com> <523B26E9.30608@mpstor.com> <523B3185.3020309@mpstor.com> <523B874D.4050904@hardwarefreak.com> <52414D81.4010104@hardwarefreak.com> <524181A6.6050303@NorthTech.US> <52424B46.6000107@hardwarefreak.com> Reply-To: stan@hardwarefreak.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <52424B46.6000107@hardwarefreak.com> Sender: linux-raid-owner@vger.kernel.org To: stan@hardwarefreak.com Cc: "Bradley D. Thornton" , linux-raid@vger.kernel.org List-Id: linux-raid.ids On 9/24/2013 9:32 PM, Stan Hoeppner wrote: > This mangled header caused TBird's reply-all to do the following: > > To: Roberto Spadim > CC: unlisted-recipients:;, Linux-RAID > > > I've never used the feature, but AIUI, this "unlisted-recipients" > directive in TBird turns all subsequent CCs into BCCs. Actually, upon further inspection, a BCC header isn't the issue, because there's not one, just the mangled CC: Illegal-Object: Syntax error in CC: address found on vger.kernel.org: CC: unlisted-recipients:;Linux-RAID ^-missing end of address vger simply replaced the broken CC header with a syntax error message. Thus a reply-all to this message will simply go to the sender and the non-broken CC list, i.e. to me and to Roberto, not the list. Regardless, the root of the problem lay with Roberto or his MUA for the original mangled header. -- Stan