IETF Logo Mail Archive

Re: IETF Mailing Lists and DMARC

"John Levine" <johnl@taugh.com> Wed, 02 November 2016 16:36 UTC

Return-Path: <johnl@taugh.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 6EFF112955A for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 09:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 dqXrorJgB9OB for <ietf@ietfa.amsl.com>; Wed, 2 Nov 2016 09:36:55 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1E6C129460 for <ietf@ietf.org>; Wed, 2 Nov 2016 09:36:54 -0700 (PDT)
Received: (qmail 2842 invoked from network); 2 Nov 2016 16:36:54 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 2 Nov 2016 16:36:54 -0000
Date: Wed, 02 Nov 2016 16:36:41 -0000
Message-ID: <20161102163641.66951.qmail@ary.lan>
From: John Levine <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: IETF Mailing Lists and DMARC
In-Reply-To: <678C2FBA-A661-4556-A300-5C08562B5F8A@iii.ca>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2-oGS1imLJMK2-16-U0VB111WSs>
Cc: fluffy@iii.ca
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 16:36:56 -0000

In article <678C2FBA-A661-4556-A300-5C08562B5F8A@iii.ca> you write:
>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 is a well known DMARC failure mode that has been discussed at
great length on this very list.  Please see the archives.

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

This is a topic that has been discussed at great length on this very
list.  Please see the archives.  ALso look for ARC which is a DMARC
band-aid in development that's supposed to mitigate DMARC damage.

>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. 

This is a well known DMARC failure mode that has been discussed at
great length on this very list.  Please see the archives.

R's,
John

v2.23.0 | Report a Bug | By Email