IETF Logo Mail Archive

Re: Google.com hops on the DMARC bandwagon

Theodore Ts'o <tytso@mit.edu> Tue, 29 April 2014 23:11 UTC

Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9C71A09D7 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 16:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.952
X-Spam-Level:
X-Spam-Status: No, score=-1.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_110=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 Sy9d4Fv53jmn for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 16:11:16 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id BE6401A09D4 for <ietf@ietf.org>; Tue, 29 Apr 2014 16:11:16 -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=j1vVTa/wkLtzMJkWJ7td3geBNlw4jmefCKfGO+Wm62A=; b=ekFJz399VMbXHrJ9OcLEf8157zjUyv8RtYQ5UvmWFOrfy4yhPfS2avm9HGxUrM5Qq/iKry5iwforiwsuTyYZqmCOWG3Vz/8OftTBfokiFH7Qf4JuVCzw3ZL0qnf6Ros/3VqMpHUfeJKnbYca9cvEPegMwsQNrW0S0LrE0DGu5KI=;
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WfHBC-0006FI-1J; Tue, 29 Apr 2014 23:11:14 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 7BE54580734; Tue, 29 Apr 2014 19:11:13 -0400 (EDT)
Date: Tue, 29 Apr 2014 19:11:13 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: ned+ietf@mauve.mrochek.com
Subject: Re: Google.com hops on the DMARC bandwagon
Message-ID: <20140429231113.GB28966@thunk.org>
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com> <536011BD.3050704@meetinghouse.net> <536012FC.9020803@att.com> <536015F7.2070100@sonnection.nl> <01P780Q4IQVA000054@mauve.mrochek.com> <53602583.4060003@sonnection.nl> <01P782BTLB96000054@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <01P782BTLB96000054@mauve.mrochek.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
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: http://mailarchive.ietf.org/arch/msg/ietf/4jNx0eAwUz2my6i3Tumq8P79ddI
Cc: Ned Freed <ned.freed@mrochek.com>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 29 Apr 2014 23:11:18 -0000

On Tue, Apr 29, 2014 at 03:36:34PM -0700, ned+ietf@mauve.mrochek.com wrote:
> >> No, because those postings will bounce, and cause those users to get
> >> unsubscribed from the list.
> 
> >But in this case, we're talking about the p=quarantine policy that
> >Google published for google.com... No bouncing (and hence no automatic
> >unsubscription, unless a receiver interprets p=quarantine as 'please
> >reject').
> 
> Fair point. My observation about the appropriate acronym stands, however.

And some of us have already pointed out internally that this might
cause engineers at Google (including folks like Vint) to not be able
to participate on external mailing lists as effectively, since some
percentage of the mailing list recipients might not receive their
message.

And if that means a Google engineer tries to send a patch to an
upstream open source maintainer via a mailing list, and the maintainer
doesn't see the patch or bug report because it got silently dropped by
their MTA (or put in some spam/junk folder), well, that's Google's
loss, and not necessarily the open source project's problem.

Me, I use a non-google.com e-mail address for my external mailing list
discussions, so it's not going to be a problem for me.  :-)

					- Ted

v2.23.0 | Report a Bug | By Email