Re: [dmarc-ietf] IETF Mailing Lists and DMARC
"Andrew G. Malis" <agmalis@gmail.com> Thu, 03 November 2016 18:25 UTC
Return-Path: <agmalis@gmail.com>
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 97295129452; Thu, 3 Nov 2016 11:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VMytUtdZdlrd; Thu, 3 Nov 2016 11:25:04 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (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 51E34129697; Thu, 3 Nov 2016 11:25:04 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id v84so102383384oie.3; Thu, 03 Nov 2016 11:25:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VqyqDFfuntUPZFQiTaU/OK7zXu6qcxRljOzTXxlTRU4=; b=r41d6CQcs2L0FZnBx32G3r9p4Gn/4CtChznHkLfugGylBAw3Pxm8LwrKUfsEIXCZnK uOhYZgTCBZm7SZeh6QRfn6Fc0xuXWhEWt11QZgtd6Lw+x3a2bYGCUPFPtVrcfZViq75b LoYirUuNT3mC/GdD3qKKwvb1U000fSzX6PyF0Efi9wGr11/ycs39OkSGIycYGl4Gqh4G xpko/R83c8UnegU8/8mgzaD0Z8Hi0kuoFw8hqK4IUTWvShGtNFpPNQuvCTB3cz8cC1Bm csauQKoz1yWZijCXTQiEoMcdW/UPRknwPUXKzHxjibdExgRp/GrpSj6++0fnAxEl6cMb bnCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=VqyqDFfuntUPZFQiTaU/OK7zXu6qcxRljOzTXxlTRU4=; b=Ah7bMj40Bxv72q3mQWrsIrqx/5/hng7/80prz6qYazfaoqhY7GL/i8aMfgsTevhtUj qnj6Md5Vd2GKWEcDCipnP582vjpli6T+aAT41IzwzG/wAEf4R2ozA47N5zjALuooRCua Vr9nl4vqGai7HBl2q5EflvgURErFrSFbXvM5pl9HyRsEnnCDgA03tFdW7gqUdE4jXH+L PIDQaJ+uG7HyZIq2Gx8GqLdBJpdqojXwm9+eroXVAZ7ASeujAO391yeDg4ST8xGw1ah4 kWbd8xeXTqP8lIzdY2NYCukoR5+IK0JH4nqCkpP/5INzgze3xQ7xn7041yU3Lgo+FxEr 8jww==
X-Gm-Message-State: ABUngvcOOjyKqhm1TjxQ+vd1yaKJhNVkKVahMiEvqdy0rA9Cz+VypaBj1x/FFWl9c1AHITuAui8VFBQKu5l7cw==
X-Received: by 10.157.20.225 with SMTP id r30mr7470693otr.148.1478197503748; Thu, 03 Nov 2016 11:25:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.150.42 with HTTP; Thu, 3 Nov 2016 11:24:43 -0700 (PDT)
In-Reply-To: <FF25052A-842C-45A4-BEDB-DAD3C9233B36@wordtothewise.com>
References: <678C2FBA-A661-4556-A300-5C08562B5F8A@iii.ca> <29429.1478113235@obiwan.sandelman.ca> <CABa8R6vHdt75NFKW3s6xOzLcq=jmVAHDPX0tjLRdGpYSTP2cYA@mail.gmail.com> <20161102232357.b55vx7est7vjrdfo@thunk.org> <CO2PR00MB01018CDB45F0CE17671AD67596A30@CO2PR00MB0101.namprd00.prod.outlook.com> <20161103134909.lnndzi6feaqfskyj@thunk.org> <CO2PR00MB0101960D3E311D2E1D4E1C4296A30@CO2PR00MB0101.namprd00.prod.outlook.com> <CAA=duU2C8uyj7e7bET8+73QrsXLtO9-+eXdRBr8FiGsLCfU9dA@mail.gmail.com> <FF25052A-842C-45A4-BEDB-DAD3C9233B36@wordtothewise.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Thu, 03 Nov 2016 14:24:43 -0400
Message-ID: <CAA=duU1pbQ8ZWX_eLATJU+i7Nhz35JpFkEgvaXtzjnhu6Dq-9Q@mail.gmail.com>
Subject: Re: [dmarc-ietf] IETF Mailing Lists and DMARC
To: Steve Atkins <steve@wordtothewise.com>
Content-Type: multipart/alternative; boundary="001a113cdada1e6fb3054069adec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n8x-R__490jCNP8dYskjpF7lnEM>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>, IETF <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: Thu, 03 Nov 2016 18:25:06 -0000
Hi Steve! The site goes on to say: "If you don't take any action here, you're leaving a subset of your potential subscribers out in the cold. Making them second class citizens, unable to participate in the mailing lists you're hosting. Be kind, and don't beat up Yahoo users because of a domain policy that Yahoo choose to implement (and that Yahoo user is stuck dealing with).” I certainly agree with that sentiment. And it’s not the DMARC WG that's responsible for IETF email list support, it’s the admin staff at AMS that are the ones “caught in the middle”. Cheers, Andy On Thu, Nov 3, 2016 at 2:06 PM, Steve Atkins <steve@wordtothewise.com> wrote: > > > On Nov 3, 2016, at 10:56 AM, Andrew G. Malis <agmalis@gmail.com> wrote: > > > > > > On Thu, Nov 3, 2016 at 1:30 PM, Terry Zink <tzink@exchange.microsoft.com> > wrote: > > The average Internet user doesn't understand DMARC. The average person > on an Internet mailing list doesn't understand DMARC either, and even the > average tech person on a mailing list doesn't understand DMARC. All they > know is that their mailing list doesn't work, or that they have been > unsubscribed. Only people who work on DMARC understand DMARC. > > > > Asking the average person to switch their email address just so that > they can participate in mailing lists isn't a solution. > > > > Three thumbs up on the last sentiment above - could you imagine saying > to someone that you need to switch phone providers in order to reach > certain recipients? And while my current use of gmail allows me to more or > less get around DMARC list problems (although I need to check my incoming > spam folder at least daily since mailing list DMARC failures send > legitimate emails there), there’s no guarantee how long that will continue. > > > > And regarding Terry's previous paragraph, while I’m by no means an > expert on DMARC (or mailman for that matter), a bit of googling tells me > that there are more recent versions of mailman than what the IETF is > currently using that support DMARC mitigation. See, for example, > http://www.spamresource.com/2016/09/dmarc-support-in-mailman.html . > > "Mitigating the effects of the DMARC reject policy are difficult. All > known mitigation techniques break some user expectations and/or degrade the > user experience. Still, it's incumbent on the Mailman developers to try to > reduce the pain our users feel, and to provide some options for site and > list administrators who find themselves caught in the middle." > > dmarc@ietf.org, of all lists, is not one whose administrators are "caught > in the middle". > > Cheers, > Steve >
- Re: IETF Mailing Lists and DMARC Dave Crocker
- IETF Mailing Lists and DMARC Cullen Jennings
- Re: IETF Mailing Lists and DMARC John Levine
- Re: IETF Mailing Lists and DMARC Ted Lemon
- Re: IETF Mailing Lists and DMARC John Levine
- RE: IETF Mailing Lists and DMARC MH Michael Hammer (5304)
- RE: IETF Mailing Lists and DMARC John R Levine
- Re: IETF Mailing Lists and DMARC Ted Lemon
- Re: IETF Mailing Lists and DMARC John Levine
- Re: IETF Mailing Lists and DMARC Dave Crocker
- Re: IETF Mailing Lists and DMARC Ted Lemon
- Re: IETF Mailing Lists and DMARC Paul Hoffman
- Re: IETF Mailing Lists and DMARC John C Klensin
- Re: IETF Mailing Lists and DMARC Ted Lemon
- Re: IETF Mailing Lists and DMARC Michael Richardson
- Re: IETF Mailing Lists and DMARC Yoav Nir
- Re: IETF Mailing Lists and DMARC Ted Lemon
- Re: IETF Mailing Lists and DMARC Yoav Nir
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Hector Santos
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Dave Crocker
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Brandon Long
- Re: IETF Mailing Lists and DMARC Cullen Jennings
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Cullen Jennings
- Re: IETF Mailing Lists and DMARC S Moonesamy
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Brian E Carpenter
- Re: IETF Mailing Lists and DMARC John Levine
- Re: IETF Mailing Lists and DMARC John Levine
- Identification of an email author (was - Re: [dma… Dave Crocker
- Re: IETF Mailing Lists and DMARC Ted Lemon
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Theodore Ts'o
- RE: [dmarc-ietf] IETF Mailing Lists and DMARC Terry Zink
- Re: IETF Mailing Lists and DMARC John Levine
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Theodore Ts'o
- Next step on IETF Mailing Lists and DMARC Alexey Melnikov
- Re: IETF Mailing Lists and DMARC Bob Hinden
- RE: IETF Mailing Lists and DMARC MH Michael Hammer (5304)
- Re: IETF Mailing Lists and DMARC Ted Lemon
- RE: [dmarc-ietf] IETF Mailing Lists and DMARC Terry Zink
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Andrew G. Malis
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Steve Atkins
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Andrew G. Malis
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Theodore Ts'o
- Options for temporary operational solution to DMA… Ted Lemon
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Brandon Long
- Re: [dmarc-ietf] Identification of an email autho… Brandon Long
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Franck Martin
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Hector Santos
- Re: Options for temporary operational solution to… Andrew G. Malis
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC John C Klensin
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Ted Lemon
- Re: IETF Mailing Lists and DMARC Michael Richardson
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Michael Richardson
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Michael Richardson
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC John C Klensin
- Re: Options for temporary operational solution to… John Leslie
- RE: [dmarc-ietf] Identification of an email autho… Terry Zink
- Re: Options for temporary operational solution to… Toerless Eckert
- Re: [dmarc-ietf] Identification of an email autho… Ted Lemon
- Re: Options for temporary operational solution to… John Levine
- RE: [dmarc-ietf] Identification of an email autho… Terry Zink
- Re: Options for temporary operational solution to… Ted Lemon
- RE: [dmarc-ietf] IETF Mailing Lists and DMARC Christian Huitema
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Brian E Carpenter
- Re: Options for temporary operational solution to… Michael Richardson
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Michael Richardson
- Re: Options for temporary operational solution to… Dave Crocker
- Re: [dmarc-ietf] Identification of an email autho… Franck Martin
- Re: [dmarc-ietf] Identification of an email autho… Khaled Omar
- Re: [dmarc-ietf] Identification of an email autho… S Moonesamy
- Re: [dmarc-ietf] IETF Mailing Lists and DMARC Brandon Long
- Re: [dmarc-ietf] Identification of an email autho… Dave Crocker
- Re: [dmarc-ietf] Identification of an email autho… Dave Crocker
- Re: [dmarc-ietf] Identification of an email autho… ned+ietf
- Re: [dmarc-ietf] Identification of an email autho… Franck Martin
- Re: [dmarc-ietf] Identification of an email autho… Dave Crocker
- Re: [dmarc-ietf] Identification of an email autho… John C Klensin
- Re: [dmarc-ietf] Identification of an email autho… Brandon Long