On Wed 12/Feb/2025 21:44:48 +0100 John Levine via mailop wrote:
It appears that Niels Kobschätzki via mailop <ni...@kobschaetzki.net> said:
Hello,
I have encountered the first time apparently the problem that I have a user who
forwards mails to another mail-server and a forwarded
mail got rejected because of the dmarc-policy of the original senders domain.
I am using SRS and my understanding is that ARC should solve the problem since
DMARC breaks SRS and the solution for that is ARC.
Now my question: if I implement ARC, what do I do with a mail that is forwarded?
a) I use always SRS and ARC to sign/seal the message when I forward
b) I only use ARC and no SRS when the original senders domain has a
dmarc-policy (so I need to check that before forwarding)
If you use it at all, sign and seal everything you forward. That's what I do.
Isn't it redundant to sign and seal? I mean, if you know the receiver supports
ARC.
Also: does anyone have an idea when the ARC-RFC is finalized? From what I’ve seen
it is marked as experimental for like 6 years now?>
Probably never. ARC has found some use internally at large mail systems but
the fact
that for it to be useful you still need to keep a list of trusted forwarders
means
it's not going to solve the problem we hoped it would solve.
Unless there's a way to automate keeping such lists.
Best
Ale
--
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
