IETF Logo Mail Archive

Re: dmarc damage, was gmail users read on... [bozo subtopic]

Nico Williams <nico@cryptonector.com> Thu, 11 September 2014 20:35 UTC

Return-Path: <nico@cryptonector.com>
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 134411A0143 for <ietf@ietfa.amsl.com>; Thu, 11 Sep 2014 13:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.256
X-Spam-Level: *
X-Spam-Status: No, score=1.256 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, IP_NOT_FRIENDLY=0.334, MANGLED_SPAM=2.3, RCVD_IN_DNSWL_NONE=-0.0001] 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 cuAcY3V54JNk for <ietf@ietfa.amsl.com>; Thu, 11 Sep 2014 13:35:40 -0700 (PDT)
Received: from homiemail-a109.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id ABA221A0135 for <ietf@ietf.org>; Thu, 11 Sep 2014 13:35:40 -0700 (PDT)
Received: from homiemail-a109.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTP id 87E4420047B08 for <ietf@ietf.org>; Thu, 11 Sep 2014 13:35:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=YH6AGmF9mTxv60rcrJy1 a6gMIoU=; b=wyHIXt1VTdVjNKfIRvJ96LKZtJAK0S6gcNI0V6iCV3j7NlUdEIEn eSQqM+cbui/WaeYSE8ALfAZBgMc5BlU6kJE/frZ9vgP4MoKr0sPzRxxb4hU8Y/KA TaCWWeLvpLph+6jRhRBFa7lEWNODV8NRpnI0YBBsm42E8uNtw4a9t68=
Received: from mail-we0-f179.google.com (mail-we0-f179.google.com [74.125.82.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a109.g.dreamhost.com (Postfix) with ESMTPSA id 34C4E20047B02 for <ietf@ietf.org>; Thu, 11 Sep 2014 13:35:40 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id u56so6531298wes.24 for <ietf@ietf.org>; Thu, 11 Sep 2014 13:35:37 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.77.243 with SMTP id v19mr4901095wjw.18.1410467737316; Thu, 11 Sep 2014 13:35:37 -0700 (PDT)
Received: by 10.216.52.8 with HTTP; Thu, 11 Sep 2014 13:35:37 -0700 (PDT)
In-Reply-To: <20140911202058.3327.qmail@joyce.lan>
References: <5411DC37.8080101@dougbarton.us> <20140911202058.3327.qmail@joyce.lan>
Date: Thu, 11 Sep 2014 15:35:37 -0500
Message-ID: <CAK3OfOhkwELp5oFF-E7Qm0GBZRZ0MciegjRe4VFxm4_MzRJczA@mail.gmail.com>
Subject: Re: dmarc damage, was gmail users read on... [bozo subtopic]
From: Nico Williams <nico@cryptonector.com>
To: John Levine <johnl@taugh.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AW6Xnxceqs-ISpOpCPy0t2auMdc
Cc: "ietf@ietf.org" <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: Thu, 11 Sep 2014 20:35:42 -0000

On Thu, Sep 11, 2014 at 3:20 PM, John Levine <johnl@taugh.com> wrote:
> http://wiki.asrg.sp.am/wiki/Mitigating_DMARC_damage_to_third_party_mail

Perhaps mailman should offer subscribers some of these (and other?)
options.  Let the subscriber pick their poison.  I realize it's more
work for the list manager, but not that much more work, and easily
automated work anyways.

With my MUAs the lack of WG name in the subject is not fatal.  Though
nonetheless I appreciate that being there.

The footer should just not be added.  It doesn't help anyone, full
stop.  Instead the list should make a simple attempt to detect
"unsubscribe me" messages (and spank the user).

Finally, a subscriber with no delivery option (using the archives
and/or the hopefully-soon-to-arrive IETF IMAP service) would be nice.

Nico
--

v2.23.0 | Report a Bug | By Email