IETF Logo Mail Archive

Re: [dmarc-ietf] Issue submission - Mailing list security and potential solutions using DMARC

Alessandro Vesely <vesely@tana.it> Tue, 29 September 2020 17:09 UTC

Return-Path: <vesely@tana.it>
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 B2F773A0F18 for <dmarc@ietfa.amsl.com>; Tue, 29 Sep 2020 10:09:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.311
X-Spam-Level:
X-Spam-Status: No, score=-2.311 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.213, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 TTQshnXgLbDO for <dmarc@ietfa.amsl.com>; Tue, 29 Sep 2020 10:09:16 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 25C053A0F14 for <dmarc@ietf.org>; Tue, 29 Sep 2020 10:09:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1601399354; bh=Os9j4F0zJsTDAGYSssbRNgHIwzkLjX68XBO/ndxBN/4=; l=1172; h=To:Cc:References:From:Date:In-Reply-To; b=CMu918vOO7nXMcy8itolU5A0ujl4K7jHW1Zw38+U6Xr24iBP6UskchJE/emf+WCVm zD9ILCYxpN/nLUgrLt6t10HrZ0/uGJjMoxqY8/XAXCJBk7fme5wyH6+Iioqf6kGrQX J7uYfSxWMkVqcZhiR9G1O0KS7M3gli0AWuuiB+CfJRsR2JknCTJQwZTk2ew/f
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC050.000000005F736A3A.000051D3; Tue, 29 Sep 2020 19:09:14 +0200
To: "Murray S. Kucherawy" <superuser@gmail.com>, Doug Foster <fosterd@bayviewphysicians.com>
Cc: "dmarc@ietf.org" <dmarc@ietf.org>
References: <81937b856c4a4a40b313ae6b9b7af97b@bayviewphysicians.com> <CAL0qLwbBnA62qV=9yTRWp5VSPAke75c=XesHqYgGfX_WBDog8Q@mail.gmail.com> <CAL0qLwZEDNT+LZDMrzecSuTD794jn0CoXRA5FG=rk6QJXO5Hyg@mail.gmail.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <64089a46-64ba-1b87-92a0-88d23ee52e02@tana.it>
Date: Tue, 29 Sep 2020 19:09:14 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <CAL0qLwZEDNT+LZDMrzecSuTD794jn0CoXRA5FG=rk6QJXO5Hyg@mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/QXbe4bVFSskdVdYY25VfkvI3Cyc>
Subject: Re: [dmarc-ietf] Issue submission - Mailing list security and potential solutions using DMARC
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: Tue, 29 Sep 2020 17:09:18 -0000

On Sun 13/Sep/2020 03:43:07 +0200 Murray S. Kucherawy wrote:
> While I'm thinking of it:
> 
> On Sat, Sep 12, 2020 at 6:11 PM Murray S. Kucherawy wrote:
>> On Thu, Sep 10, 2020 at 3:51 PM Douglas E. Foster wrote:
>>
>>> The Alternative
>>>
>>> All of these problems can be avoided if the subscriber is given an alias
>>> at enrollment, and the alias is used for all messages relayed on the
>>> subscriber's behalf.    For this list, my alias could be
>>> DougF.dmarc@ietf.org.   Messages sent to an alias address must be
>>> submitted through the list operator, and the list manager should have logic
>>> to reject messages from a non-subscriber that are targeting a subscriber
>>> alias.
>>>
>>
> How does this compare to what's done here already (if enabled)?
> 
> https://wiki.list.org/DEV/DMARC


Mailman has an anonymous_list[*] configuration variable that, if enabled, removes or replaces the From:, Sender:, and Reply-To: fields of any message posted to the list.  It can be consider an (overkill) alternative to From: munging.


Best
Ale
-- 

[*] https://mailman.readthedocs.io/en/latest/src/mailman/handlers/docs/cleanse.html#anonymous-lists

v2.46.0 | Report a Bug | By Email | System Status