Re: DMARC and ietf.org

S Moonesamy <sm+ietf@elandsys.com> Sun, 14 August 2016 17:27 UTC

Return-Path: <sm@elandsys.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 4237612D761 for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2016 10:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.037
X-Spam-Level:
X-Spam-Status: No, score=-3.037 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.247, T_DKIM_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=opendkim.org header.b=x+Xg9vWG; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=elandsys.com header.b=RhRa3uob
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 bVzpnHXo91Sj for <ietf@ietfa.amsl.com>; Sun, 14 Aug 2016 10:27:20 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id D48A712D1D7 for <ietf@ietf.org>; Sun, 14 Aug 2016 10:27:20 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.147.165]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id u7EHQt3o002944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 14 Aug 2016 10:27:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1471195628; x=1471282028; bh=ezqEDUcw9HH5Kli8ybHgMNy4HJwMpQzhSxjoWUfwVX8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=x+Xg9vWGCAb+1jgym5VlmrFbSi8YcEZuQJbicu5yd+2pNHAsoWuKDc5VpqENwjugn Uy/SoUDvCdb439dPRb76E9kB18V0d1xZgxHrAwPH+l53Lh4jXXYsgB164fjN59fGSr n2i3jGifK/GIpIZjpX/+foQYU7bNalJIlS8pkHRs=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1471195628; x=1471282028; i=@elandsys.com; bh=ezqEDUcw9HH5Kli8ybHgMNy4HJwMpQzhSxjoWUfwVX8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RhRa3uob3kwYh81q34aJWHmz2xdj6Cci0dHQTeUmjkshZBXl56XKWXBBy29ZCXA8m RdKGIzRFBrUH6/BkymJOK7W5g7Dwu8ZFlklbLNCC3fhhbUe25TqJkypWb/wKU9cT2u LoDYymjpGoyKWYCIhBjVchNWha+zywdDhZPsrHOk=
Message-Id: <6.2.5.6.2.20160814093145.0aec98d8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 14 Aug 2016 10:23:54 -0700
To: =JeffH <Jeff.Hodges@KingsMountain.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: DMARC and ietf.org
In-Reply-To: <305f4a93-7d4c-681c-18a0-25c7939d2b02@KingsMountain.com>
References: <305f4a93-7d4c-681c-18a0-25c7939d2b02@KingsMountain.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7keyBs_EQpte9kqjaBp0_5pWyVI>
Cc: "Carlos Pignataro \(cpignata\)" <cpignata@cisco.com>, Christian Huitema <huitema@huitema.net>
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: Sun, 14 Aug 2016 17:27:22 -0000

Hi Jeff,

For information about the facilitators experiment, please see
http://www.ietf.org/mail-archive/web/ietf/current/msg97290.html

At 10:20 12-08-2016, =JeffH wrote:
>Regardless of details, applying some sort of remediation to 
>ietf.org/mailman is becoming more pressing IMV -- I am noticing that 
>email, sent from pingidentity.com (p=quarantine; pct=100;) via IETF 
>mailing lists, is not being delivered to my paypal.com inbox at all. 
>Also, the same is occurring for some email from microsoft.com 
>(p=quarantine; pct=30;). The same is true for email I might send via 
>my @paypal.com persona.
>
>The W3C mailing list manager (MLM) is apparently configured to do 
>rfc5322.from field re-writing which seems to ameliorate the 
>DMARC-MLM issues (in my experience, at least), and it would be 
>helpful if the IETF would take similar measures.

There was a message [1] from Russ Housley on this thread in which he 
mentioned that: "Mailman has an option we can enable to force 
DMARC-spoofing sender rewriting of all outgoing Mailman email.  If we 
enable that option, the From: field rewriting and could be disruptive 
in unknown ways".  It was also mentioned that "SPF/DMARC are taken 
into account" for the scoring of incoming email to ietf.org.

Regards,
S. Moonesamy

1. https://www.ietf.org/mail-archive/web/ietf/current/msg98965.html