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

Ted Lemon <mellon@fugue.com> Wed, 02 December 2015 03:09 UTC

Return-Path: <mellon@fugue.com>
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 289F41B31DB; Tue, 1 Dec 2015 19:09:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 cwAJxk7bTeyX; Tue, 1 Dec 2015 19:09:53 -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 774631B31DA; Tue, 1 Dec 2015 19:09:52 -0800 (PST)
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="----sinikael-?=_1-14490257896920.9116729779634625"
From: Ted Lemon <mellon@fugue.com>
To: shutup@ietf.org
In-Reply-To: <565DF2F0.6050207@mustelids.ca>
References: <20151130042819.10658.qmail@ary.lan> <1448858775386-ceecd236-8b11ac04-a03b4438@fugue.com> <01PTPUIP3IUK01729W@mauve.mrochek.com> <11d014e5-9a6a-4b78-92a1-8e0a1e0a905d@gulbrandsen.priv.no> <01PTRE1WMUMQ01729W@mauve.mrochek.com> <1448995610381-36d96644-173d7bf5-b94de12d@fugue.com> <565DF2F0.6050207@mustelids.ca>
Date: Wed, 02 Dec 2015 03:09:49 +0000
Message-Id: <1449025790038-5861f0d7-9427eca4-6b12d71f@fugue.com>
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/shutup/vRB_ORVqvuhGazZDi5eGjDpceOE>
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: Wed, 02 Dec 2015 03:09:55 -0000

Tuesday, Dec 1, 2015 2:20 PM Chris Lewis wrote:
>> If they don't care enough to make such information available, it's
>> likely that it's because they don't see the issue as being
>> sufficiently important, which is to say they don't think Received:
>> headers make enough difference to be worth arguing about.
> 
> That's not what it means at all.
> 
> For any such information to be even remotely meaningful, it has to be tested on very large real environments.
> 
> Imagine, if you will, our approached our largest customers (which are certainly big enough to matter in this context), and asked them to either:
> 
> - sacrifice filtering effectiveness for a week and tell us the
> result, or
> - re-instrument thousands of receiving MTAs to distinguish and report
> on the differential based on a new indicator I provide
> 
> So that we could satisfy your curiousity, they'd laugh in our faces.

That is literally what I said.   They don't care enough about satisfying my curiosity to do the work.   Perfectly understandable.   If they thought that the IETF producing a document recommending that the Received header field be obfuscated were a serious problem, they would care enough to do the work--it's really not that much work, and chances are they already have a test harness that would allow them to do it.

> I could tell you the differential in our instrumentation. But if you don't accept my previous assertions, you won't accept this one either.

Again, this is literally what I asked for.   I do not trust your assurances that you speak from authority.  IETF people are always trying to argue from authority--if we held that against each other we would never get anything done.

I am very curious to hear your numbers, as long as you explain how you got them.  I don't mean explain your spam algorithm--I mean characterize your sample, and explain why you think it's a good sample, and explain your methodology: what you did to the sample for test A versus what you did for test B.   Interesting things to do for the test sample to differentiate it from the control sample would be removing the last Received header field entirely (last in sequence, meaning first added), modifying the From clause for example as Stephen Farrell suggested, or simply deleting the From clause but keeping the rest of the last Received header field.

BTW, turning off the Received header field testing for a week isn't a valid methodology, since there's no way to control for the rather substantial variation in amounts and types of spam from week to week.

> In an ideal world, when everybody here was under NDA, I could give you some of the obvious, compelling and overwhelming evidence. 

I don't think you could.   You've said enough things that don't actually make sense at this point that I would really need you to show your work, not just give me assurances like the following:

> It's huge. Really.

Sorry.


--
Sent from Whiteout Mail - https://whiteout.io

My PGP key: https://keys.whiteout.io/mellon@fugue.com