[dmarc-ietf] Concerns for not Sending a Failure Report?

Дилян Палаузов <dilyan.palauzov@aegee.org> Fri, 02 August 2019 21:41 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 C35F41200E9 for <dmarc@ietfa.amsl.com>; Fri, 2 Aug 2019 14:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_NONE=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 giaAiHaCyd71 for <dmarc@ietfa.amsl.com>; Fri, 2 Aug 2019 14:41:09 -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 1667D120059 for <dmarc@ietf.org>; Fri, 2 Aug 2019 14:41:08 -0700 (PDT)
Authentication-Results: mail.aegee.org/x72Lf4NZ008709; auth=pass (LOGIN) smtp.auth=didopalauzov
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1564782066; i=dkim+MSA-tls@aegee.org; r=y; bh=4RVCc8zQRi5gTHndbQ4+/PXVE0+krXAwQ0Q0zNABbZo=; h=Subject:From:To:Date; b=kb+VPnZ4eht05LqreZw0XlnDcXbA3Tt5OtkeMf64LCp8zOFVBNSvnqqdY1Dr91/RC nnqA4/NZ91wkfqOLc0QVEkRic+Bv3p9y7wefM4YuMZx6ghqJXZ+qeXRFUKsOyoy02R TWMIg07cpUb0Q5guw0UgneRoqSYxEftHUZFSkbrh5OIBe7IGlYZ4q/PI528GsATiW8 cm3eEvGZCaZyCmHkiOX0bMmUDHBDSKjCB08lh1T+59vgde16XKe4cFalOLVNaD7hrF zx6rhB45DeCAwqdeAMtfvyMXP+ruHV0oyJnoKE+BYJT4P62SMT6MSRRc1/P2+pa3XX bRh52DSDYtFKGU1E5MWZwc1K96g0UnFzfGz6+57Q+KXXSCn2K8ykoVXDbcPVuaSOth BT9ooYW2opZygVVDIEafr2zzMSihstuozIUWZ8QCOAA31eBDH41TMdmLzo8v+nqlQk MAKqu+9l5eI2dT4jCofSSxAe3TY1aejK9WpfRDdi0buGAkj888eK3mf4uDIFfSSI16 ZVIK6w17w1IgZHD0FTDXThHNB16xl+TvngzSOlsC5vToN86ZnxhJsohOQQEc/pok+f 1iQQHYaeDuSAyvpHl7f/edKtL6cQ1em5axUByXzoZdw/MCtoy4yFezgU762eM2aVMV m7wiwyVjtcXukLCJLfkei2us=
Authentication-Results: mail.aegee.org/x72Lf4NZ008709; dkim=none
Received: from Tylan (87-118-146-153.ip.btc-net.bg [87.118.146.153]) (authenticated bits=0) by mail.aegee.org (8.15.2/8.15.2) with ESMTPSA id x72Lf4NZ008709 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO) for <dmarc@ietf.org>; Fri, 2 Aug 2019 21:41:05 GMT
Message-ID: <e84652a9df6b61e599f30e7fae6c0c728faf5ce5.camel@aegee.org>
From: Дилян Палаузов <dilyan.palauzov@aegee.org>
To: dmarc <dmarc@ietf.org>
Date: Fri, 02 Aug 2019 21:41:04 +0000
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.33.90
MIME-Version: 1.0
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/sWB5eWVJCoMxCP8-RSRbarIeLqY>
Subject: [dmarc-ietf] Concerns for not Sending a Failure Report?
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, 02 Aug 2019 21:41:11 -0000

Hello,

I just thougth once again on this.

Some of the senders of aggregate reports offer free mailboxes.

Aggregate reports show that emails from a host to a provider of free mailboxes sometimes do not validate DMARC.

The one provider sending emails opens a free mailbox on the receiver and then sends a secret copy of each, otherwise
ordinary delivered email, to that special mailbox.

Then the mails from that mailbox are downloaded, and the A-R header is checked.  By this way the sender finds out, which
messages exactly have failed DMARC validation.

At the end the same information is obtained, that can be obtained by exchanging a failure report: which messages have
failed.

Has somebody done this?

Why does it have to be that complicated?

Regards
  Дилян