IETF Logo Mail Archive

Re: IETF Mailing Lists and DMARC

Cullen Jennings <fluffy@iii.ca> Wed, 02 November 2016 22:00 UTC

Return-Path: <fluffy@iii.ca>
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 185A41294CE for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 15:00:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.621
X-Spam-Level:
X-Spam-Status: No, score=-2.621 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=unavailable 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 WXyWFOrjq6_B for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 15:00:39 -0700 (PDT)
Received: from smtp134.dfw.emailsrvr.com (smtp134.dfw.emailsrvr.com [67.192.241.134]) (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 BCEB71296DF for <ietf@ietf.org>; Wed, 2 Nov 2016 15:00:39 -0700 (PDT)
Received: from smtp21.relay.dfw1a.emailsrvr.com (localhost [127.0.0.1]) by smtp21.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 141AD40154; Wed, 2 Nov 2016 18:00:39 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp21.relay.dfw1a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 3E9D040379; Wed, 2 Nov 2016 18:00:38 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.253] (d75-159-45-76.abhsia.telus.net [75.159.45.76]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.7); Wed, 02 Nov 2016 18:00:39 -0400
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
Subject: Re: IETF Mailing Lists and DMARC
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <29429.1478113235@obiwan.sandelman.ca>
Date: Wed, 02 Nov 2016 16:00:36 -0600
Content-Transfer-Encoding: quoted-printable
Message-Id: <81242B03-803E-4ECD-9131-B301CA932CA5@iii.ca>
References: <678C2FBA-A661-4556-A300-5C08562B5F8A@iii.ca> <29429.1478113235@obiwan.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3226)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E28mOOWGKDhLyaPx07p0vpXpnww>
Cc: dmarc@ietf.org, 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: Wed, 02 Nov 2016 22:00:42 -0000

> On Nov 2, 2016, at 1:00 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> 
> Cullen Jennings <fluffy@iii.ca> wrote:
>> So if someone send a email with a bad signature to an IETF list from a
>> domain that has a reject policy, and the IETF server forwards it to my
>> email email provider, my email provider rejects it. Now the IETF email
>> server counts that as a bounce. Too many bounces in a row and the IETF
>> server unsubscribes me from the list.
> 
>> This does not seem OK that anyone can trivially send some SPAM and get
>> me unsubscribed.
> 
> yeah, that's a real problem isn't it.
> 
> After nearly three years of yelling about this problem, we are not even close
> to consensus that it's a problem, with many people suggesting that IETF mailing
> list software should just munge headers.

My apologies for not checking the archives. I did try but I downloaded a mbox file from one of the IETF mail archive tools that when I importated that into mail.crapp just turned out not to really be a valid mbox file and just turned into one email - anyways, I digress about our broken tools. 

So how do we get this fixed ? Has someone talked to the IESG about this? Right now as a chair, I am making consensus calls that are probably ignoring any emails from people from google.com - and other - because I am not getting their email. That seems like a serious process problem.

v2.23.0 | Report a Bug | By Email