IETF Logo Mail Archive

Re: IETF Mailing Lists and DMARC

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 02 November 2016 19:00 UTC

Return-Path: <mcr+ietf@sandelman.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 F1DD4129B86; Wed, 2 Nov 2016 12:00:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.398
X-Spam-Level:
X-Spam-Status: No, score=-3.398 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.497, 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 LCsZu93w_QbU; Wed, 2 Nov 2016 12:00:46 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7D92129B89; Wed, 2 Nov 2016 12:00:36 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id F3945E1A7; Wed, 2 Nov 2016 15:16:02 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9E99B637A6; Wed, 2 Nov 2016 15:00:35 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Cullen Jennings <fluffy@iii.ca>
Subject: Re: IETF Mailing Lists and DMARC
In-Reply-To: <678C2FBA-A661-4556-A300-5C08562B5F8A@iii.ca>
References: <678C2FBA-A661-4556-A300-5C08562B5F8A@iii.ca>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Wed, 02 Nov 2016 15:00:35 -0400
Message-ID: <29429.1478113235@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eI9LrXnDQERGWK25e8UvxwPfE8Q>
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 19:00:50 -0000

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.

DMARC WG was supposedly designing a solution. I don't know where that is.

My take is that IETF mailing list software should reject email from p=reject
senders, since that's their stated policy.

The original threads include:
    https://www.ietf.org/mail-archive/web/ietf/current/msg99659.html

    > What's the right advice on how the IETF server should be run?

    > Now to a more detailed problem - Jana sends lots of email to the quic
    > list. I don't get any of them. It appears that my email server (run by
    > rackspace) rejects them with an

    > Diagnostic-Code: smtp; 550 5.7.1 Email rejected per DMARC policy for
    > google.com (G15)

    > If Jana sends the email directly to me, it works. This seems to point
    > at the IETF server is doing something that breaks signature in Jana
    > email.

Jana needs to stop sending from google.com.

Their policy is that not to forward, so sad to lose all the google.com
contributors.... we really shouldn't violate their stated policy.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email