Re: [dmarc-ietf] DMARC forensic reports (ruf=) and privacy

2019-01-28 Thread John Levine
In article you write: >sending a notification, when DMARC does not match is comparable to sending a >notification/feedback loop, when a user >clicks a message as spam. No, it isn't. When the user clicks the spam button, she has taken a specific step to notify someone about the message. DMARC f

[dmarc-ietf] I-D Action: draft-ietf-dmarc-rfc7601bis-06.txt

2019-01-28 Thread internet-drafts
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Domain-based Message Authentication, Reporting & Conformance WG of the IETF. Title : Message Header Field for Indicating Message Authentication Status Auth

[dmarc-ietf] Protocol Action: 'Message Header Field for Indicating Message Authentication Status' to Proposed Standard (draft-ietf-dmarc-rfc7601bis-05.txt)

2019-01-28 Thread The IESG
The IESG has approved the following document: - 'Message Header Field for Indicating Message Authentication Status' (draft-ietf-dmarc-rfc7601bis-05.txt) as Proposed Standard This document is the product of the Domain-based Message Authentication, Reporting & Conformance Working Group. The IESG

Re: [dmarc-ietf] DMARC forensic reports (ruf=) and privacy

2019-01-28 Thread Дилян Палаузов
Hello, sending a notification, when DMARC does not match is comparable to sending a notification/feedback loop, when a user clicks a message as spam. In practice, when a company owns two labels, that were distinct companies in the past, for the one label the new company sends in the feedback lo

Re: [dmarc-ietf] DMARC forensic reports (ruf=) and privacy

2019-01-28 Thread Alessandro Vesely
On Sat 26/Jan/2019 18:21:28 +0100 Дилян Палаузов wrote: > Imagine there is a failure report stating that after a direct communication > between your server and another server, the receiving server sends you an > aggregate report, stating that 1% of the messages you sent yesterday do not > validate