All, please do not reply to this message, as it's not on topic for
this thread and I don't want the thread to veer off.

Thanks,
Barry, as chair

On Thu, Jul 9, 2026 at 12:57 PM Dan Mahoney <[email protected]> wrote:
>
>
>
> > On Jul 6, 2026, at 6:56 AM, Isamu Koga <[email protected]> 
> > wrote:
> >
> >> I think we should NOT make ARC historic, yet.
> >>
> >> 1. ARC is actively deployed and utilized
> >> 2. No interoperable replacement is yet published
> >
> > I totally agree with Seth.
> >
> > It is too early to make ARC Historic at this point.  ARC may eventually be
> > deprecated, but no interoperable replacement exists today.  If a customer
> > were to ask what interoperable alternative is currently available, I would
> > not have a good answer.
>
> I get it, technology marches on, but...
>
> I am so tired of the "next great thing that's going to fix email that admins 
> of both sending servers and receivers alike need to figure out how to staple 
> in to their infrastructure even if it ignores some 
> edge-case-thats-not-an-edge-case-at-all."
>
> network-operators-actually-paying-attention-to-abuse@
> RBL's
> SPF with TXT records
> SPF with SPF RRTYPES
> No wait, SPF with TXT records (but not _spf.domain, let's continue to 
> overload the apex).
> MS Sender-ID with its wierd licensing requirements that no admin can agree to 
> without contacting Legal.
> Lets-put-a-haiku-in-your-headers and use that to assert copyright
> Hashcash
> The CAN-SPAM act
> Domainkeys
> DKIM
> DKIM-Reputation
> ADSP
> SenderScore
> SPEWS (and about 3 dozen other RBLs that will randomly return bad codes)
> DMARC
> DMARCbis
> ARC
> MTA-STS
> BIMI
>
> and...even if you do the right things according to the above, you can still 
> get delivery issues to $big_mailbox, which will have its own vague rules and 
> requirements.
>
> After which, someone can STILL put "Paypal Official Support" 
> <[email protected]> in their legitimate From header, fully signed, 
> and pretty much every MUA out there won't flag it (or even display it) 
> because that's "too confusing for the users", so either way mail admins are 
> forced to put forwarding-breaking WARNING: EXTERNAL ORGANIZAION mime bodies 
> in their mail.
>
> If you want operator burnout, this is the way.
>
> I'm sure the proponents of DKIM2 are going to be real proud of their new 
> sliced-bread machine when it comes out and totally solves everything, no this 
> time for real, but the time to deprecate ARC is *after* it's out, IMHO.  
> Maybe make it easier for admins to have a flag day to do both things?
>
> -Dan
> _______________________________________________
> dmarc mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
dmarc mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to