[dmarc-ietf] Recipient domain in aggregate reports (#23)

2021-04-28 Thread Matthäus Wander
Hello everyone, I'm new to the party. I'd like to bring in some practical experience of working with DMARC rua reports. #23 introduces "receiving_domains" in the report metadata, justified by large infrastructures that host a large number of domains (e.g. Google). I think, this information would

Re: [dmarc-ietf] Recipient domain in aggregate reports (#23)

2021-04-28 Thread Todd Herr
Apologies to Matt; I sent this originally only to him when I meant to send it to the list... On Wed, Apr 28, 2021 at 4:27 AM Matthäus Wander wrote: > Hello everyone, > > I'm new to the party. I'd like to bring in some practical experience of > working with DMARC rua reports. > > #23 introduces "

Re: [dmarc-ietf] Recipient domain in aggregate reports (#23)

2021-04-28 Thread Brotman, Alex
Matt, While, yes, there is the existing envelope_to, there was a request to add this to the report format (which I believe I did as the submitter desired). I would assume we’d hash it out on the list and remove one of them. However, from an operator side of things, I tend to align with Todd on

Re: [dmarc-ietf] Recipient domain in aggregate reports (#23)

2021-04-28 Thread Douglas Foster
I understand that additional detail might make the reporting effort unacceptable to the big organizations that are creating them, and this reason alone may prevent alternatives. It seems that the potential uses for reports are: - Identifying and fixing my own infrastructure problems - Celebrating