Tom, Same here: as per 1st May Validity made some huge changes related to the allowed access volumes by free-tier accounts. I had a free account before and did not have issues but since 1st May it's getting much worse. Think it's a good idea if the SA project brings this up to Validity and see if they could offer something for masscheckers.
Just one thing @Tom: do you use your own recursing resolver or one of your ISP-provider or even worse a huge public one like Google or Quad- 9? It's important to use your own dedicated resolver for such queries, fully recursive and not just forward queries to another resolver. But anyway I can confirm that even with a dedicated recursive resolver I cannot process my corpus without tons of Validity issues. Thinking about removing them completely from my masschecks and my SA instances. Have a good one and happy spam catching tobi On Sun, 2025-05-11 at 23:21 +0200, Tom Hendrikx wrote: > Hi, > > I'm running masschecks for RuleQA, and since last week, the network > checks enabled run on Saturday started complaining about the Validity > RBL checks being blocked. This is of course related to the passing of > the May 1st deadline that they set. > > I signed up for an account with Validity, but even my modest volume > of > corpus messages triggers their limits. The machine/account running > masschecks does not even access the Validity services for regular > mail > traffic, this is only masscheck workload. > > How do/can we handle this? I'm not sure about the effect of this > issue > for the masscheck results. Is it okay that I disable the Validity > rules > in the masschecks process? > > Or would it be an idea to bring this up with Validity, to see if they > can support SA volunteers with (free) larger quota? This would be a > nice > thing for them to do if they have any interest in keeping the > Validity > rules in the default SA ruleset. > > > Kind regards, > > Tom
