Hello John,
in case of modernwebsite.pl:
DNS TXT _dmarc.modernwebsite.pl is "v=DMARC1; p=reject; pct=100;
rua=mailto:[email protected];
ruf=mailto:[email protected]; aspf=s;adkim=s;"
Emails to [email protected] 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.
The loop happens, when you do send failure reports, not just receiving such.
Regards
Дилян
----- Message from John Levine <[email protected]> ---------
Date: 25 May 2019 17:53:17 -0400
From: John Levine <[email protected]>
Subject: Re: [dmarc-ietf] Is there any recommendation to send DMARC
message-specific failure reports FROM:<> ?
To: [email protected]
Cc: [email protected]
In article
<[email protected]> you
write:
Consider this scenario: an email from a domain, with DMARC policy
“p=reject; ruf=postmaster@domain” fails validation. A
message-specific report is sent to postmaster@domain. The report is
bounced (or there is any reply on it) and the reply is again From:
that domain and does not validate DMARC. In turn a new
message-specific report is sent and this loop ends, when some disk
gets full. With FROM:<> or NOTIFY=NEVER there would be no such loop.
The trickle of failure reports I get are from addresses like these:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
I would expect that any mail sent to those addresses is unlikely to
provoke a failure report, no matter how mangled it is when it arrives.
We've had failure reports for almost seven years and I don't ever
recall someone getting into a mail loop so it's not a problem in
practice.
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
----- End message from John Levine <[email protected]> -----
_______________________________________________
dmarc mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmarc
