Re: [dmarc-ietf] Forensic report loops
Дилян Палаузов <dilyan.palauzov@aegee.org> Fri, 15 January 2021 21:40 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 03B903A11F7 for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 13:40:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
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, HTML_MESSAGE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] 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 Ii2gAwR40rau for <dmarc@ietfa.amsl.com>; Fri, 15 Jan 2021 13:40:22 -0800 (PST)
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 621EE3A11F6 for <dmarc@ietf.org>; Fri, 15 Jan 2021 13:40:21 -0800 (PST)
Authentication-Results: mail.aegee.org/10FLeDEW289960; auth=pass (LOGIN) smtp.auth=didopalauzov@aegee.org
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1610746816; i=dkim+MSA-tls@aegee.org; bh=y63BcwR5gn/bJlqa0HZDRMYudXa1kmkIAUMjaYbTpLU=; h=Subject:From:To:Cc:Date:In-Reply-To:References; b=ZATi3aB57bgAJBM3qgSnSBk+2O9uMGJyoJ267DmuqlHW5L/Li1BLqPfJAyKKxdcmt Ixyx4dk3Ptd9ROjCrzlCMKhIZx0vFCCaabtYsYaZytHgtuXyqs6moTULEwC2nOJsS5 lF54d4cTWpYmV3DPPup5VIxSEhGMHJZamyIiGX89f8A434kV8EdEEg72CwAEZ8dF+i JNmel0MR33X8OKaDp0JXx/o/km1QsMsGwlxJzqhOHsANFGJbpiM/vZ89MtDtkRn3za KnTwhvGApZ7ho3lefooBVQIF5C8Uk0y7e1XzJTRAlFnRvn7nF2zw38ELih54slq8tD xaKseFAv/IfGk/qZHsCCOrHgt5UW4BFIVNmbbM3RVpT/7SMPgLlT/ieeXZb+4saBsg mylNjTDSYcv1q9f3fp9dGjYvW0P40nPDVO6lk/6Zvz7eMd0HcB9FIz+U4ORfxiJgCp m6Z+C4CPmakPWE+cD4/Ja18i2Cn4aK6DOr6ix1U+3uuaBLFJAEfxuivnxm5woiLkoD rw/plVIIPrpJKAfkCs4rW2SruXu4yWP2KHpEZMgN3yDGZSDxjh3jY5IWWdrw+vTVsH EWLDrxWop+5TVcNK2Rew7KzC8OLf7nX5WO5FEzqRJ7HiOeMW+h7k8KW05J+Qgj4D26 slXl6GBvd/J2lOZHtFuVOUx8=
Authentication-Results: mail.aegee.org/10FLeDEW289960; dkim=none
Received: from [192.168.0.125] (87.118.146.153.topnet.bg [87.118.146.153] (may be forged)) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id 10FLeDEW289960 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 15 Jan 2021 21:40:14 GMT
Message-ID: <e5d26bccdadc2abb2390f2a491ef5894d5641048.camel@aegee.org>
From: Дилян Палаузов <dilyan.palauzov@aegee.org>
To: Douglas Foster <dougfoster.emailstandards@gmail.com>, "Murray S. Kucherawy" <superuser@gmail.com>
Cc: IETF DMARC WG <dmarc@ietf.org>, "Kurt Andersen (b)" <kboth@drkurt.com>
Date: Fri, 15 Jan 2021 23:40:13 +0200
In-Reply-To: <CAH48Zfz4yGzGZcXJBjdeyO7dPK405EtmRebkgvMTS34Jgek2zg@mail.gmail.com>
References: <CAL0qLwaZx97cztehz_o=cCVZRbEP_yFVS9hTqWDKg7cMgjNvFg@mail.gmail.com> <9b68024a-f538-af7a-3a9b-e2ad2657ce9b@crash.com> <621d4aa5a72baf46b45a005f8e45eab6f7421e50.camel@aegee.org> <CAL0qLwa2Xy-aM_p1ebmHfOvPfo8SKeivMjp4qQSh_AyXHWr=-w@mail.gmail.com> <CABuGu1oK+4xHjs-o0i617MGxuGaQVmrR-3_Tfrec=_1BWz5NRg@mail.gmail.com> <CAL0qLwbeR_HGY9kFc9WxqnfCOqatmPKtdaT2x-LSsrAuxNMRgg@mail.gmail.com> <CAH48Zfz4yGzGZcXJBjdeyO7dPK405EtmRebkgvMTS34Jgek2zg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=-0Do961LE++DPOjml0lY9"
User-Agent: Evolution 3.39.2
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/mdo7sFEttPO230wCFJKvF8roLSg>
Subject: Re: [dmarc-ietf] Forensic report 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: Fri, 15 Jan 2021 21:40:25 -0000
Hello, Am Freitag, dem 15.01.2021 um 16:31 -0500 schrieb Douglas Foster: > I would think this should prevent problems if at least one complies: > > Reports should be sent from a no-reply account so that any auto-reply > will be rejected as invalid recipient. DMARC reporting SHOULD NOT > occur for such messages, even if the DATA section is accepted before > rejecting or discarding the message. > > Report reception accounts should be dedicated to this purpose. > Unacceptable incoming messages to this account SHOULD be excluded > from DMARC reporting, regardless of reason. Accepted messages MAY > also be excluded from DMARC reporting. > this text suggests WHAT to do, but not WHY to do it. In my opinion any suggested workflow shall be accomplished by problem description, so that the implementers can understand the rationale of the proposed solution (and thus higher the chances, that the endless loops are prevented). I put the problem description in my previous mail on this mailing list. Greetings Дилян > Doug Foster > > On Fri, Jan 15, 2021, 11:25 AM Murray S. Kucherawy > <superuser@gmail.com> wrote: > > On Thu, Jan 14, 2021 at 9:51 AM Kurt Andersen (b) > > <kboth@drkurt.com> wrote: > > > I thought that we discussed that ticket and decided that the > > > incidence of problems was low enough to warrant a "WONT FIX" > > > determination. > > > > > > > > > https://mailarchive.ietf.org/arch/browse/dmarc/?gbt=1&index=W3uGPEpT3Yi5lqKntZXyL8jkNjk > > > > > > > > > We did, and if it had only ever come up exactly once, I might think > > nothing of it. But here it is again. Now I'm inclined to think > > where there's smoke there's fire, and this might require more > > consideration. > > > > -MSK, participating > > _______________________________________________ > > dmarc mailing list > > dmarc@ietf.org > > https://www.ietf.org/mailman/listinfo/dmarc > _______________________________________________ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc
- [dmarc-ietf] Forensic report loops Murray S. Kucherawy
- Re: [dmarc-ietf] Forensic report loops Steven M Jones
- Re: [dmarc-ietf] Forensic report loops Juri Haberland
- Re: [dmarc-ietf] Forensic report loops Дилян Палаузов
- Re: [dmarc-ietf] Forensic report loops Murray S. Kucherawy
- Re: [dmarc-ietf] Forensic report loops Murray S. Kucherawy
- Re: [dmarc-ietf] Forensic report loops Alessandro Vesely
- Re: [dmarc-ietf] Forensic report loops John Levine
- Re: [dmarc-ietf] Forensic report loops Kurt Andersen (b)
- Re: [dmarc-ietf] Forensic report loops Murray S. Kucherawy
- Re: [dmarc-ietf] Forensic report loops Douglas Foster
- Re: [dmarc-ietf] Forensic report loops Дилян Палаузов
- Re: [dmarc-ietf] Forensic report loops are not a … John Levine
- Re: [dmarc-ietf] Forensic report loops are not a … Douglas Foster
- Re: [dmarc-ietf] Forensic report loops are not a … Murray S. Kucherawy
- Re: [dmarc-ietf] Forensic report loops are not a … John R Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… Juri Haberland
- Re: [dmarc-ietf] Forensic report loops are a prob… John Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… Alessandro Vesely
- Re: [dmarc-ietf] Forensic report loops are a prob… John R Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… Alessandro Vesely
- Re: [dmarc-ietf] Forensic report loops are a prob… John R Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… Murray S. Kucherawy
- Re: [dmarc-ietf] Forensic report loops are a prob… John Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… Murray S. Kucherawy
- Re: [dmarc-ietf] Forensic report loops are a prob… John R Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… Steven M Jones
- Re: [dmarc-ietf] Forensic report loops are a prob… Steven M Jones
- Re: [dmarc-ietf] Forensic report loops are a prob… Douglas Foster
- Re: [dmarc-ietf] Forensic report loops are a prob… Alessandro Vesely
- Re: [dmarc-ietf] Forensic report loops are a prob… Murray S. Kucherawy
- Re: [dmarc-ietf] Forensic report loops are a prob… John R Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… Murray S. Kucherawy
- Re: [dmarc-ietf] report floods, not Forensic repo… John R Levine
- Re: [dmarc-ietf] Report bombing is a prolem, Fore… John Levine
- Re: [dmarc-ietf] Report bombing is a prolem, Fore… Douglas Foster
- Re: [dmarc-ietf] Report bombing is a prolem, Fore… Alessandro Vesely
- Re: [dmarc-ietf] Report bombing is a prolem, Fore… John Levine
- Re: [dmarc-ietf] Report bombing is a prolem, Fore… Alessandro Vesely
- Re: [dmarc-ietf] Report bombing is a prolem, Fore… John R Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… Dave Crocker
- Re: [dmarc-ietf] Forensic report loops are a prob… Michael Thomas
- Re: [dmarc-ietf] Forensic report loops are a prob… Dave Crocker
- Re: [dmarc-ietf] Forensic report loops are a prob… Alessandro Vesely
- Re: [dmarc-ietf] Forensic report loops are a prob… Dave Crocker
- Re: [dmarc-ietf] Forensic report loops are a prob… Michael Thomas
- Re: [dmarc-ietf] Forensic report loops are a prob… Michael Thomas
- Re: [dmarc-ietf] Forensic report loops are a prob… Dave Crocker
- Re: [dmarc-ietf] Forensic report loops are a prob… Michael Thomas
- Re: [dmarc-ietf] Forensic report loops are a prob… Dave Crocker
- Re: [dmarc-ietf] Forensic report loops are a prob… Michael Thomas
- Re: [dmarc-ietf] Report bombing is a prolem, Fore… Dotzero
- Re: [dmarc-ietf] Forensic report loops are a prob… John Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… John Levine
- Re: [dmarc-ietf] Forensic report loops are a prob… Dave Crocker
- Re: [dmarc-ietf] Forensic report loops are a prob… Michael Thomas
- Re: [dmarc-ietf] Forensic report loops are a prob… Dave Crocker
- Re: [dmarc-ietf] Forensic report loops are a prob… Dotzero
- Re: [dmarc-ietf] Forensic report loops are a prob… Michael Thomas
- Re: [dmarc-ietf] Forensic report loops are a prob… Michael Thomas
- Re: [dmarc-ietf] Forensic report loops are a prob… Dave Crocker
- Re: [dmarc-ietf] Forensic report loops are a prob… Michael Thomas
- Re: [dmarc-ietf] Forensic report loops are a prob… Dave Crocker
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… John R Levine
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Dave Crocker
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Michael Thomas
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Dave Crocker
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Michael Thomas
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Dave Crocker
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Douglas Foster
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Michael Thomas
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Michael Thomas
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Dave Crocker
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Seth Blank
- Re: [dmarc-ietf] Report bombing is a prolem, Fore… Alessandro Vesely
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Alessandro Vesely
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Dave Crocker
- Re: [dmarc-ietf] DMARC'ed reports, was Forensic r… Alessandro Vesely
- Re: [dmarc-ietf] Report bombing is a prolem, Fore… John R Levine