Re: [dmarc-ietf] Minutes from IETF 112

2021-11-30 Thread Jesse Thompson
On 11/18/2021 1:44 PM, John Levine wrote: > It appears that Todd Herr said: >> It seems to me that DMARC already provides the ability for >> security.example.edu to ensure that no other part of example.edu can send >> mail on their behalf. To accomplish this, security.example.edu can today: >> >>

Re: [dmarc-ietf] Reversing modifications from mailing lists

2021-11-30 Thread Scott Kitterman
On November 30, 2021 5:30:39 PM UTC, John R Levine wrote: >On Tue, 30 Nov 2021, Wei Chuang wrote: >> What about adding a footer to some html mime part is poorly handled when >> using "l="? Multipart bodies could be handled by other techniques. > >See section 8.2 in the DKIM spec which says if

Re: [dmarc-ietf] Reversing modifications from mailing lists

2021-11-30 Thread John R Levine
On Tue, 30 Nov 2021, Wei Chuang wrote: What about adding a footer to some html mime part is poorly handled when using "l="? Multipart bodies could be handled by other techniques. See section 8.2 in the DKIM spec which says if you use l= you need to be careful with your MIME boundaries so naug

Re: [dmarc-ietf] Reversing modifications from mailing lists

2021-11-30 Thread Alessandro Vesely
On Mon 29/Nov/2021 15:17:45 +0100 John R Levine wrote: On Mon 29/Nov/2021 04:03:57 +0100 John Levine wrote: This was part of the discussion about what sort of body modifications to allow. We ended up with optionally ignoring white space changes, and l= to ignore added text. My impression is that