From: Stan Hoeppner <stan@hardwarefreak.com>
To: stan@hardwarefreak.com
Cc: "Bradley D. Thornton" <Bradley@NorthTech.US>, linux-raid@vger.kernel.org
Subject: Re: Best configuration for bcache/md cache or other cache using ssd
Date: Tue, 24 Sep 2013 21:44:45 -0500 [thread overview]
Message-ID: <52424E1D.5050007@hardwarefreak.com> (raw)
In-Reply-To: <52424B46.6000107@hardwarefreak.com>
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 <rspadim@gmail.com>
> CC: unlisted-recipients:;, Linux-RAID <linux-raid@vger.kernel.org>
>
>
> 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 <linux-raid@vger.kernel.org>
^-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
next prev parent reply other threads:[~2013-09-25 2:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 19:20 Best configuration for bcache/md cache or other cache using ssd Roberto Spadim
2013-09-18 13:59 ` Drew
[not found] ` <CAH3kUhHin5PfjDCNFjD8eypNML=0YrkQp14DrCADc2StcODdaw@mail.gmail.com>
2013-09-18 15:39 ` Fwd: " Drew
2013-09-18 16:00 ` Mark Knecht
2013-09-18 15:51 ` Fwd: " Roberto Spadim
2013-09-18 16:07 ` Tommy Apel
[not found] ` <CAH3kUhEWUe=20ovmd5BT3kzmYn25YS3Np5R3jPiJDBEAhAOb_A@mail.gmail.com>
2013-09-18 16:27 ` Tommy Apel
2013-09-18 17:15 ` Drew
2013-09-18 17:33 ` Roberto Spadim
2013-09-19 2:26 ` Stan Hoeppner
2013-09-19 3:42 ` Roberto Spadim
2013-09-19 7:47 ` Stan Hoeppner
2013-09-19 15:30 ` Roberto Spadim
2013-09-19 15:49 ` Benjamin ESTRABAUD
2013-09-19 16:23 ` Roberto Spadim
2013-09-19 16:31 ` Benjamin ESTRABAUD
[not found] ` <CAH3kUhE33h=7D6r7KO9VvQRN5qrZS+cad KUBQW8POFYvyGsS3w@mail.gmail.com>
[not found] ` <523B3185.3020309@mpstor.com>
2013-09-19 23:22 ` Stan Hoeppner
2013-09-24 5:06 ` Roberto Spadim
2013-09-24 6:11 ` Roberto Spadim
2013-09-24 7:18 ` Tommy Apel
2013-09-24 8:29 ` Stan Hoeppner
2013-09-24 12:12 ` Bradley D. Thornton
2013-09-25 2:32 ` Stan Hoeppner
2013-09-25 2:44 ` Stan Hoeppner [this message]
2013-09-25 4:35 ` Roberto Spadim
2013-09-25 5:53 ` Stan Hoeppner
2013-09-19 22:15 ` Stan Hoeppner
2013-09-19 22:50 ` Roberto Spadim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52424E1D.5050007@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=Bradley@NorthTech.US \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).