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

Al Iverson <aiverson@spamresource.com> Mon, 30 November 2015 16:11 UTC

Return-Path: <aiverson@spamresource.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 2569E1A90E9 for <shutup@ietfa.amsl.com>; Mon, 30 Nov 2015 08:11:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.379
X-Spam-Level:
X-Spam-Status: No, score=-1.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, 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 plsvnzqaaPty for <shutup@ietfa.amsl.com>; Mon, 30 Nov 2015 08:11:18 -0800 (PST)
Received: from mail-ig0-x22d.google.com (mail-ig0-x22d.google.com [IPv6:2607:f8b0:4001:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C961D1A036E for <shutup@ietf.org>; Mon, 30 Nov 2015 08:11:18 -0800 (PST)
Received: by igl9 with SMTP id 9so67558026igl.0 for <shutup@ietf.org>; Mon, 30 Nov 2015 08:11:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=spamresource.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=guMhwqnRL5h50PW1SAPZhzqY7kTQe8y43zzC8kMR/6w=; b=vLzWTpzWpBct+7wBHjLWAXx43zJiqM3eLalGiHXyUTBD0i6rn8mYzN8wCXoHGTEhrG /b0hNACqytURZbw/59P+hU/pjaOoLF9KOHAU4cvpJDw2QL7cm7XiysK6qyGmMNWxHoUt TtZXXCE7hZwwEwaOwi0PYU9B6mwQlBLDCkgCU=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=guMhwqnRL5h50PW1SAPZhzqY7kTQe8y43zzC8kMR/6w=; b=HvWKvUxo9MziVmyTuyxTIAVEm5QWXvbOryo8xUAv0CoZP4ariGb1MsB8S93FcYvJwf O6tPRs12nBzbEttvvYmS1R+DFu9YYyNDEyY3XKJG+GiOxkie3fic5S3aVNqHB6IgGkuD 8xexzlrHLnHNpWEGaqA7nqdL6mV9k+Dnf0C4NdSTQ5GxK/wxOnW3rSiNc/sDFNBpM+j9 fJYprjZJ4f7XF8N/yFk6Uu3ccygsm5icPGzhFzAKeGeleIVmMEV9oY28AkC8XW4Wb4hk Jqn1DgoI3uK1i7xw8nMy7mIxAr0eFrYtLriLQGf5PvVyGWsf9KBZRtAhqpQcZfqeZBzq 4lrg==
X-Gm-Message-State: ALoCoQlXYlAumGkd5hb1cnS1NZvp885AWcrrtW1Ef57HCXAHUfoqwfbGYdiHN48v4jFlezNLJBfV
MIME-Version: 1.0
X-Received: by 10.50.61.98 with SMTP id o2mr21371959igr.79.1448899877921; Mon, 30 Nov 2015 08:11:17 -0800 (PST)
Received: by 10.36.149.10 with HTTP; Mon, 30 Nov 2015 08:11:17 -0800 (PST)
In-Reply-To: <01PTPUIP3IUK01729W@mauve.mrochek.com>
References: <20151130042819.10658.qmail@ary.lan> <1448858775386-ceecd236-8b11ac04-a03b4438@fugue.com> <01PTPUIP3IUK01729W@mauve.mrochek.com>
Date: Mon, 30 Nov 2015 10:11:17 -0600
Message-ID: <CAGGEJxYn=LoHvJRWzhD-fwg4JOFvzLW72WaVZ4sG9sWq4hPBnw@mail.gmail.com>
From: Al Iverson <aiverson@spamresource.com>
To: ietf-smtp@ietf.org
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/shutup/Xftrz8s36sGyc3jjyNVepVt8Un0>
X-Mailman-Approved-At: Mon, 30 Nov 2015 09:34:46 -0800
Cc: shutup@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: Mon, 30 Nov 2015 16:11:20 -0000

On Mon, Nov 30, 2015 at 9:19 AM, Ned Freed <ned.freed@mrochek.com> wrote:

>> Do you seriously think that Google has special-case header parsing to deal with
>> spam from Cornell students' infected computers?   No, they just use machine
>> learning.
>
> I have no idea what Google does, but I can assure you Received: field analysis
> does play a role in spam filtering elsewhere. And even if it didn't, there's
> more to mail operations than spam filtering.

I work for an email service provider dealing with rather large volumes
of mail, yet Received header analysis still plays an important role
for us in troubleshooting operational issues. It would be a tremendous
loss to lose received headers or the IP address information in those
headers. You raise Google as an example; Gmail occasionally seems to
delay message delivery. The internal received hops in a Gmail header
tell you that it's Gmail, not the sender, delaying that delivery of
the message, because the message is likely queued on some internal
server for some period of time, after sender's initial handoff.

Some of us do actually process this data at some level of scale to
identify issues.

Not only do I seriously believe it, but I have also personally
observed AOL to use special-case header parsing to deal with certain
types of mail, to more directly answer your question.

Regards,
Al Iverson

--
Al Iverson - Minneapolis - (312) 275-0130
Simple DNS Tools since 2008: xnnd.com
www.spamresource.com & aliverson.com