IETF Logo Mail Archive

Re: [IETF] DMARC methods in mailman

Viktor Dukhovni <ietf-dane@dukhovni.org> Tue, 27 December 2016 20:10 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D865D129B5E for <ietf@ietfa.amsl.com>; Tue, 27 Dec 2016 12:10:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=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 A2aIBsB9z2nn for <ietf@ietfa.amsl.com>; Tue, 27 Dec 2016 12:10:35 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6AA45129B48 for <ietf@ietf.org>; Tue, 27 Dec 2016 12:10:35 -0800 (PST)
Received: from [172.31.30.83] (gzac12-mdf2-1.aoa.twosigma.com [208.77.215.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id 67712282D54 for <ietf@ietf.org>; Tue, 27 Dec 2016 20:10:34 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [IETF] DMARC methods in mailman
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <07a209a7-c529-c81a-bffa-19daa308bff3@dcrocker.net>
Date: Tue, 27 Dec 2016 15:10:33 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <5CC82889-33E0-4485-BBF4-2B14E6E5A8F6@dukhovni.org>
References: <20161226205249.rneaenhh5c2dcpz4@thunk.org> <20161227013401.11378.qmail@ary.lan> <03e401d25fe5$5f32a5f0$1d97f1d0$@huitema.net> <6ec78001-e522-70cc-6592-0228492b8f74@dcrocker.net> <000201d26070$248a9030$6d9fb090$@huitema.net> <49a2a831-a096-233a-3e48-0a87fa98e6ef@dcrocker.net> <0BE40471-1783-4C75-84FB-1CFEBC9CDB12@dukhovni.org> <07a209a7-c529-c81a-bffa-19daa308bff3@dcrocker.net>
To: IETF general list <ietf@ietf.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KGI9Gw4cj-EDhgg02AT6sOs024o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: IETF general list <ietf@ietf.org>
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 27 Dec 2016 20:10:37 -0000

> On Dec 27, 2016, at 2:47 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> 
> 
> End-users are essentially irrelevant to the formalized detection and handling of phishing.

That's good news.  There's no need to worry about what the From: field says at all,
all that matters is automated detection of scams.

Since phishers don't send messages with "Sender" such a change would have no immediate
negative consequences.  Real lists can DKIM sign their outbound messages and get a
decent reputation, while unsigned or forged "Sender" headers can aggressively filtered.

The user can continue to see the bare "From:" header, or "on behalf of" ala Outlook as
deemed most appropriate by the MUA designer and user preference.

-- 
	Viktor.

v2.23.0 | Report a Bug | By Email