I did create this a while ago. https://datatracker.ietf.org/doc/draft-brotman-srds/
This would allow the MTA doing the sending to see that it will go to the spam folder. I’ve created initial code to support this, but haven’t yet deployed it. -- Alex Brotman Sr. Engineer, Anti-Abuse & Messaging Policy Comcast From: mailop <mailop-boun...@mailop.org> On Behalf Of Scott Mutter via mailop Sent: Monday, January 29, 2024 12:44 AM To: mailop@mailop.org Subject: [EXTERNAL] Re: [mailop] Spamfolder mini rant (Was: Contact Google Postmaster) What if the receiving mail server tagged the message in some way in their final acknowledgement of the message. For Google. instead of: 250 2.0.0 OK 1706409809 h4-20020ac85844000000b10427e71c979dsi9837397zyh.449 - gsmtp If the message is redirected to the user's spambox, the message could be: 250 2.0.0 OK 1706409809 h4-20020ac85844000000b10427e71c979dsi9837397zyh.449-spam - gsmtp Or provide some number attached to the ID that identifies how much spamminess the receiving mail server thinks the message is. This would at least give a tool for the sending server to know if the messages being sent out of their server are being flagged as spam. I get that it's a thin line between offering this information and that information being abused by spammers to circumvent the receiving server's anti-spam measures. But there's also no judicial system or oversight in making these determinations. The receiving server gets to be judge, jury, and executioner when it comes to making these determinations. And because these email service providers are "too-big-to-fail" it's never their fault for being overzealous with their blocking or weighing scale. They can block whoever they want, whenever they want, with no explanation at all.
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
