They have explicit consent to send rfc compliant e-mail. Rfc-clueless.org seems.a good starting point.
Thank you -------- Original Message -------- On 1 Aug 2020, 15:53, Kevin A. McGrail < [email protected]> wrote: On Sat, Aug 1, 2020 at 8:59 AM Rupert Gallagher <[email protected]> wrote: Two well known companies in my country persist in making the mistake of writing their mid with a non-public fqdn, violating the rfc. It has been so for the past three years, with me sending detailed, manually written error messages to their painstakingly collected admin addresses. Their answer is that everybody else accepts their invalid mid, and their servers are enterprise ibm / microsoft shitware that they are unwilling to fix. Since we get a lot of their emails, I decided to scale up their problem. There are many blacklists, and I have no intention to go through each idiosyncratic procedure. Is there an ombusdman that superintends the major blacklists and enforces rfc compliance through them? First, I use Chris Santerre's definition of Spam that spam is about not having consent rather than the content. If someone sends something with RFC issues to evade spam detection, that demonstrates a lack of consent and clear intent. But if it's something with consent, as long as the email can get from point A to point B, bending the RFCs is fine. I'd equate it to a kid addressing an envelope to his Granny in crayon, forgetting the zip code and put the stamp on the wrong corner. The post office can figure it out automatically and it gets where it's meant to go. By comparison, the big bad Wolf trying to contact Granny from his jail cell would be spam. The RFC compliance might be an indicator for me but not a reason to block but that's my take. If you want to share a sample on pastebin, I can give you my take on it using the content vs consent litmus test for rules/blocking. Second, I'm not aware of any ombudsman for RBLs. Many RBLs are run by distinct organizations and many have unique listing/delisting criteria. An ombudsman would basically be a consultant spending a lot of time on the issue so you might just go that route and hire someone. Finally, there are RBLs you might want to use. There used to be RFC Ignorant but it appears to be shuttered. Take a look at http://rfc-clueless.org/ Also if they use the same domain, just locally block it. Regards, KAM
