Bill, Even though this part wasn't the main purpose of the thread, that is still very helpful information. I will pass that along to my client so that they can hopefully fix their configuration problem with regards to their usage of URIBL.
Thanks! Rob McEwen Sent from my Verizon Motorola Droid On Oct 2, 2018 11:48 AM, Bill Cole <sausers-20150...@billmail.scconsult.com> wrote: > > On 2 Oct 2018, at 9:36, Rob McEwen wrote: > > > SIDE NOTE: I don't think there was any domain my message that was > > blacklisted on URIBL - so I can't explain the "URIBL_BLOCKED", but > > that only scored 0.001, so that was innocuous. I suspect that that > > rule is malfunctioning on their end, and then they changed the score > > to .001 - so just please ignore that for the purpose of this > > discussion. > > No, "URIBL_BLOCKED" means that the URIBL DNS returned a value that is > supposed to be a message to a mail admin that they are using URIBL wrong > and will nevewr get a useful answer without either (1) paying for a feed > to support their usage volume or (2) using their own recursive resolver > instead of forwarding queries to the likes of Google, OpenDNS, & > CloudFlare. > > A mail filtering system that gets URIBL_BLOCKED hits is broken. A mail > filtering system that gets them chronically is mismanaged.
