Re: [dmarc-ietf] non-mailing list use case for differing header domains

Hector Santos <hsantos@isdg.net> Thu, 30 July 2020 12:51 UTC

Return-Path: <hsantos@isdg.net>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 364B93A10F3 for <dmarc@ietfa.amsl.com>; Thu, 30 Jul 2020 05:51:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=fVmjoRMr; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=SqyN8NN8
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 3ySIY-oAkV46 for <dmarc@ietfa.amsl.com>; Thu, 30 Jul 2020 05:51:23 -0700 (PDT)
Received: from mail.winserver.com (groups.winserver.com [76.245.57.69]) (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 9B1F63A10DB for <dmarc@ietf.org>; Thu, 30 Jul 2020 05:51:23 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1220; t=1596113479; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=LD0aH0m2JE1sN/X2tLkTBpTfn/c=; b=fVmjoRMr2Zb1vNz2bLUVlmlb+Pl8OosZj36BYrkr/KbOwDM+teV9+SRxx972Wa RFr5/JoG7madZ6nrFL4BO7Wa3fITa8agiKbZacGp1hZ4Y0l2CvTrJkeii2+LPwdn /oWEQJ7zGLLQZZ6NrCTKm7egzVlP+sBAM9sL7ePM+ycTQ=
Received: by mail.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Thu, 30 Jul 2020 08:51:19 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com; dmarc=pass policy=reject author.d=isdg.net signer.d=beta.winserver.com (atps signer);
Received: from beta.winserver.com ([76.245.57.74]) by mail.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 2545770548.1.3888; Thu, 30 Jul 2020 08:51:19 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1220; t=1596113362; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=N6Wwy+N mhTQtnrtHNChSJiVLqMnY7D8ptWdinAO2qrc=; b=SqyN8NN8hM4YsESOIYmFtUP PqZv8HaJtYFW4elg3+cZWNKccdjyUYu2LJV7NBKatgbgkR1iJyPjZdgbKQtHAtQn OykqXRsh30N/GzdqW8kClPrwAi/XVdOVm6aVDuyZ4B3O9us/sX+mF8wOG8Xl2YI5 oOMHWc1xGprcyaSdkXgs=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.10) for dmarc@ietf.org; Thu, 30 Jul 2020 08:49:22 -0400
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.10) with ESMTP id 2256537343.1.60928; Thu, 30 Jul 2020 08:49:21 -0400
Message-ID: <5F22C246.1060309@isdg.net>
Date: Thu, 30 Jul 2020 08:51:18 -0400
From: Hector Santos <hsantos@isdg.net>
Reply-To: hsantos@isdg.net
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: dmarc@ietf.org
References: <BY5PR13MB29998094418C8A6C25902569D7730@BY5PR13MB2999.namprd13.prod.outlook.com> <c0361cb2-b25b-5d75-cb1f-f9c87e3ecccc@tana.it> <AE9A3A9F-27FC-4935-B8E6-AB0CE1A6D5E2@wordtothewise.com> <5F204CB3.7080404@isdg.net> <000001d66503$4d447e50$e7cd7af0$@bayviewphysicians.com> <5F21B338.8000700@isdg.net> <ecf7a4bd-5524-82d5-afec-1e0e256cce10@wizmail.org> <fe66f197-9b13-2122-cc30-a52d66894cc1@wemonitoremail.com>
In-Reply-To: <fe66f197-9b13-2122-cc30-a52d66894cc1@wemonitoremail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/fmAP492AWtRCezDppkDKTiKtL2k>
Subject: Re: [dmarc-ietf] non-mailing list use case for differing header domains
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jul 2020 12:51:26 -0000

On 7/30/2020 7:57 AM, Ken O'Driscoll wrote:
> On 30/07/2020 11:39, Jeremy Harris wrote:
>> That works at a domain-controlled level.  But people sign up for,
>> and write to, mailinglists on an individual level.  Mismatch.
>
> To be fair, this thread is specifically about a non-MLM use case at an
> organisational level. But, I believe that any improvements to how DMARC
> might handle use cases like mailing lists will likely have to be at the
> domain-controlled level for there to be any chance of widespread adoption.
>
> From experience, the type of organisations that are deploying DMARC (in
> p=reject) are not interested in allowing individual senders to delegate
> which third-parties can send on their behalf. Banks etc. don't care
> about mailing lists, most have HR policies that prevent employees from
> interacting on external discussion groups so it's not on the radar.
> However,  the use case presented in this thread - executive assistants
> sending on behalf of multiple DMARC protected brand domains - is not
> that uncommon and I think a policy solution to that would be warmly
> welcomed.

+1

-- 
Hector Santos,
https://secure.santronics.com
https://twitter.com/hectorsantos