Re: [dmarc-ietf] Forensic report loops

"Murray S. Kucherawy" <> Thu, 14 January 2021 15:28 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5788E3A10DA for <>; Thu, 14 Jan 2021 07:28:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YkQU4gGTcEGC for <>; Thu, 14 Jan 2021 07:28:30 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::e36]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E29A23A10D3 for <>; Thu, 14 Jan 2021 07:28:29 -0800 (PST)
Received: by with SMTP id j140so3292698vsd.4 for <>; Thu, 14 Jan 2021 07:28:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DRT/iVsyKWMn3yTRnxoKN6KwcdN0/CeVzlnK6hSuDwg=; b=tQYVyE7p9Gt54qRQwro23IBqyFzbJ2AJNCI+d90oYDcaiMbCFaEofJiPZwTfFzwiMT lz0v9Km0PMEXXECSPNLiku8+Wzf4y5r+6PXlTt2QE01JDxXL7C7FOuUIcA1liEYhC8eD xNNDc26xbQ2Wf+k1gxSOBSHCBktfFYqncgnP7QFhP225kTNwiv1OYQXGhi8q8BaqDfi/ L4K9Zo6LI+FS63JTibuBDzYJtULowZryYihkuXu+w6PdrWAKe50uOoBDuwopEbi/LGyb Gm/xh91nYQZRp4jy2frkyVumv+oinJnkrl/DcyFBhkD1GpM5yzXf9TzojMwvvk5zdXWk wTbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DRT/iVsyKWMn3yTRnxoKN6KwcdN0/CeVzlnK6hSuDwg=; b=GjU4WSxTqjbPGNiyQmVGw7VdpesOvcK40en12HRoUkWg85tDrpjQiIIGH1IciUJMxz oLn3Tlse2sLkPlPxr68d+oAzpQniJiOd+EsiwvdonW+YyEgmPJnrcxH486/RsKzvSc+t 03fzuDw9UvMReXkj6tBao+pp0UPt4wXACourkNH3WVlIKJwVT/H6hDptksG7eEsCafL+ qPrux8/D7KzJVV3qYz0JRohy8CxOVdpMZB+jf7EJzM8svQsjfTYypOw6CvwWpYWkKMam 1LqYGRxnvrp3CRsJ8j2i4tNlpI7ZVrngdqqp0e2KnIZwzF9K/8OLpgfWKswisKuaDQZU te/Q==
X-Gm-Message-State: AOAM533dTrc3WNj/E3QegR1FX7gRSQDH0XYBz5Xl13F39/6XcB2yQYGV lyYWZfCYwl7Hnu2V4cqHuSNG5ZYCpZZK4qido18=
X-Google-Smtp-Source: ABdhPJwkqOol0NIRueGz774QgrxjT84mvEs9cee+BTydUrAhtpmM13mb8ecmISm36B1YhQBltROzLyxkWGsqnUAKkiU=
X-Received: by 2002:a67:fb46:: with SMTP id e6mr7284946vsr.40.1610638108975; Thu, 14 Jan 2021 07:28:28 -0800 (PST)
MIME-Version: 1.0
References: <> <> <>
In-Reply-To: <>
From: "Murray S. Kucherawy" <>
Date: Thu, 14 Jan 2021 07:28:17 -0800
Message-ID: <>
To: =?UTF-8?B?0JTQuNC70Y/QvSDQn9Cw0LvQsNGD0LfQvtCy?= <>
Content-Type: multipart/alternative; boundary="00000000000058e7dc05b8dde851"
Archived-At: <>
Subject: Re: [dmarc-ietf] Forensic report loops
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Jan 2021 15:28:31 -0000

On Thu, Jan 14, 2021 at 3:12 AM Дилян Палаузов <>

> I have not read the thread “Ticket #28 - Failure report mail loops”.

Thanks, and apologies to the group; I should've checked for an open ticket
on this topic first.

This one recommends rate limiting rather than simpler "don't" type
guidance.  I think we can table this until that ticket is open.

A possible approach is not to send failure reports for messages
> received on the address for accepting aggregate/forensic reports.
> These messages shall just be excluded from all calculations.

That seems plausible, though less bulletproof than simply using the address
already reserved by the email standard for administrative messages.