On March 15, 2023 10:50:58 AM UTC, Alessandro Vesely wrote:
>On Tue 14/Mar/2023 23:50:13 +0100 Scott Kitterman wrote:
>> On March 14, 2023 10:41:12 PM UTC, Steven M Jones wrote:
>>> On 3/14/23 13:18, Scott Kitterman wrote:
My expectation is that if you were able to contact the people who
On Tue 14/Mar/2023 23:50:13 +0100 Scott Kitterman wrote:
On March 14, 2023 10:41:12 PM UTC, Steven M Jones wrote:
On 3/14/23 13:18, Scott Kitterman wrote:
My expectation is that if you were able to contact the people who made that
decision, they'd say they did it because they want
On March 14, 2023 10:41:12 PM UTC, Steven M Jones wrote:
>On 3/14/23 13:18, Scott Kitterman wrote:
>> My expectation is that if you were able to contact the people who made that
>> decision, they'd say they did it because they want information on DMARC
>> failures, which is not what DMARC
On 3/14/23 13:18, Scott Kitterman wrote:
My expectation is that if you were able to contact the people who made that
decision, they'd say they did it because they want information on DMARC
failures, which is not what DMARC failure reports give you. They provide
details on messages which fail
On March 14, 2023 7:41:47 PM UTC, Steven M Jones wrote:
>On 3/12/23 07:50, John Levine wrote:
>>
>> It also occurs to me that anyone who sends failure reports also sends
>> aggregate reports, so if you care, you have a way to find out.
>
>
>This made me wonder if everybody requesting failure
On 3/12/23 07:50, John Levine wrote:
It also occurs to me that anyone who sends failure reports also sends
aggregate reports, so if you care, you have a way to find out.
This made me wonder if everybody requesting failure reports also
requests aggregate reports, so I took a look at the data
It appears that Scott Kitterman said:
>I don't think it's needed. My understanding is that failure reports aren't
>typically used as an aid to troubleshooting DMARC failures. The aggregate
>reports are sufficient for that. The failure reports have other information
>that's useful for other
On Friday, March 10, 2023 6:12:45 PM EST Steven M Jones wrote:
> On 3/10/23 3:08 AM, Alessandro Vesely wrote:
> > although I'm back as an editor of the failure reporting I-D, that file
> > is almost final and I can't think of anything to be discussed live
> > about it. I haven't registered for
On 3/10/23 3:08 AM, Alessandro Vesely wrote:
although I'm back as an editor of the failure reporting I-D, that file
is almost final and I can't think of anything to be discussed live
about it. I haven't registered for 116.
Off the top of my head, and in light of the aggregate reports
