IETF Logo Mail Archive

[dmarc-ietf] Is there any recommendation to send DMARC message-specific failure reports FROM:<> ?

Dilyan Palauzov <Dilyan.Palauzov@aegee.org> Sat, 25 May 2019 18:36 UTC

Return-Path: <Dilyan.Palauzov@aegee.org>
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 056151200EC for <dmarc@ietfa.amsl.com>; Sat, 25 May 2019 11:36:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=aegee.org
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 xX1UsmbrPOxN for <dmarc@ietfa.amsl.com>; Sat, 25 May 2019 11:36:00 -0700 (PDT)
Received: from mail.aegee.org (mail.aegee.org [144.76.142.78]) (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 EDC66120086 for <dmarc@ietf.org>; Sat, 25 May 2019 11:35:59 -0700 (PDT)
Received: from mail.aegee.org (localhost [127.0.0.1]) by mail.aegee.org (8.15.2/8.15.2) with ESMTP id x4PIZudm014630 for <dmarc@ietf.org>; Sat, 25 May 2019 18:35:56 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1558809356; i=dkim+sm-localhost@aegee.org; r=y; bh=jI1bcXmnqAzqxUDwe6Qo5NdPEotggewUqF/8tnZXRNE=; h=Date:From:To:Subject; b=hbS+06QRIREXfwMnoQ/daCxuBzA48JzjjWFIYgzZiZNXc0H/c64DUsWw5Ca5Anmns DJozjnLM2yrfMqOGPe3bIdAOr0Leohv500RZQUpLHOX0UH9WsNFrQwULCGBioFfNaR oaa42d+r+k1RexgEF6VTuEf1KjCbJtxpylxx+IN1qKlH2UUnWZIn3u+hYvRyQAO7Z2 pRbJYJp8Bs46k6T4m7StOx/OxZxJr/z25erdIrhGc+AywrPYLSUH3mQn6g/xHW8naZ pYoQqd6Ksa/i5gefT7aDXI/DlkfsGm3XIBf+CmIxrQ2PHrPXLZHvkpUL4RRwjlTdg8 lXUUdJ817wrqcaqTK8L3KPFV8CepbJsTv22OdIS2x3COqvYpUEB02GnWv19ouZ3urk /vORREsZTonct3Yqf5GIngj1zUnwycWgPi6243kguWpEH/xXEOlqRBZ0dmQ7pMZ0wl uBXUEcV05WOCPTNeO+GUETWh2kEW2xD0WCmrxmNag/H8TG2vaaKNAZgnoWTH5AUXaJ XZ+MOQRc9ANo9tgZUymkYP3YMoBCr6DtABv8kODVDIuWsx18QYNMdHQOIAJBEB+bdC 9ect3QAbJGJE/ZTIqeNZsHNoG+OYp3IK3RPnT4uvvX9W0A+IpirGMfmSgrLpvfL5GB W/7AxFr5hTEQKAW/VnO3NIuw=
Authentication-Results: mail.aegee.org/x4PIZudm014630; dkim=none
Received: from 87-118-146-153.ip.btc-net.bg (87-118-146-153.ip.btc-net.bg [87.118.146.153]) by webmail.aegee.org (Horde Framework) with HTTPS; Sat, 25 May 2019 18:35:56 +0000
Date: Sat, 25 May 2019 18:35:56 +0000
Message-ID: <20190525183556.Horde.zvg1bNsYbvs_enKZPKjlhVV@webmail.aegee.org>
From: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
To: dmarc@ietf.org
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset="utf-8"; format="flowed"; DelSp="Yes"
MIME-Version: 1.0
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.101.2 at mail.aegee.org
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/e36mQmL-VSfTOqKQGkVdJ1A29ik>
Subject: [dmarc-ietf] Is there any recommendation to send DMARC message-specific failure reports FROM:<> ?
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: Sat, 25 May 2019 18:36:02 -0000

Hello,

is there already any recommendation from IETF to send DMARC  
message-specific failure individual (non-aggregate) reports with  
FROM:<> (or NOTIFY=NEVER)?

Consider this scenario: an email from a domain, with DMARC policy  
“p=reject; ruf=postmaster@domain” fails validation.  A  
message-specific report is sent to postmaster@domain.  The report is  
bounced (or there is any reply on it) and the reply is again From:  
that domain and does not validate DMARC.  In turn a new  
message-specific report is sent and this loop ends, when some disk  
gets full.  With FROM:<> or NOTIFY=NEVER there would be no such loop.

Note, that DMARC aggregate reports do not have this problem.

Regards
   Дилян

v2.23.0 | Report a Bug | By Email