From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-2.7 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_NONE,SPF_PASS shortcircuit=no autolearn=no autolearn_force=no version=3.4.0 Received: from mail-it0-x243.google.com (mail-it0-x243.google.com [IPv6:2607:f8b0:4001:c0b::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id DBDB91FC44 for ; Tue, 14 Feb 2017 04:41:54 +0000 (UTC) Received: by mail-it0-x243.google.com with SMTP id r141so2875228ita.1 for ; Mon, 13 Feb 2017 20:41:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=o4kGNS5bE4B3c0WBXbCeYNXMcL18wqVOJP1awMD74PI=; b=Gus0tz0MkDaAfcPns06/iOEKJvYL+9hPH/e++61WtNSaqx9PyCnu79OpkM9ff6P14C QxyIUvzq6Uxrmju676waLqg6IcxymgCfrjKoWI5+ZD+cr7vpeGBJ04CeVchBfDUFaNlN 3zNRknXXEMmqZQGCRHr4/nwTzSa47lm0QpgDRPUVsmP05GjhtLF6LDlSN0Wxw5g6AWDr qrRXKtG7AQM5QJMfOnfE4LbrUrYX8cgxAvK2znTuUh2iC1Z82lj7giSFhQO4CqmzZXUZ CZPM5xRL3UWXmskIki4QuBvVqssqGC7PiAM9b2ksvi9nVhbtKGZLussM2FZVk25JA2A3 3CTQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:subject:references:date :in-reply-to:message-id:user-agent:mime-version; bh=o4kGNS5bE4B3c0WBXbCeYNXMcL18wqVOJP1awMD74PI=; b=Gk7D8JEpIdP1h06R+S4KdPI3ssKiEOBdFvVjJKU6bV3pMDmu54C6ec4eeook0ypbu7 YmkJa18q/noMD5IKmtwLZC+df0j9+owTOx/hJuGdOm84l8H35qLN6nCqTVt5TS5IW5lE D4UiCJCsWfWyoJs9nKzfl85OJjy/Mw23jN0LjRtl2TT1Zfwd2B9ZZ/VFBuML+7jSEJDP OEmTxTx9sbcfwCZXZbsI9IaZUcSZeMn7bu1HyHWpvKbzlsLx/mgB+2Mw0JzbQyy0McDq 2jIN5EG9DppByANjEZBzT2m62biPSjc0+92KNJN/qdEoqINBAxPHfCmFbZpEZXWOXTeG JzqQ== X-Gm-Message-State: AMke39mPzUcpp2S378/kYp0ydkYhFbvAG5jUJ06Di5IzShrPBIgZbFY1MsYCf2otj0PRpw== X-Received: by 10.84.132.1 with SMTP id 1mr34117392ple.44.1487047314249; Mon, 13 Feb 2017 20:41:54 -0800 (PST) Received: from localhost ([2620:0:1000:8622:d0e0:42a7:601f:5154]) by smtp.gmail.com with ESMTPSA id l25sm17368758pfg.134.2017.02.13.20.41.52 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Mon, 13 Feb 2017 20:41:52 -0800 (PST) Sender: Junio C Hamano From: Junio C Hamano To: Arif Khokar Cc: Johannes Schindelin , Arif Khokar , Jakub =?utf-8?Q?Nar=C4=99bski?= , Jeff King , Stefan Beller , "meta\@public-inbox.org" , "git\@vger.kernel.org" , Eric Wong Subject: Re: Working with public-inbox.org [Was: [PATCH] rev-parse: respect core.hooksPath in --git-path] References: <20160819150340.725bejnps6474u2e@sigill.intra.peff.net> <46a5b9b6-f3f6-7650-8a5b-b0b52223e375@gmail.com> Date: Mon, 13 Feb 2017 20:41:51 -0800 In-Reply-To: (Arif Khokar's message of "Mon, 13 Feb 2017 22:55:49 -0500") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.91 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain List-Id: Arif Khokar writes: > One concern I have regarding this idea is whether or not SMTP servers > typically replace a Message-Id header set by the client. The clients are supposed to give Message-IDs, but because some clients fail to do so, SMTP server implementations are allowed to add an ID to avoid leaving a message nameless (IIRC, 6.3 in RFC2821). So "replace" would be in violation. But some parts of the world ignore RFCs, so...