IETF Logo Mail Archive

Re: [dmarc-ietf] Forensic report loops are a problem

John Levine <johnl@taugh.com> Wed, 27 January 2021 20:37 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 451623A03FA for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:37:18 -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=FkYIPMFX; dkim=pass (2048-bit key) header.d=taugh.com header.b=dA5v+byT
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 H0JOz-mAPNeX for <dmarc@ietfa.amsl.com>; Wed, 27 Jan 2021 12:37:16 -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 A3F7C3A03F3 for <dmarc@ietf.org>; Wed, 27 Jan 2021 12:37:16 -0800 (PST)
Received: (qmail 38719 invoked from network); 27 Jan 2021 20:37:15 -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=973c.6011cefb.k2101; bh=8w4SeMz/BfJIi0znR1et85e9OldGyqBiVRx0csAuT2Q=; b=FkYIPMFXEyHFxgOxUna8RQPDOybBQPF77TzfRYAFd3FD+/ezu+DbOr/VdXokzvzWUPke3Um/nqo9CkGA/yGx2Avfb8sq2YPsj6uNkX4o0PDUeQD8WaCO3fYfbOIvk9Ro7Utayu3CiMkl6j3NtZRO4za+kAoxIqiS3w2qgdo6PHUXJ0gH4J47Uv9MTzXYCtg6Ff3+MI85ReRbpQFa0Xf/3rL7ax/oe8iXRfFpKd1U2tSagvXpaZvlPk9chhjmwOyvSo70qS0JXWot6vi5i5/dhgdzKKfrqCt1gtzKx0UulbrJjPTuY2F8orPffQ2r9KBDhZ9hVoYe8XydSyZxaJECBw==
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=973c.6011cefb.k2101; bh=8w4SeMz/BfJIi0znR1et85e9OldGyqBiVRx0csAuT2Q=; b=dA5v+byTrVcRuO5IO7yVlhD7z/1Upe/0z1eXw0l99PiW2CITHWPL6iS9FFSJn8iyQ3mkfz08kIfPB/UTaRzc++5iF0qly1RK5LCf7Zv5W9XnH8vPGOl/e5BwcEKLOV2hqigHDLpMLVcuqe1fimtIBTJVCf/TauNi5LfmKmKI4YUXbCm64TERPNgxxTp3oYKkP1ndPe0LAXwit1JjWPWots4WA9HkH9b9+NKLI8J5maMkDrT4d0Bx59grgpLPy6Sybme1DUPAIKiA1nUCO1AQdWHQx3ByHWW6+LfUbqfovATTqC+OBj2ZQi+G246vMKC0hOHoUGBQqMypsa1wk9G4sw==
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; 27 Jan 2021 20:37:14 -0000
Received: by ary.qy (Postfix, from userid 501) id 007C86CDB9CA; Wed, 27 Jan 2021 15:37:13 -0500 (EST)
Date: Wed, 27 Jan 2021 15:37:13 -0500
Message-Id: <20210127203714.007C86CDB9CA@ary.qy>
From: John Levine <johnl@taugh.com>
To: dmarc@ietf.org
Cc: superuser@gmail.com
In-Reply-To: <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com>
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/FS9riHMFGX8EbmtJD2M2PATMRSg>
Subject: Re: [dmarc-ietf] Forensic report loops are a problem
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, 27 Jan 2021 20:37:18 -0000

In article <CAL0qLwY5BbwvS9XXqBk=Mp074ntN=NeS97pJAxPBdQEZAsgohg@mail.gmail.com> you write:
>-=-=-=-=-=-
>
>On Wed, Jan 27, 2021 at 10:38 AM John R Levine <johnl@taugh.com> wrote:
>
>> Stop there.  If you don't want failure reports, don't send unaligned
>> messages.
>
>I could be sold on the idea that there's not a problem for us to fix in the
>protocol here, but what about the notion that it's something that might
>warrant a sentence or two of informative text (i.e., that this is a problem
>that can occur and possibly cause operational pressure)?

I still don't understand why failure reports about messages that
happen to be failure reports are in any way special.

The report is after all a brand new message which I would hope is sent
the way tou send any other message, and should be aligned if the rest
of your mail is.

R's,
John

v2.23.0 | Report a Bug | By Email