On Sat, Apr 15, 2023 at 1:40 PM Scott Kitterman
wrote:
>
>
> On April 15, 2023 8:17:41 PM UTC, John R Levine wrote:
> >> I'm assuming that the "long list of stinky possible workarounds" are
> the existing "whatever" mitigations, and rewriting seems to be acceptable
> enough as a mitigation to
On 4/15/2023 4:39 PM, Scott Kitterman wrote:
On April 15, 2023 8:17:41 PM UTC, John R Levine wrote:
I would like a pony, too. But ARC is as good as we have now and
after a decade of beating our heads against the wall, I don't think
we're going to find anything better. I've suggested a bunch
On April 15, 2023 8:17:41 PM UTC, John R Levine wrote:
>> I'm assuming that the "long list of stinky possible workarounds" are the
>> existing "whatever" mitigations, and rewriting seems to be acceptable enough
>> as a mitigation to convince large [enterprise] mail systems to move forward
I'm assuming that the "long list of stinky possible workarounds" are the
existing "whatever" mitigations, and rewriting seems to be acceptable
enough as a mitigation to convince large [enterprise] mail systems to
move forward with restrictive policies. ...
I think you are greatly
On Sat, Apr 15, 2023, at 12:07 PM, John Levine wrote:
> It appears that Jesse Thompson said:
> >Why not turn off rewriting on this list, as an experiment? The hypothesis is
> >that everyone will switch to Gmail and not tilt
> >at IETF, but instead they will tilt at their domain owners.
>
>
It appears that Jesse Thompson said:
>Why not turn off rewriting on this list, as an experiment? The hypothesis is
>that everyone will switch to Gmail and not tilt
>at IETF, but instead they will tilt at their domain owners.
That's how we got here. A lot of IETF participants use mail systems
