Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-31 Thread Alessandro Vesely
On Wed 30/Dec/2020 22:17:47 +0100 John R Levine wrote: On Fri, 4 Dec 2020, John Levine wrote: In article <0408ae98-e1c1-71fe-fdd4-8bc7a7c15...@tana.it> you write: We would like to close this ticket by Dec 18, two weeks from now, so please get on it. The ticket originated from John's comment,

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-30 Thread John R Levine
On Fri, 4 Dec 2020, John Levine wrote: In article <0408ae98-e1c1-71fe-fdd4-8bc7a7c15...@tana.it> you write: We would like to close this ticket by Dec 18, two weeks from now, so please get on it. The ticket originated from John's comment, in May 2019: Apropos recent discussions, we could

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-18 Thread Alessandro Vesely
On Wed 09/Dec/2020 18:22:04 +0100 Dave Crocker wrote: On 12/9/2020 7:23 AM, John R Levine wrote: No.  This is not a problem.  There is nothing to fix.  Please close this ticket. +1 Fair enough. Ticket closed. Best Ale -- ___

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-09 Thread Dave Crocker
On 12/9/2020 7:23 AM, John R Levine wrote: No.  This is not a problem.  There is nothing to fix.  Please close this ticket. +1 d/ -- Dave Crocker dcroc...@gmail.com 408.329.0791 Volunteer, Silicon Valley Chapter American Red Cross dave.crock...@redcross.org

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-09 Thread John R Levine
On Wed, 9 Dec 2020, Alessandro Vesely wrote: It seems better than the other three bullets, so I'd prepend it. Does the WG agree? No. This is not a problem. There is nothing to fix. Please close this ticket. Regards, John Levine, jo...@taugh.com, Taughannock Networks, Trumansburg NY

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-09 Thread Alessandro Vesely
On Wed 09/Dec/2020 01:04:46 +0100 John Levine wrote: In article <62b7d80e-2c39-4d02-0b5a-bd6ede7d5...@tana.it> you write: When dmarc authentication method fails on a message, an MTA may decide to send a failure report. If the message is itself a failure report, however, no failure report

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-08 Thread John Levine
In article <62b7d80e-2c39-4d02-0b5a-bd6ede7d5...@tana.it> you write: >When dmarc authentication method fails on a message, an MTA may decide to send >a failure report. If the message is itself a failure report, however, no >failure report should be sent. The question is, how does the MTA

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-08 Thread Alessandro Vesely
On Mon 07/Dec/2020 20:51:12 +0100 John Levine wrote: In article , Alessandro Vesely wrote: 4. Some explicit loop prevention specification may be added. For example: 4.1. send reports from a subdomain having a DMARC record without ruf=, or 4.2. never send failure reports about failed

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-07 Thread John Levine
In article <0408ae98-e1c1-71fe-fdd4-8bc7a7c15...@tana.it> you write: >We would like to close this ticket by Dec 18, two weeks from now, so please >get >on it. > >The ticket originated from John's comment, in May 2019: > > Apropos recent discussions, we could recommend that failure reports be

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-07 Thread Alessandro Vesely
On Mon 07/Dec/2020 08:15:57 +0100 Murray S. Kucherawy wrote: On Fri, Dec 4, 2020 at 3:10 AM Alessandro Vesely wrote: We would like to close this ticket by Dec 18, two weeks from now, so please get on it. The ticket originated from John's comment, in May 2019: Apropos recent

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-06 Thread Murray S. Kucherawy
On Fri, Dec 4, 2020 at 3:10 AM Alessandro Vesely wrote: > We would like to close this ticket by Dec 18, two weeks from now, so > please get > on it. > > The ticket originated from John's comment, in May 2019: > > Apropos recent discussions, we could recommend that failure reports be >

Re: [dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-04 Thread John Levine
In article <0408ae98-e1c1-71fe-fdd4-8bc7a7c15...@tana.it> you write: >We would like to close this ticket by Dec 18, two weeks from now, so please >get >on it. > >The ticket originated from John's comment, in May 2019: > > Apropos recent discussions, we could recommend that failure reports be

[dmarc-ietf] Ticket #28 - Failure report mail loops

2020-12-04 Thread Alessandro Vesely
We would like to close this ticket by Dec 18, two weeks from now, so please get on it. The ticket originated from John's comment, in May 2019: Apropos recent discussions, we could recommend that failure reports be rate limited per recipient both to break loops and to deter indirect