> On Apr 23, 2023, at 4:17 PM, Dotzero wrote:
>
> On Sun, Apr 23, 2023 at 1:20 PM Hector Santos
> mailto:40isdg@dmarc.ietf.org>> wrote:
>>
>> With each year, that "temporary hack" becomes the new normal and it
>> will be harder to clean up. It is not the right way and I don't its
>>
On Sun, Apr 23, 2023 at 1:20 PM Hector Santos wrote:
> On 4/23/2023 6:10 AM, Alessandro Vesely wrote:
> >
> > Meanwhile, digressions about ATPS and similar schemes can help
> > casting some light on future evolution. From: rewriting cannot be
> > the final solution; it is a temporary hack.
On 4/23/2023 6:10 AM, Alessandro Vesely wrote:
Meanwhile, digressions about ATPS and similar schemes can help
casting some light on future evolution. From: rewriting cannot be
the final solution; it is a temporary hack. Digressions don't slow
down the publication, as discussions about
NOTE: This thread is clearly off-topic with respect to publication. Yet, it
may help convergence toward a community vision of the possible future of DMARC,
which, in turn, can help finding out a statement about today's limits of DMARC,
its interoperability damage, and From: rewriting.
On
On Fri 21/Apr/2023 18:43:30 +0200 Scott Kitterman wrote:
On April 21, 2023 3:57:54 PM UTC, Alessandro Vesely wrote:
On Fri 21/Apr/2023 05:41:03 +0200 Scott Kitterman wrote:
On April 20, 2023 4:18:08 PM UTC, Dotzero wrote:
On Thu, Apr 20, 2023 at 11:38 AM John Levine wrote:
It appears that
Count| Bytes | Who
++---
74 ( 100%) | 827411 ( 100%) | Total
16 (21.6%) | 249185 (30.1%) | Hector Santos
10 (13.5%) | 160009 (19.3%) | Douglas Foster
8 (10.8%) | 49381 ( 6.0%) | Alessandro Vesely
8 (10.8%) | 47318 ( 5.7%) | John Levine
