Re: SMTP RFC: "MUST NOT" change or delete Received header

Hector Santos <hsantos@isdg.net> Mon, 31 March 2014 11:57 UTC

Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBFE61A07C2 for <ietf@ietfa.amsl.com>; Mon, 31 Mar 2014 04:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.002
X-Spam-Level:
X-Spam-Status: No, score=-100.002 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_64=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A89uySG7mLnk for <ietf@ietfa.amsl.com>; Mon, 31 Mar 2014 04:57:55 -0700 (PDT)
Received: from news.winserver.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id AF29D1A07B8 for <ietf@ietf.org>; Mon, 31 Mar 2014 04:57:54 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1627; t=1396267062; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=B14UF3phl+oPM98x7jSSU+10w8A=; b=BFRliLmAFEJ8hPqHF3l/ xX7VzgJmmkX6hhaHb8/cNe3ejM7Ws8Oo9LdX/6NXd0Sf/BfGctp8a2ZL7KgebV+4 v5bqHj02CPTKzygiQSJjdERSmSMm2NZ9ijrKwuVtn34gVkZtYVSN15hKCeECgkDw ogrphNVRxPeAnjLn2791YDo=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 31 Mar 2014 06:57:42 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1254522625.12698.4476; Mon, 31 Mar 2014 06:57:41 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1627; t=1396267020; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=0Nw8Bb9 KdGioMyi7RlQleRdjwLEbypu9KSO88iPivso=; b=A5d4IbtUt8hHQ74u2D+S5aw v3oHev6RGzifpGdOj3BcApe/Sopvng20Do7nQOVFBVUVL0qKgweGI1jf9teeuEao dyf3rhj7Qug2gNdgUfFKIve83knjk0AeuSq770RRERSiJzjlGtQypnFstfvLeF2l LADjLIR6tLbeyr7HhdXI=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 31 Mar 2014 07:57:00 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 700775741.9.16428; Mon, 31 Mar 2014 07:56:59 -0400
Message-ID: <53395831.6060801@isdg.net>
Date: Mon, 31 Mar 2014 07:57:37 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>, Scott Brim <scott.brim@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: SMTP RFC: "MUST NOT" change or delete Received header
References: <mailman.1570.1395964793.2468.ietf@ietf.org> <53366F34.8050501@ageispolis.net> <5336979B.6000102@cisco.com> <0AF4D5B8-C99C-4944-87FA-A458D6CE67D9@nominum.com> <5336F1EF.1020203@dcrocker.net> <CAPv4CP9nFmYfondSrqA7ETkhvCMe4YrqRjOdGZuPiLz2kZzXrw@mail.gmail.com> <5336F9A8.5050305@isdg.net> <775a8b23bb97437992aa191457a1225b@BLUPR03MB424.namprd03.prod.outlook.com>
In-Reply-To: <775a8b23bb97437992aa191457a1225b@BLUPR03MB424.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ynP5IFjXrS47pZqdc9b20MzA-Ck
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Mar 2014 11:57:58 -0000

On 3/29/2014 9:02 PM, Christian Huitema wrote:

> There is a strong case that the "SMTP submission" information should
>be removed from the trace fields for privacy reasons.

We need to remind ourselves that, as a society, we have already 
exposed "Caller ID" information for the originating contact.  So this 
engineering mindset is set.

But we have made it optional (via a phone).  So I would rephrase your 
suggestion that there is a strong case to allow operators the option 
to remove it or add it by default, however, I would suggest it 
SHOULD|MUST always be recorded, like in a log.

It may be none of my business to know what your IP address is, but it 
maybe also be none of my business to know:

  -- your MAILER?, reader/writer software?
  -- how many machines in your network?
  -- that you have anti-spam, security activity going on
     between HOP x and HOP y?

That spam scoring stuff can leave one with a major complex!

The only time any of this is needed is when there is a tech support 
issue.  In my opinion, communications reliability has improved over 
the years where the overhead items are less necessary.  However, when 
the need does arise, you want the information.

So do we turn it off?  Perhaps not, the software would evolved where 
it would be recorded -- somewhere, but maybe not further distributed 
downlink.

Consider, between all communication devices, hosting systems, we only 
really need the common denominator headers:

    From:
    To:
    Subject:
    Date:

plus body and not much more.  The popularity of texting in general 
illustrates that simplicity works.


-- 
HLS