On 9/24/2013 7:12 AM, Bradley D. Thornton wrote: > On 09/24/2013 01:29 AM, Stan Hoeppner wrote: >> On 9/24/2013 12:06 AM, Roberto Spadim wrote: >>> Hi Stan,Benjamin, Drew and others guys! >> >> You desire to drink champagne on a beer budget I'm afraid. You first ... > Please don't BCC the list - it whacks people's mail filters. either To: > or CC: is fine, but again, please don't BCC: the list okay? Hi Bradley, Thank you for scolding a mailop WRT the netiquette of BCC'ing a list. :) "Reply to all" shouldn't cause this. So what is the root cause? Hmm... let's see... Here we go. Take a look at the headers of Roberto's msg to which I replied: From: Roberto Spadim <rspadim@xxxxxxxxx> Cc: Linux-RAID <linux-raid@xxxxxxxxxxxxxxx> Content-Type: text/plain; charset=ISO-8859-1 To: unlisted-recipients:; (no To-header on input) This mangled header caused TBird's reply-all to do the following: To: Roberto Spadim <rspadim@xxxxxxxxx> CC: unlisted-recipients:;, Linux-RAID <linux-raid@xxxxxxxxxxxxxxx> I've never used the feature, but AIUI, this "unlisted-recipients" directive in TBird turns all subsequent CCs into BCCs. So, my apologies for concentrating on the content of my reply, and not paying closer attention to the headers before hitting send. That said, the root cause of this problem lay at the feet of Roberto, or his MUA, for mangling the headers. You may want to take this up with him, though I'm sure he'll see this msg. -- Stan -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
