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

Alessandro Vesely <> Sun, 04 August 2019 10:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 24223120026 for <>; Sun, 4 Aug 2019 03:56:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Status: No, score=-4.301 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_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1152-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 85th624ZxMYb for <>; Sun, 4 Aug 2019 03:56:09 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 162B2120025 for <>; Sun, 4 Aug 2019 03:56:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=delta; t=1564916167; bh=5q9iFJb0gDpmm0VudgOv/czGkcCda9zVP/Mf1cbA+HU=; l=1661; h=To:References:From:Date:In-Reply-To; b=Bnodeu/AOrEOqR7mSLVgGTJZWMOISVFDLhAQdf8JCT8+RV9hAwf9YSkibRivj/a6l HSUAo/r3KGPF6CnD2W31RipQKfC06QYWo+sMfA3Zcj30ern4dRAl0+8/BuDRiqA+dZ iA3WznGLQx+86ylyjGkuZbRiIo3ivrxxrOHANG9d6I2hXh7lTl2D6pTUHMDh7
Authentication-Results:; auth=pass (details omitted)
Received: from [] (pcale.tana []) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by with ESMTPA id 00000000005DC03D.000000005D46B9C7.00001743; Sun, 04 Aug 2019 12:56:07 +0200
References: <> <> <> <> <>
From: Alessandro Vesely <>
Openpgp: id=0A5B4BB141A53F7F55FC8CBCB6ACF44490D17C00
Message-ID: <>
Date: Sun, 4 Aug 2019 12:56:06 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <>
Subject: Re: [dmarc-ietf] Concerns for not Sending a Failure Report?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 04 Aug 2019 10:56:12 -0000

Hi Dilyan,

On Sun 04/Aug/2019 12:10:51 +0200 Дилян Палаузов wrote:

> The receiving server knows, which IP address sent the mail and it knows, to
> which IP addresses set the failure report will go.  If there is a match in
> the IP addresses, then the receiving server knows that the one who will get
> the report is also the one, who has anyway access to the message.

That's not always true.  For example, I know of mailbox providers who, on
delivery, automatically encrypt cleartext messages to the public key of the
recipients, including the Sent folder.  Operators at that provider's aren't
able to sniff message contents unless they're sent back on failure by receiving
sites.  In general, users trust their mailbox providers also because of the
policies they enact.  Matching those policies with unwarranted disclosure of
messages is not straightforward.

In addition, the most interesting reports are messages not coming from my IP.
Scammers abusing may domain name use their own IPs.  I see those failures in
the aggregate reports, but don't know if the IPs mentioned there correspond to
mailing lists or other legitimate forwarders, or even some ill-informed users
of mine who send their mail through their ISPs.  That's why I need failure
reports.  It would be enough if the aggregate reports contained an indication
of the spamminess of those messages, or the reputation of those IPs.

Failure reports for messages originating from my IP are only useful for
debugging.  An activity which I can more easily do by using free mailboxes, as
you said, or sites specifically dedicated to testing email.