You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ruleqa@spamassassin.apache.org by Tom Hendrikx <to...@whyscream.net> on 2025/05/11 21:21:15 UTC

Automasscheck, network tests and Validity

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

Re: Automasscheck, network tests and Validity

Posted by John Hardin <jh...@impsec.org>.
On Sun, 11 May 2025, 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.

Late to the party, but: Me Too, even though I've configured DNS to be 
recursive for those domains.

I disabled masscheck lookups the complaining providers; thankfully my spam 
corpora are pretty tiny.

I don't object to them being turned off by default.


-- 
  John Hardin KA7OHZ                    http://www.impsec.org/~jhardin/
  jhardin@impsec.org                         pgpk -a jhardin@impsec.org
  key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C  AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
   Are you a mildly tech-literate politico horrified by the level of
   ignorance demonstrated by lawmakers gearing up to regulate online
   technology they don't even begin to grasp? Cool. Now you have a
   tiny glimpse into a day in the life of a gun owner.   -- Sean Davis
-----------------------------------------------------------------------
  2 days until the 77th anniversary of Israel's independence

Re: Automasscheck, network tests and Validity

Posted by Tom Hendrikx <to...@whyscream.net>.
Hi Tobi (and Bill),

Thanks for your reply. Yes I use a recursing resolver, and I hope that 
every masscheck contributor is smart enough to do the same without being 
explicitly instructed to do so.

@Bill: (after reading your message on the users mailinglist) I wasn't 
annoyed, merely triggered by the error messages in the masscheck output.

My main concerns are (as you also state) the possible effect on 
masscheck results, and possible actions by Validity for me hitting the 
threshold every time masscheck runs. Also, I didn't want to adjust the 
masscheck configuration (by disabling the DNS queries for some rbls) 
without conferring with others to make sure that I render the results 
inconsistent by my actions.

Anyway, the change as proposed on the users list seems great. Thanks for 
taking a responsible decision.

Kind regards,
Tom

On 12-05-2025 07:56, Tobi wrote:
> 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


Re: Automasscheck, network tests and Validity

Posted by Tobi <ja...@gmx.ch>.
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