Am Fri, 09 Feb 2024 22:09:45 -0800 schrieb Hal Murray via mailop <[email protected]>:
> I expect that there would be a protocol to handle it. I can't be the > only one who has thought of this. After a handshke to set things up, > the sender adds a forwarding header and the receiver verifies that a > forwarded message is coming from an allowed IP Address then bypasses > spam checking for that message. (but not phish/malware checking???) Bypassing spam checking would make spammers use exactly that way to send spam. SPF can't be verified except the sender connect to you. A forwarder can forge everything here, so you can't rely on the oter Received: headers. DKIM can be checked and will pass if the message isn't altered. SPF won't and depending on the DMARC policy, it will be rejected if MAIL FROM is another domain. The sender domain can decide about that. If they want that everybody can send with their name, they can have +all in their SPF. > Is there a technical reason why something like that doesn't work? Or > some economic/policical reason why too many key players aren't > interested? SPF and DKIM provide a way to make forging of messages a bit harder. Providers like Google want to implement them and DON'T CARE about the disadvantages. They don't care about mailing lists and forwardings. Their web interface isn't intended to be used on mailing lists. They prefer that everybody uses Gmail and don't run their own mail infrastructure. The harder that is, the more people will stop doing that. _______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
