<div dir="ltr"><div dir="ltr">> procmail is to late to solve the problem in milters<br>
<br>Agreed but since what we're talking about is delivery rejections due to no/bad accounts is (IMO) viable.<br><br>As I understand it (and correct me if I'm wrong), Report-NO-Send lists are lists of domains which are not to receive reports. it's this implementation (blocking by domain) that's not useful<br></div><div><br>"Report-NO-Send" lists should be based on email addresses, rather than domains. The biggest reason is that if a records RUA/RUF address is corrected then emails can resume for the domain.<br></div><div dir="ltr"><br>
> imho best way to solve is to create a new specifik milter to test that <br>
> mailto: can be mailed to, <br><br></div><div>That's a lot of potential overhead depending on the amount of emails that are received.<br></div><div>Additionally, there's also a chance this method could end up causing your mail server to be black-listed<br></div><div dir="ltr"><br>> why would domain owners like to have dmarc reporting when <br>
> there mailserver does not accept it<br><br></div><div>Legitimate reasons: Address changed and record wasn't, Address no longer valid (person left, etc) and record wasn't changed, person who setup the record applied it to the wrong address, etc<br><br></div><div>Not so legitimate reasons: Just to be an *SS<br>
</div></div><br><div class="gmail_quote"><div dir="ltr">On Thu, Jan 3, 2019 at 10:14 AM Benny Pedersen <<a href="mailto:me@junc.eu">me@junc.eu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Ken skrev den 2019-01-03 14:38:<br>
<br>
> I'm in full agreement, it is very annoying.<br>
<br>
users tend to use loopback ip mx for reporting, yes i have seen it<br>
<br>
> Unfortunately, the only other option I can think of at the moment<br>
> would be not sending reports.<br>
<br>
that only solves half of the problem, mailto: links can be to totaly <br>
diffrent domain then sender envelope domain :/<br>
<br>
so it support ddos another domain mx, why ietf have not thinked about <br>
that possible is imho sadly<br>
<br>
> It should be possible to create a filter for procmail (or whatever) to<br>
> do what you're looking for. But that's well beyond me<br>
<br>
procmail is to late to solve the problem in milters<br>
<br>
imho best way to solve is to create a new specifik milter to test that <br>
mailto: can be mailed to, if not succee tempfail senders that shoot them <br>
self in foots, why would domain owners like to have dmarc reporting when <br>
there mailserver does not accept it<br>
<br>
there was a time i see lots of domains used mx to 127.0.0.1, this was <br>
simple to reject in postfix, now we need to mx check mailto: in dmarc :/<br>
_______________________________________________<br>
opendmarc-users mailing list<br>
<a href="mailto:opendmarc-users@trusteddomain.org" target="_blank">opendmarc-users@trusteddomain.org</a><br>
<a href="http://www.trusteddomain.org/mailman/listinfo/opendmarc-users" rel="noreferrer" target="_blank">http://www.trusteddomain.org/mailman/listinfo/opendmarc-users</a><br>
</blockquote></div>