Re: [Shutup] [ietf-smtp] Proposed Charter for the "SMTP Headers Unhealthy To User Privacy" WG (fwd)

Chris Lewis <ietf@mustelids.ca> Tue, 01 December 2015 23:11 UTC

Return-Path: <ietf@mustelids.ca>
X-Original-To: shutup@ietfa.amsl.com
Delivered-To: shutup@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6B6E1ADBFC; Tue, 1 Dec 2015 15:11:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.343
X-Spam-Level:
X-Spam-Status: No, score=0.343 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, RDNS_NONE=0.793, SPF_PASS=-0.001] 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 rYOQHQG5KMlA; Tue, 1 Dec 2015 15:11:36 -0800 (PST)
Received: from stoat.mustelids.ca (unknown [174.35.246.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 782601B29AD; Tue, 1 Dec 2015 15:11:36 -0800 (PST)
Received: from [192.168.0.6] (badger.mustelids.ca [192.168.0.6]) (authenticated bits=0) by stoat.mustelids.ca (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id tB1NBYuD020966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 1 Dec 2015 18:11:35 -0500
To: shutup@ietf.org
References: <20151130042819.10658.qmail@ary.lan> <1448858775386-ceecd236-8b11ac04-a03b4438@fugue.com> <01PTPUIP3IUK01729W@mauve.mrochek.com> <11d014e5-9a6a-4b78-92a1-8e0a1e0a905d@gulbrandsen.priv.no> <lGTaHvC8ygXWFAuu@highwayman.com> <1449005349724-ffd73ebb-f70e368e-426663a1@fugue.com>
From: Chris Lewis <ietf@mustelids.ca>
X-Enigmail-Draft-Status: N1110
Message-ID: <565E2926.1050900@mustelids.ca>
Date: Tue, 1 Dec 2015 18:11:34 -0500
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
In-Reply-To: <1449005349724-ffd73ebb-f70e368e-426663a1@fugue.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/shutup/oQ_-TP_2JkJmDE7FFqK1l8A-Icc>
Cc: ietf-smtp@ietf.org
Subject: Re: [Shutup] [ietf-smtp] Proposed Charter for the "SMTP Headers Unhealthy To User Privacy" WG (fwd)
X-BeenThere: shutup@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SMTP Headers Unhealthy To User Privacy <shutup.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/shutup>, <mailto:shutup-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/shutup/>
List-Post: <mailto:shutup@ietf.org>
List-Help: <mailto:shutup-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/shutup>, <mailto:shutup-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Dec 2015 23:27:13 -0000

On 12/01/2015 04:29 PM, Ted Lemon wrote:
> Tuesday, Dec 1, 2015 4:10 PM Richard Clayton wrote:
>> If you want to have very limited data in your email header fields then
>> you should look at the systems that you operate yourself and clean up
>> the information at that point. You'll probably get a poorer delivery
>> experience when sending to MAGY and others -- but that's your tradeoff.
>
> Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01DDB1B2F31; Tue, 1 Dec 2015 11:10:08 -0800 (PST)
> 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 BPlsDC_M90ws; Tue, 1 Dec 2015 11:10:06 -0800 (PST)
> Received: from fugue.com (mail-2.fugue.com [IPv6:2a01:7e01::f03c:91ff:fee4:ad68]) by ietfa.amsl.com (Postfix) with ESMTP id CDD061AD481; Tue, 1 Dec 2015 11:10:05 -0800 (PST)
>
> Here are the Received: headers from the previous message I sent to the list.   As you can see, there is no Received header at all for the submit server.   My submit server doesn't add one, because there's no good reason to.   I have had zero issues with mail I send not being delivered to any of the big providers.   When I do have issues, the issues I have tend to be really small servers (typically IETF participants who, like me, run their own mail servers) that have all sorts of exciting steampunk gadgets filtering spam.
>
> The issues that I have tend to be that mail to those users is delayed, not that it never arrives.   It's their choice to set up greylisting, and slowing down the reply rate for discussions like this isn't a bad thing, so I really wouldn't describe this as a "poorer delivery experience."

The inevitable result is your mail server is treated no differently than 
grandma's PC.

When your cat's litter box gets infected with, say, cutwail, spewing 
gazillions of copies of randomized "come do X to my Y!" exhortations, 
you're not giving the receiver (ML or ad-hoc) very much to distinguish 
between that and your pearls of wisdom.

Hence your entire infrastructure gets blocked, you end up annoyed, the 
cat ain't admitting anything, and nothing gets fixed very quickly.

Also remember that at scale, you CANNOT afford to talk to everybody who 
has trouble with email.  Not when the loaded labor rate of just one 
support call dwarfs the income you make with the associated customer.

If you have to get noticed by a human being, you're already cost them 
more than they'll make.

Of course many systems operate this way without much difficulty. 
Because they are either already clean or expend the effort to remain 
clean.  Which is fine until that one day when something goes wrong.