Re: All RCVD_IN_VALIDITY rules being applied to every email.

On 20 Nov 2024, Andy Smith uttered the following:

> Hi,
>
> On Wed, Nov 20, 2024 at 05:07:09PM +0000, Nix wrote:
>> > From https://knowledge.validity.com/s/articles/Accessing-Validity-reputation-data-through-DNS :
>> 
>> Tried registering here. I can register a v4 address, but every format of
>> v6 CIDR I've tried reports "Invalid V6_CIDR" with (of course) no
>
> I experienced the same a couple of months ago and reported it to them.
> Their response after several weeks was:
>
>     "I investigated this with our engineering team. We currently don't
>     support IPV6 in the on the my validity/ zone file registration page.
>     Our product team is working to remove IPV6 as option.
>
>     Currently only IPV4 single and IPV4 range are supported. I apologize
>     for any confusion."
>
> I see they haven't got around to removing the IPv6 features that they
> consider a mistake yet then.
>
> (They don't have IPv6 addresses on their nameservers so currently there
> is no point supplying your IPv6 netblocks in any case. You're not
> missing out.)

Oh right. I never even considered *checking* that. Of course they've got
IPv6 addresses, who hasn't who's running a server for high-volume public
use?

... most of the more stick-in-the-mud corners of the Internet, it turns
out.

> More here:
>
>     https://www.mail-archive.com/[email protected]/msg23456.html

Wow, that thread is eye-opening. Fairly hilarious DNS management, I must
say...

> Their web site only half works. They were unable / unwilling to explain
> to me how they have calculated that I have exceeded their limits when
> I'm almost certain that I haven't. I find their corporate web site to be
> difficult to understand regarding what they actually do or sell. But
> their DNS lists *are* free so there is a limit to what one can expect. I
> don't have a lot of confidence that they will continue to exist as a
> company.

Indeed not.

> I don't think they should be in default SpamAssassin and if I experience
> any more problems with them then I'm going to disable lookups.

Ditto.

-- 
NULL && (void)