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

Dilyan Palauzov <Dilyan.Palauzov@aegee.org> Sun, 26 May 2019 19:01 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 E14EE1200FE for <dmarc@ietfa.amsl.com>; Sun, 26 May 2019 12:01:01 -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, 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 mo2BeH4CzY-1 for <dmarc@ietfa.amsl.com>; Sun, 26 May 2019 12:00:59 -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 CF0E31200FB for <dmarc@ietf.org>; Sun, 26 May 2019 12:00:58 -0700 (PDT)
Received: from mail.aegee.org (localhost [127.0.0.1]) by mail.aegee.org (8.15.2/8.15.2) with ESMTP id x4QJ0ueN019839; Sun, 26 May 2019 19:00:56 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=aegee.org; s=k4096; t=1558897256; i=dkim+sm-localhost@aegee.org; r=y; bh=P+POL1E+J0Y+kdM0WcuHMMMGCp9Ro5uRarCBxi1B/9w=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=ZjqTNz/0/V2mw9fZWFnpjMSqYHXlhvvvy1ko1802DOFmgDP2sTVH8g6kYPfo2506O 3icHOMuHN3vZ41vv1Ge1Rn6pvODipEn17viB6KI3jJOZOs/Z6A+SSodQQj0OcPQnnS uubaqThLM0gjbsBwJrf01AE8BKlzJOHR9rs1c/iRX4cs/AWuC/kQlk98A2QehEx3jg gZsfzSV1OlzRGE/IEfdigNVci06ovJcbSvBJOnVANXJKeKidsz5afY+otoPiKYlEK5 mcRKIBNnCcW0K3nMyiklC/OhUWfX6PUoByrK5kO9vbnlQ98UXC0Mixz1l0BT1uzFwc oDQcSRLtZFgIqeLBDlYO5K6b1lkrZuosbmn/+YcYL+VTn+Y+54PwxbS+ZVcmaEaIFY MMSFCLoS7EoZEOHGOTye9clWiuWmtQLosafrJrQYMaFKqGlT9EjhQ/Wmlgan3jpquZ xdkIvVtDsQPNQSUnuN3zlVR9/wBPMOlmqcSExhG2EbuB5bWqMpGM/xC6CgqV1jCdzH NkzgQc+CGwBcPq+NAfiGfcVFF/hDdxz2q8kxzo3FvPNNFKyrzgQhWz4w8C35qSt89H pD9w+Q/A+JyshIOXXWrnFrunrSibkmcVmnFb+BpnukvLBLnJzfOao7RgKCKcvTR5re j/gkJjajz6XtQQcafMjQIh/M=
Authentication-Results: mail.aegee.org/x4QJ0ueN019839; dkim=none
Received: from 87-118-146-153.ip.btc-net.bg (87-118-146-153.ip.btc-net.bg [87.118.146.153]) by webmail.aegee.org (Horde Framework) with HTTPS; Sun, 26 May 2019 19:00:56 +0000
Date: Sun, 26 May 2019 19:00:56 +0000
Message-ID: <20190526190056.Horde.eosw0oHN3SdnNASHChwrn88@webmail.aegee.org>
From: Dilyan Palauzov <Dilyan.Palauzov@aegee.org>
To: John Levine <johnl@taugh.com>
Cc: dmarc@ietf.org
References: <20190526050958.Horde.6VaAxRZKGLqyeJ4Uov0vrXR@webmail.aegee.org> <20190526144439.C059D2014A0B4D@ary.qy>
In-Reply-To: <20190526144439.C059D2014A0B4D@ary.qy>
User-Agent: Horde Application Framework 5
Content-Type: text/plain; charset="utf-8"; format="flowed"; DelSp="Yes"
MIME-Version: 1.0
Content-Disposition: inline
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/aYqUv2_LF2xQvPJ82pK74AdXV6Q>
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 19:01:02 -0000

Hello John,

at SMTP level the server communicates EHLO mail.modernwebsite.pl and  
ENVFROM:<>.  There is no TXT record for mail.modernwebsite.pl so SPF  
fails and cannot align.

The email itself contains “From: MAILER-DAEMON@modernwebsite.pl (Mail  
Delivery System)” without DKIM signature. ⇒ DMARC validation fails.

You can give it a try and send yourself a message to  
“postmaster@modernwebsite.pl”, the answer will be
   <template@modernwebsite.pl> (expanded from <postmaster@modernwebsite.pl>):
     unknown user: "template"

Unfortunately I had another loop back in September 2018.  I do not  
remember the details.  Given that this can happen again to somebody  
else, it is better to have recommendation sending the message-specific  
reports with FROM:<> or NOTIFY=NEVER, or at least some text  
elaborating on the attack.

Regards
   Дилян




----- Message from John Levine <johnl@taugh.com> ---------
    Date: 26 May 2019 10:44:39 -0400
    From: John Levine <johnl@taugh.com>
Subject: Re: [dmarc-ietf] Is there any recommendation to send DMARC  
message-specific failure reports FROM:<> ?
      To: dmarc@ietf.org
      Cc: Dilyan.Palauzov@aegee.org


> In article  
> <20190526050958.Horde.6VaAxRZKGLqyeJ4Uov0vrXR@webmail.aegee.org> you  
> write:
>> Hello John,
>>
>> in case of modernwebsite.pl:
>>
>> DNS TXT _dmarc.modernwebsite.pl is "v=DMARC1; p=reject; pct=100;
>> rua=mailto:postmaster@modernwebsite.pl;
>> ruf=mailto:postmaster@modernwebsite.pl; aspf=s;adkim=s;"
>>
>> 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.
>
> Just out of curiosity, where do the reports come from?  I see their
> SPF record says "mx a".
>
> _______________________________________________
> dmarc mailing list
> dmarc@ietf.org
> https://www.ietf.org/mailman/listinfo/dmarc


----- End message from John Levine <johnl@taugh.com> -----