Sujet : Re: Forwarding problem with aliases
De : gtaylor (at) *nospam* tnetconsulting.net (Grant Taylor)
Groupes : comp.mail.sendmailDate : 26. Oct 2024, 17:32:47
Autres entêtes
Organisation : TNet Consulting
Message-ID : <vfj5jf$alk$1@tncsrv09.home.tnetconsulting.net>
References : 1 2 3 4
User-Agent : Mozilla Thunderbird
On 9/6/24 03:59, Marco Moock wrote:
It is a experimental standard that is pushed by the big companies. It will also help them because they trust big ones, but I dunno how ARC will be handled that comes from small sites. I assume this will be the next bullying mechanism.
IMHO ARC had a priming problem. It's neigh impossible to get others to trust you or your ARC signature. So if not enough people are benefiting from it, fewer people are inclined to start using it.
SPF breaks forwarders, by design.
IMHO, as it should.
DMARC is a policy how to handle stuff that doesn't pass DKIM/SPF and regulates alignment. Some big companies made SPF and DMARC mandatory which will make forwarders and mailing lists a PITA.
I disagree.
TLDR: In times of SPF and DMARC, forwarding doesn't work like before. My recommendation: Avoid it whenever possible.
I've found that Sender Rewrite Scheme (SRS) has been remarkably effective when forwarding to Gmail.
SRS is also perfectly compatible with mailing lists. Though admittedly I'd hope that contemporary mailing list managers were using VERP to be able to correlate bounces with subscriber addresses. Bonus points if they also use SMTP's RCPT verb's optional ORCPT parameter.
-- Grant. . . .