IETF Logo Mail Archive

Re: Do we actually want to do anything about DMARC?

Theodore Ts'o <tytso@mit.edu> Mon, 15 August 2016 13:01 UTC

Return-Path: <tytso@thunk.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 BBC8712DDA9 for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2016 06:01:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level:
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=thunk.org
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 5QBWmK9dkEjt for <ietf@ietfa.amsl.com>; Mon, 15 Aug 2016 06:01:08 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) (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 445A112DDA8 for <ietf@ietf.org>; Mon, 15 Aug 2016 06:01:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org; s=ef5046eb; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=ZW+6lamw7dQTC1BsuaeBNAhoMDej4DVnuy3bZWXdlXQ=; b=PHt6Y72Zrj93NgZdgC6oazRH0zf348VblYs7IH78+fMXZPO2N85xnFf5uLTyQhrh51hjk+zFMx8BvahNfb1f8uBFjhDriDDEvshAZUdAM++RTlQ0DL6vmAoUVVjD0joJ6Ge5yIKdUSCxQE/lBMmUdfvDDsF65VaZoGWr20pYAg4=;
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.84_2) (envelope-from <tytso@thunk.org>) id 1bZHVq-00013M-RF; Mon, 15 Aug 2016 13:01:06 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 1CB0A82F802; Mon, 15 Aug 2016 09:01:06 -0400 (EDT)
Date: Mon, 15 Aug 2016 09:01:06 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: Do we actually want to do anything about DMARC?
Message-ID: <20160815130106.GS10626@thunk.org>
References: <20160815012208.8845.qmail@ary.lan> <eb972040-caf2-7acf-85b8-a40fa8cdcd60@tana.it>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <eb972040-caf2-7acf-85b8-a40fa8cdcd60@tana.it>
User-Agent: Mutt/1.6.0 (2016-04-01)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/01kkvMBb6U-LuaW4fDdhzQG8bHU>
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <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: Mon, 15 Aug 2016 13:01:10 -0000

On Mon, Aug 15, 2016 at 11:31:16AM +0200, Alessandro Vesely wrote:
> On Mon 15/Aug/2016 03:22:08 +0200 John Levine wrote:
> > 
> > My form is marissa@yahoo.com.dmarc.fail, but if wildcard MX records
> > are scary, it could be marissa-yahoo.com@fwd.ietf.org.  Having done
> > this before, I know it's not terribly hard, and I'd be happy to help
> > make it work.
> 
> Marissa@yahoo.com.MANUALLY.REMOVE.THE.TRAILING.PARTS would involve even
> less work and worries.  IMHO, it is not so much its forcing recipients
> to refurbish their wit in order to discern phishes, as its rendering the
> From: field meaningless, which troubles this workaround's viability.

>From what John has said, he's actually made the from field work:

% dig -t mx dmarc.fail +nocomments

; <<>> DiG 9.10.3-P4-Debian <<>> -t mx dmarc.fail +nocomments
;; global options: +cmd
;dmarc.fail.			IN	MX
dmarc.fail.				3599	IN	MX	20 mail1.iecc.com.
;; Query time: 188 msec
;; SERVER: 192.168.86.1#53(192.168.86.1)
;; WHEN: Mon Aug 15 08:58:07 EDT 2016
;; MSG SIZE  rcvd: 69


I do wonder how he deals with the spam reputation problem of his
forwarding server if too many spammers try to send mail to
marissa@yahoo.com.dmarc.fail --- I assume he must do a lot of
anti-spam filtering and is refusing to forward stuff which is spam?

Hopefully he's using a more intelligent spam filter than Gmail is,
though.  :-)

	https://plus.google.com/+DavidMiller/posts/ifyNptbyxs1

Maybe spammers are starting to use patches as filler?  Who knows.  :-(

Next thing you know, maybe they'll start using excerpts from I-D's,
and then where will the IETF be?

						- Ted

v2.23.0 | Report a Bug | By Email