OT: gmane address mangling selectors

From: Jeff King <peff-adepduraxsq@public.gmane.org>
Date: May 10, 2012, 17:19 UTC
Message-ID: <20120510171912.GA29972@sigill.intra.peff.net>
In-Reply-To: <7vd36cng6n.fsf-s2KvWo2KEQL18tm6hw+yZpy9Z0UEorGK@public.gmane.org>

On Thu, May 10, 2012 at 09:39:44AM -0700, Junio C Hamano wrote:

Show 7 quoted lines

> Jeff King <peff-AdEPDUrAXsQ@public.gmane.org> writes:
> 
> > PS It would have been nice to see the patch on the list for review. I
> >    only noticed it because it hit 'next', and had a minor conflict with
> >    my patches in the area.
> 
> Heh, it was sent before I gave you this message:

Ah, I never got that message. Probably because...

>         To: Jeff King <peff-AdEPDUrAXsQ-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org>

...I have no clue where that address would end up.

Show 5 quoted lines

> Junio C Hamano <gitster-e+AXbWqSrlAAvxtiuMwx3w-XMD5yJDbdMReXY1tMh2IBg@public.gmane.org> writes:
> 
>     Administrivia: these gmane-mangled e-mail addresses are extremely
>     annoying.  Please do not cross post with any insane list that choose
>     to turn that feature on when sending message to the git list; thanks.

Where do they come from? I notice that my address has been mangled above, but I do not use gmane to either post or read the list. In fact, looking at the start of the thread in my mailbox, I see:

  1. Eli posts[1], to: git@vger and magit@googlegroups; his from address
     looks normal, and there is no reply-to.

  2. You reply, to: a gmane-mangled address, cc: git@vger.

The presence of the magit list is obviously the unusual thing here, but he did not involve gmane at all. If I recall correctly, you read the list via gmane. So I believe it is your workflow that introduces the mangled addresses on the reading end, not the sender.

It seems that this gmane "feature" is turned on by the presence of the magit list, which I guess is configured at gmane to obfuscate emails. But I don't see how the sender should be expected to know or care about this gmane nonsense. It is your fault that the gateway through which you read the messages is doing the mangling. So the right fix is not to arbitrarily restrict cc-ing of other lists, but to fix the gmane bug[2].

-Peff

[1] mid:<20379.9312.943088.350379-a5nvgYPMCZcx/1z6v04GWfZ8FUJU4vz8@public.gmane.org>; the gmane link
    at http://thread.gmane.org/gmane.comp.version-control.git.magit/1308
    is mangled, but the original message as sent by vger looks fine (a
    copy of the headers that I received is included below).

[2] Without looking at the gmane code at all, I suspect the faulty logic
    is "mangle addresses for privacy if the message went to any list
    which requests this feature". But that is not right. The privacy was
    lost as soon as it went to any list that does _not_ mangle. And the
    unmangled version should be given to people accessing the sane list
    (it is slightly pointless to still mangle for the other list, since
    the privacy has been lost, but at least it is not actively bad). But
    given that my search for the mid at gmane turns up the magit
    version, I am guessing that they are storing only a single version
    of the message (mangled).

-- >8 --
Return-Path: <git-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Delivered-To: peff-AdEPDUrAXsQ@public.gmane.org
Received: (qmail 2012 invoked by uid 107); 28 Apr 2012 00:03:12 -0000
X-Spam-Level: *
X-Spam-Status: No, hits=-3.4 required=4.9
	tests=BAYES_00,KB_DATE_CONTAINS_TAB,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,TAB_IN_FROM
X-Spam-Check-By: peff.net
Received: from vger.kernel.org (HELO vger.kernel.org) (209.132.180.67)
    by peff.net (qpsmtpd/0.84) with ESMTP; Fri, 27 Apr 2012 20:03:07 -0400
Received: (majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org) by vger.kernel.org via listexpand
	id S1758065Ab2D1ACs (ORCPT <rfc822;peff-AdEPDUrAXsQ@public.gmane.org>);
	Fri, 27 Apr 2012 20:02:48 -0400
Received: from winooski.ccs.neu.edu ([129.10.115.117]:52945 "EHLO
	winooski.ccs.neu.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1757659Ab2D1ACg (ORCPT <rfc822;git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>);
	Fri, 27 Apr 2012 20:02:36 -0400
X-Greylist: delayed 3897 seconds by postgrey-1.27 at vger.kernel.org; Fri, 27 Apr 2012 20:02:36 EDT
Received: from winooski.ccs.neu.edu (localhost.localdomain [127.0.0.1])
	by winooski.ccs.neu.edu (8.14.4/8.14.4) with ESMTP id q3RMvbEt019273;
	Fri, 27 Apr 2012 18:57:37 -0400
Received: (from eli@localhost)
	by winooski.ccs.neu.edu (8.14.4/8.14.4/Submit) id q3RMvbHJ019269;
	Fri, 27 Apr 2012 18:57:37 -0400
From:	Eli Barzilay <eli-oSK4jVRJLyZg9hUCZPvPmw@public.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <20379.9312.943088.350379-a5nvgYPMCZcx/1z6v04GWfZ8FUJU4vz8@public.gmane.org>
Date:	Fri, 27 Apr 2012 18:57:36 -0400
To:	git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, magit-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Bug in git-stash(.sh) ?
X-Mailer: VM 8.2.0a under 23.2.1 (x86_64-redhat-linux-gnu)
Sender:	git-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Precedence: bulk
List-ID: <git.vger.kernel.org>
X-Mailing-List:	git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Status: RO
Content-Length: 3206
Lines: 100