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

2021-05-02 Thread Douglas Foster
John, your logic is circular. The only way that Matthäus can know if he objects to what you are doing with his message is to monitor what you are doing with his message. It is also irrelevant. Data privacy is pretty thoroughly lost, notwithstanding GDMR's efforts to fight the system. It seems

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

2021-05-02 Thread John Levine
It appears that Matthäus Wander said: >envelope_to allows you to automatically correlate these reports and >reconstruct the forwarding path. This helps to identify the culprit who >is breaking DKIM signatures, especially with longer forwarding chains. >Without envelope_to, reconstructing the mail

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

2021-05-02 Thread Matthäus Wander
I see the following use cases for the envelope_to. Case 1: Identify mail flows along forwarders. With an increased adoption of DMARC reporting, we will be getting reports like this: Report from $ForwarderOrg: HeaderFrom=$OriginDomain + EnvFrom=$OriginDomain --> $ForwarderOrg Report from

[dmarc-ietf] Messages from the dmarc list for the week ending Sun May 2 06:00:06 2021

2021-05-02 Thread John Levine
Count| Bytes | Who ++--- 3 (33.3%) | 40393 (36.3%) | Todd Herr 3 (33.3%) | 32265 (29.0%) | Douglas Foster 1 (11.1%) | 30814 (27.7%) | Brotman, Alex 1 (11.1%) | 4937 ( 4.4%) | Matthäus Wander 1 (11.1%) | 2852 ( 2.6%) | John