You don’t have to worry about it. The IPBlocklist code will only try to actually download a specific list if the frequency is matching. Each list has a defined frequency in the sources file.
So the Spamhaus_Edrop list has a 1 hr frequency and the Shodan list has a 1 day frequency.
IPBlocklist keeps a file for each selected list with a date/time code for when it was last updated.
So the Shodan list will be skipped until 1 day has passed from the last update. The message Skipping SHODAN blocklist - Too frequent update attempts!
means that the no attempt was made to download it, it was skipped.
Others are skipped because the file has not been updated since the last download.
The Spamhaus_edrop list no longer exists. The available file is an empty list. In mid April or so Spamhaus combined their Spamhaus_drop and Spamhaus_edrop lists into one list called Spamhaus_drop.
In CU186 the Spamhaus_edrop list will be removed from the system and if users had Spamhaus_edrop selected but not Spamhaus_drop then the Spamhaus_drop list will be selected for them.
The ipblocklist is very chatty (verbose) with log entries. I had thought about removing many of the above log entries. But I did not want to make changes to someone else’s code without permission.
@timf / @stevee - would it be OK to make a log change??
@bonnietwin Thank you so much for you reply, glad to hear it is nothing to worry about.
As per your information, I have also disabled Spamhuas_edrop and enabled Spamhause_drop.
Thank you again.