Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports

2020-10-22 Thread Brotman, Alex
-- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast From: Dotzero Sent: Thursday, October 22, 2020 7:37 AM To: Brotman, Alex Cc: dmarc@ietf.org Subject: Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports On Wed, Oct 14, 2020 at 2:17 PM Brotman, Alex ma

Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports

2020-10-22 Thread Dotzero
On Wed, Oct 14, 2020 at 2:17 PM Brotman, Alex wrote: > During a session at M3AAWG50, one of the other participants proposed an > idea where a sender could optionally send reports to a domain holder when > they send messages on behalf of that domain. > > Let's consider the idea that example.com ha

Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports

2020-10-19 Thread Brotman, Alex
-- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast > -Original Message- > From: Jesse Thompson > Sent: Monday, October 19, 2020 9:51 AM > To: Brotman, Alex ; dmarc@ietf.org > Subject: Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports >

Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports

2020-10-19 Thread Jesse Thompson
On 10/19/20 7:17 AM, Brotman, Alex wrote: > Sure, I think Masaki Kase is suggesting roughly the same thing (along with IP > address). Tell the domain who is the entity responsible for attempting this > delivery? This might need to be a hash of some sort. > I think this sort of data would benef

Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports

2020-10-19 Thread Brotman, Alex
I think that could be reasonable. It could make reports noisy though? -- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast From: dmarc On Behalf Of Masaki Kase Sent: Thursday, October 15, 2020 7:34 PM To: Brotman, Alex Cc: dmarc@ietf.org Subject: Re: [dmarc-ietf] Thought

Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports

2020-10-19 Thread Brotman, Alex
-- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast > -Original Message- > From: dmarc On Behalf Of Jesse Thompson > Sent: Wednesday, October 14, 2020 6:59 PM > To: dmarc@ietf.org > Subject: Re: [dmarc-ietf] Thoughts on "Senders DMARC" Re

Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports

2020-10-15 Thread Masaki Kase
Hello Alex, > This would not be meant just for ESPs, but also for MBPs/ISPs as well. > > Does this sound like a reasonable idea? Report overload? Not a helpful data > set for a domain holder? With the perspective of MBPs, I imagined these 3 things: (a) Identify the E/U’s IP address The MBPs

Re: [dmarc-ietf] Thoughts on "Senders DMARC" Reports

2020-10-14 Thread Jesse Thompson
On 10/14/20 1:17 PM, Brotman, Alex wrote: > During a session at M3AAWG50, one of the other participants proposed an idea > where a sender could optionally send reports to a domain holder when they > send messages on behalf of that domain. > > Let's consider the idea that example.com has properly

[dmarc-ietf] Thoughts on "Senders DMARC" Reports

2020-10-14 Thread Brotman, Alex
During a session at M3AAWG50, one of the other participants proposed an idea where a sender could optionally send reports to a domain holder when they send messages on behalf of that domain. Let's consider the idea that example.com has properly created SPF/DKIM/DMARC reports for themselves, and