They seem to be a Cisco shop, so it’s likely the Cisco Appliance is sending
them it as it considers the RUA address another user
On Fri, Sep 4, 2020 at 12:09 PM, vom513 via mailop <mailop@mailop.org> wrote:
>> On Sep 4, 2020, at 12:30 PM, John Levine via mailop <mailop@mailop.org>
>> wrote:
>>
>> In article <d0a2ada0-541e-4e87-a09c-2b552ebf9...@gmail.com>,
>> vom513 via mailop <vom...@gmail.com> wrote:
>>> PS: I’m just trying to persuade them to not send out DMARC agg reports for
>>> mail sent to their rua address in the
>>> first place (loop). Not the biggest deal in the world but annoying.
>>
>> Please don't.
>>
>> DMARC reports are designed to be sent and consumed automatically. I
>> have no idea what reports people are sending me day to day, since
>> they're parsed and put into the database without my even seeing them.
>> I'm sure this is quite typical.
>>
>> If for some reason you have trouble dealing with tiny reports, it's
>> not hard to figure out how to throw them away automatically.
>>
>> R's,
>> John
>>
>
> Yep, I’m already using parsedmarc/elasticsearck/kibana. So as I said it’s not
> a huge deal - but I would have thought that it was best practice to NOT send
> an agg report for emails sent TO your own RUA. This can be one end of a
> potential infinite loop yes ?
>
> target.com is the only org I get these from based on the agg’s I send them. I
> send plenty of agg reports to other orgs and they are quietly
> consumed/dropped/bounced etc.
> _______________________________________________
> mailop mailing list
> mailop@mailop.org
> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
_______________________________________________
mailop mailing list
mailop@mailop.org
https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
