linux-btrfs.tebulin posted on Fri, 20 Nov 2015 10:38:33 +0100 as excerpted:
> Am 20.11.2015 um 04:14 schrieb Duncan: >> Meta-comment: >> >> Apparently that attribution should actually be to Hugo Mills. I've no >> idea what went wrong, but at least here as received from gmane.org, the >> from header really does say linux-btrfs.tebulin, so something obviously >> bugged out somewhere! > > Meta-Answer: My fault > > I accidentally exposed my spamgourmet proxy address to Hugo by taking > him CC. He replied to all assuming it would go directly to the list, but > the proxy address masked his original address an put id in it. > > Sorry for messing up! Makes sense. While I suppose his reply to all went to the list and to the proxy, the proxy bounced it, presumably with the same message-id, and anything that tracks by message-id (including my client), which is supposed to be unique and thus usable for message tracking, would see only one of the two. Which one would depend on which one got to it first, and whether it took that and refused the other one, or let the second one override the first. Either way, definitely confusing, but at least there's a reasonable explanation now. Thanks for helping to clear that up! =:^) (FWIW, as with most linux kernel lists, replying to all is customary. I generally reply only to the list, however, because it's far easier with my specific setup, tho I'll reply to author as well if specifically requested. But Hugo actually does the list-recommended thing by replying to all by default.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
