Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

Alessandro Vesely <vesely@tana.it> Thu, 31 December 2020 12:13 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 048863A0AD6 for <dmarc@ietfa.amsl.com>; Thu, 31 Dec 2020 04:13:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 kvjZvjUQPoFY for <dmarc@ietfa.amsl.com>; Thu, 31 Dec 2020 04:13:28 -0800 (PST)
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 BFF3F3A0AD4 for <dmarc@ietf.org>; Thu, 31 Dec 2020 04:13:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1609416804; bh=VAtw5wlSmE6dvdvW9VsFUTYnt3KruRSf9KIHInZzI/4=; l=1004; h=To:References:From:Date:In-Reply-To; b=Dh2VGaErPcoz0GssfTvpDxh8Z1+phxEkiHfTVX7Ar4zVikQIYch4cjYNqdGO4LnVf BAWRed1ST+k4PSMbLp7kuh87vQ1Hl7vr6Oj/MOOL7mCZ33EiMHH3jdrOSZMNrZyXej N+gFPT7J4n2FffhpWb3loEqfxE1Zscb3ua/ACO9cD4Mj/Xr8R8ixPKnWAHJWE
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
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 00000000005DC07E.000000005FEDC064.0000024B; Thu, 31 Dec 2020 13:13:24 +0100
To: dmarc@ietf.org
References: <20201204195833.6B48A28F892A@ary.qy> <c85ed36b-754-27a1-aaa1-ef42cccf24ae@taugh.com>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <74b5c149-8b8c-8c98-d9ff-5121a544349c@tana.it>
Date: Thu, 31 Dec 2020 13:13:24 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <c85ed36b-754-27a1-aaa1-ef42cccf24ae@taugh.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/N7S13bJg__yxXCbJyEZUf4TbNUM>
Subject: Re: [dmarc-ietf] Ticket #28 - Failure report mail loops
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, 31 Dec 2020 12:13:31 -0000

On Wed 30/Dec/2020 22:17:47 +0100 John R Levine wrote:
> On Fri, 4 Dec 2020, John Levine wrote:
>> In article <0408ae98-e1c1-71fe-fdd4-8bc7a7c151d3@tana.it> you write:
>>> We would like to close this ticket by Dec 18, two weeks from now, so please get
>>> on it.
>>>
>>> The ticket originated from John's comment, in May 2019:
>>>
>>>     Apropos recent discussions, we could recommend that failure reports be
>>>     rate limited per recipient both to break loops and to deter indirect
>>>     mail bombing.
>>
>> I have never gotten enough failure reports that handling them was even
>> slightly inconvenient, and my addresses are on every spam list in the world.
>>
>> Has anyone else?  If don't have evidence that this is a real problem, I'd 
>> just close the ticket.
> 
> The answer was apparently no, so I propose we close this with no change.


Closed already on 18th, see:
https://mailarchive.ietf.org/arch/msg/dmarc/FDVvP_DNMxCtUtSdoqHYtHxZRxw


Best
Ale
--