IETF Logo Mail Archive

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

John Levine <johnl@taugh.com> Wed, 09 December 2020 00:04 UTC

Return-Path: <johnl@iecc.com>
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 5B4383A138B for <dmarc@ietfa.amsl.com>; Tue, 8 Dec 2020 16:04:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=Qm3XusOq; dkim=pass (2048-bit key) header.d=taugh.com header.b=DmTtDUlu
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 2d--CkpXm9aE for <dmarc@ietfa.amsl.com>; Tue, 8 Dec 2020 16:04:54 -0800 (PST)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 1728B3A1384 for <dmarc@ietf.org>; Tue, 8 Dec 2020 16:04:48 -0800 (PST)
Received: (qmail 94280 invoked from network); 9 Dec 2020 00:04:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=17043.5fd0149f.k2012; bh=XqAENsmfTSehf7nt97YUxDrI+Otsf83SZtgy0X8H3kM=; b=Qm3XusOq+A95Bbzf4bOVQqz8nRWrE5LHwb39CDhpB4V4imQRR0TBLVAXInRjSJvDty1yNWCYcx0rdj+2te96alTfI4DvWQi2bK9qK4Midzw617uO69rBfTIwTb+mW0Y9SYl95kLb0IgmRgQXnAppepryerS14DQJSSedfs8zQefsOxY0EB1etTW//Yt71eC2gdX43sc8j+OgQwQMF8mW7t00hxCWAAMrwye+SJyOoWYpYE2f2fiAn1Fe/GSkjJxkxGe4bWqcLHNR1ej5q35rB0UldiKNXrGM/Atc1PnmXqHKGPXu33dJGDZbreSwpUpYsEk7oQB2mXxIqUlEbmm6oA==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=17043.5fd0149f.k2012; bh=XqAENsmfTSehf7nt97YUxDrI+Otsf83SZtgy0X8H3kM=; b=DmTtDUluL38vOxJNMiTU9ExH1Px5UzVoTg97rNvL1Py/06b8xqASemf/YXh56K92s1MPyEcQ4rYAGQAFJaU887X9k6Wb2GUnmjU1XTsHj7bP1/kPlcjtjgOiRhPR14HuB94LjVBRoXc5UWqRi4/ixLB5vRq6w0UBmRDNcoc13UbfS15VSJr9nwPVVHKoG1Tx2fcpP+y+ZSjOGYIk1MTkcyybVHDjwko44vhwWJIGkyplkrMlpiW8C68CMGxX6WiOkTV5Y0lE4zh34O2gR7XuX52ETGDBZcF3L69nK0BsRLY49noa1Ztgh2lCKezlAtLZbC8dZFgFr0Y4uTsKM4g6Jg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 09 Dec 2020 00:04:47 -0000
Received: by ary.qy (Postfix, from userid 501) id 205FF2938F97; Tue, 8 Dec 2020 19:04:46 -0500 (EST)
Date: Tue, 08 Dec 2020 19:04:46 -0500
Message-Id: <20201209000447.205FF2938F97@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: vesely@tana.it
In-Reply-To: <62b7d80e-2c39-4d02-0b5a-bd6ede7d51dc@tana.it>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/1MYrtLsgwMYaeAczc4_CjJ0p1mU>
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: Wed, 09 Dec 2020 00:04:57 -0000

In article <62b7d80e-2c39-4d02-0b5a-bd6ede7d51dc@tana.it> you write:
>When dmarc authentication method fails on a message, an MTA may decide to send 
>a failure report.  If the message is itself a failure report, however, no 
>failure report should be sent.  The question is, how does the MTA determine 
>whether the message is a failure report, without resorting to lengthy content 
>analysis?

If the top level content-type is multipart/report, that would be a
pretty good signal.

Nonetheless I believe this is not a real problem and we should just
close the ticket.

Can anyone tell us about failure loops that caused an actual problem.  "We sent
one failure message per day every day" is not something I would call a problem.

R's,
John

v2.23.0 | Report a Bug | By Email