Re: DMARC methods in mailman --- [LEDE-DEV] DMARC related mass bounces / disabled subscriptions (fwd) Jo-Philipp Wich: [LEDE-DEV] DMARC related mass bounces / disabled subscriptions

Rich Kulawiec <rsk@gsp.org> Sat, 17 December 2016 12:02 UTC

Return-Path: <rsk@gsp.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 4F26B12944F for <ietf@ietfa.amsl.com>; Sat, 17 Dec 2016 04:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level:
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] 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 LSCM56nAFkQk for <ietf@ietfa.amsl.com>; Sat, 17 Dec 2016 04:02:50 -0800 (PST)
Received: from taos.firemountain.net (taos.firemountain.net [207.114.3.54]) (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 5B282129479 for <ietf@ietf.org>; Sat, 17 Dec 2016 04:02:50 -0800 (PST)
Received: from gsp.org (localhost [127.0.0.1]) by taos.firemountain.net (8.15.1/8.14.9) with SMTP id uBHC2kfj007745 for <ietf@ietf.org>; Sat, 17 Dec 2016 07:02:48 -0500 (EST)
Date: Sat, 17 Dec 2016 07:02:46 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: ietf@ietf.org
Subject: Re: DMARC methods in mailman --- [LEDE-DEV] DMARC related mass bounces / disabled subscriptions (fwd) Jo-Philipp Wich: [LEDE-DEV] DMARC related mass bounces / disabled subscriptions
Message-ID: <20161217120246.GA25459@gsp.org>
References: <25431.1481725548@obiwan.sandelman.ca> <5EF6F271-1CF7-4981-8E83-C7A7B49DB8F2@gmail.com> <CDE8A76C-ECD7-4370-9823-3C78144A8850@nohats.ca> <24005.1481827604@obiwan.sandelman.ca> <alpine.LRH.2.20.1612151513060.15183@bofh.nohats.ca> <20161216202704.glz5vgu773gqqgvm@thunk.org> <20161216203905.GD13486@mournblade.imrryr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20161216203905.GD13486@mournblade.imrryr.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/64udc5dwuh8kx4LfkVEYBHOYgfk>
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: Sat, 17 Dec 2016 12:02:52 -0000

On Fri, Dec 16, 2016 at 08:39:06PM +0000, Viktor Dukhovni wrote:
> When it is more difficult to forge an email from a Yahoo user, it
> is more convenient for the phisher to fake an address from some
> other domain, and then Yahoo deals with fewer complaints.

I don't think it's difficult at all to forge an email from a Yahoo user.
And it'll even dutifully be marked as valid courtesy of Yahoo itself:

	Yahoo Says 1 Billion User Accounts Were Hacked                          
	http://www.nytimes.com/2016/12/14/technology/yahoo-hack.html    

Please note that this is in addition to the earlier announcement
of 500M hacked accounts.

But hey, at least they got to do this:

	Yahoo breaks every mailing list in the world including the IETF's
	http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html

Yeah.  That was worth it.  Definitely.

---rsk