recently updated to 4.0.2

I recently upgraded (did not change my local.cf) and had yesterday spamassassin not functional in a container environment. Getting " Milter (spamassassin): timeout before data read, where=eom"

I wonder what is causing this. I also noticed these. I don't really know if these are new or if something changes because all the digs return blocked (I think)

[185.182.56.42 listed in bl.score.senderscore.com]\n  0.0 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED RBL: ADMINISTRATOR NOTICE: The\n                             query to Validity was blocked.  See\n



[@temp9]$ dig +short  @192.168.122.14 42.56.182.185.bl.score.senderscore.com
127.255.255.255
[@o1 temp9]$ dig +short  @192.168.122.14 42.56.182.185.sa-trusted.bondedsender.org
127.255.255.255
[@ temp9]$ dig +short  @192.168.122.14 42.56.182.185.sa-accredit.habeas.com
127.255.255.255

I am not processing that much mail so I am even wondering if these queries are indeed blocked, and why is this default on in spamassassin, especially when this can cause disruption.

Currently added these configs.

# disables only the Validity/ReturnPath/SenderScore DNSBL lookups
ifplugin Mail::SpamAssassin::Plugin::DNSEval
  rbl_validity NONE
endif

# Disable some uribl
score   RCVD_IN_DNSWL_NONE      0
score   RCVD_IN_DNSWL_LOW       0
score   RCVD_IN_DNSWL_MED       0
score   RCVD_IN_DNSWL_HIGH      0