Re: yet more DMARC stuff, was Re: Mailing list membership.

willi uebelherr <willi.uebelherr@riseup.net> Thu, 02 March 2017 20:09 UTC

Return-Path: <willi.uebelherr@riseup.net>
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 12C561295C1 for <ietf@ietfa.amsl.com>; Thu, 2 Mar 2017 12:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.722
X-Spam-Level:
X-Spam-Status: No, score=-2.722 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=riseup.net
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 y90BgoKEMZXn for <ietf@ietfa.amsl.com>; Thu, 2 Mar 2017 12:09:24 -0800 (PST)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 43DEA1295A9 for <ietf@ietf.org>; Thu, 2 Mar 2017 12:09:24 -0800 (PST)
Received: from piha.riseup.net (unknown [10.0.1.163]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id DA75A1A26FC for <ietf@ietf.org>; Thu, 2 Mar 2017 20:09:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1488485363; bh=h0nMPFBu+SfTv1ds/KmxiTPtZbrFaEva4t0BhhdK0c8=; h=Subject:To:References:From:Date:In-Reply-To:From; b=cdncg81gQK2Sw+t1IwKxGqs/l/zQTf2PBMBy5jNZup8eBtujULfj6o10K2U+dmwrM 3Cb71koeH7HW8+UdYQCa5J6zeGOYQ/QwCSuClLm8WPqnZfRChD2wtSBCscVA2NNYSv YCe4FIbduWSefX+QA+gvGIjx8liPMdQNlNYjOZX0=
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: willi.uebelherr) with ESMTPSA id 30B7E1C00AD
Subject: Re: yet more DMARC stuff, was Re: Mailing list membership.
To: ietf@ietf.org
References: <20170301210033.1672.qmail@ary.lan>
From: willi uebelherr <willi.uebelherr@riseup.net>
Message-ID: <1628e89a-349c-6fd9-f267-31a08d652811@riseup.net>
Date: Thu, 02 Mar 2017 17:08:55 -0300
MIME-Version: 1.0
In-Reply-To: <20170301210033.1672.qmail@ary.lan>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C-KEB1ypVuBC1nulskRnbWm5vks>
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, 02 Mar 2017 20:09:25 -0000

Dear John,

"PS: I presume you all know that we've been working on workarounds."

Please John, explain your results or understanding in the IETF list, 
that all members in the list know, for what you work and what problems 
exist for you.

many thanks and greetings, willi


On 01/03/2017 18:00, John Levine wrote:
> In article <70ebe3f4-bae5-7b65-a8ba-b90fdc38dbb8@comcast.net> you write:
>>> This is a good idea.  Taking it a step further, perhaps a warning could be included when
>> subscribing to an IETF list from an email provider who is known to use DMARC.
>
> You can tell who publishes DMARC policies, but without experimentation
> you can't tell who follows them on inbound mail.
>
> Of the large public mail providers, only AOL and Yahoo currently
> publish DMARC policies, but Gmail certainly looks at DMARC, albeit as
> part of the special sauce so a Gmail user might get mail with DMARC
> problems or might not.  I'm reasonably sure that Hotmail and Comcast
> also look at DMARC on incoming mail.  DMARC is surprisingly useful for
> blocking phishes, which is a big issue for consumer mail providers, so
> the providers that use it are not going to stop.
>
> R's,
> John
>
> PS: I presume you all know that we've been working on workarounds.
>
>