IETF Logo Mail Archive

Re: [dmarc-ietf] Is there any recommendation to send DMARC message-specific failure reports FROM:<> ?

Дилян Палаузов <Dilyan.Palauzov@aegee.org> Sun, 26 May 2019 05:28 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 0087012011B for <dmarc@ietfa.amsl.com>; Sat, 25 May 2019 22:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.019
X-Spam-Level:
X-Spam-Status: No, score=-1.019 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 AjyV86hFbcm5 for <dmarc@ietfa.amsl.com>; Sat, 25 May 2019 22:28:42 -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 7E1B4120115 for <dmarc@ietf.org>; Sat, 25 May 2019 22:28:42 -0700 (PDT)
Authentication-Results: mail.aegee.org/x4Q5Sbk5020002; auth=pass (PLAIN) smtp.auth=didopalauzov
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1558848519; i=dkim+MSA-tls@aegee.org; r=y; bh=gLJSK2uLty806SMzQ2YpI2M1zmkAC867Iu051dZpWFs=; h=Date:In-Reply-To:References:Subject:To:From; b=EUm2qx83UR1+3FuuynPUeGfUht44EDEf06/CTwLMzN0g/JBRTd/iFB9mV+bqE5l2Y xmKZgzKLzsGiE5e4Vi1Yg7ubxItyyuTnoPVG/v4OhbwHnOu+B7Eg9Hyp/sF8R9VWzB GAAntKonI9la0sMqKcdiuXx1OsLYThL3FrcUGI/q3sza2IQOmGLWtPDAn0Lkx9KXKs SPdQNeqdGOwaa29D9ic+yIex9vGOBoecQd5hbIVttXtrVNmoZTn40PlHQBTPRLBeyE slx9LCysUxJeJ0zNH/suPYXklluJ4uiSrzy2bK6Rl0f0ZxolAaj2LKBworxfDDEBf3 oq0OOkV4xlz4JZaB2jv5eZoX2KRVBit/BmlHMKfvTnm7DTF3BBVlBArFKpHz6YOfCV QxgnfTk6EL7QXnI93alSwx3ccU0ObRqj8IhASt5kEMKOZer6IIOS5WiR+q0glujYR8 XYUaCNKXK0YT/As8mSGffOzLwp7yMwXxQU5HW5wihQSle9iwmqLyljF6olUxMm0UhY 51BLD5/OpxcvVtp+C7LUATw7njjyEcBTDGWMk8iz/etZhP/dlK2fizCJYCli6xjVZw ahaFJxr4pu5rrxHS7Ycnvm3QCb7keY/CaoMIZhcCPBNSIRRbJxLE3ZTuOXeXuSE7LA tv7l2UM3Q1ilJvtpYAlKpivc=
Authentication-Results: mail.aegee.org/x4Q5Sbk5020002; dkim=none
Received: from [192.168.1.101] (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 x4Q5Sbk5020002 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <dmarc@ietf.org>; Sun, 26 May 2019 05:28:38 GMT
Date: Sun, 26 May 2019 08:28:29 +0300
User-Agent: K-9 Mail for Android
In-Reply-To: <26760626-b3f2-b8cd-f31f-d78b487db35c@spamtrap.tnetconsulting.net>
References: <20190525183556.Horde.zvg1bNsYbvs_enKZPKjlhVV@webmail.aegee.org> <20190525215318.1580620149E52F@ary.qy> <20190526050958.Horde.6VaAxRZKGLqyeJ4Uov0vrXR@webmail.aegee.org> <26760626-b3f2-b8cd-f31f-d78b487db35c@spamtrap.tnetconsulting.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----2FW1RKNTTT5RSLW73UWL8R4DIC1M8B"
Content-Transfer-Encoding: 7bit
To: dmarc@ietf.org
From: Дилян Палаузов <Dilyan.Palauzov@aegee.org>
Message-ID: <115E2CD4-AF67-4A8D-85BA-567BA74D34A4@aegee.org>
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/txxspM7jgQbI8WPNDU3esttHwSE>
Subject: Re: [dmarc-ietf] Is there any recommendation to send DMARC message-specific failure reports FROM:<> ?
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: Sun, 26 May 2019 05:28:44 -0000

Hello Grant,

it is a misconfiguration, but it still creates a mail loop for the site, that is not misconfigured.

To what I can say the emails are accepted at SMTP time and then bounced.

I  not asking to modify DMARC, but to recommend sending message-specific, individual failure reports FROM: <>, in order to be protected from “misconfiguration attacks”.

Regards
  Дилян

On May 26, 2019 8:20:50 AM GMT+03:00, Grant Taylor <gtaylor=40tnetconsulting.net@dmarc.ietf.org> wrote:
>On 5/25/19 11:09 PM, Dilyan Palauzov wrote:
>> Emails to postmaster@modernwebsite.pl are answered with “Undelivered 
>> Mail Returned to Sender”.  The answers do not align to the DMARC
>policy 
>> reject, so a new message-specific failure repot is sent.
>
>Are the reports that you are sending being accepted at SMTP time and 
>then bounced after the fact?
>
>That sounds like (what I think is) a misconfiguration on their end.
>
>As such, I'm less inclined to think that modifying DMARC is the proper 
>thing.  Especially if this is a rare occurrence (as in a very select 
>candidate).
>
>
>
>-- 
>Grant. . . .
>unix || die

v2.23.0 | Report a Bug | By Email