BTW, another question: when old entries are removed from IP cache, both ham and spam entries are deleted or only spam?
Only returning IP’s that were previously identified as spammer and who’s connection was terminated will update their last seen date in the caching system. Every day, once a day, a routine runs to remove the IP’s who’s last seen date is X amount of days older than the date the routine runs.
AFAIK, the SQL used deletes both spam and ham (avh-fdas.public.php, line 112):
$result = $wpdb->query($wpdb->prepare("DELETE FROM $wpdb->avhfdasipcache WHERE ((TO_DAYS(%s))-(TO_DAYS(added))) > %d", $date, $days));
Since cached spam entries are used to filter comments, shouldn’t they be remain in the cache?
Yeah the wording about the cache deleting is a little awkward. Every type of IP, ham and spam, is deleted.
The reason for deleting spam IP’s is because the IP’s can be declared as ham again by the 3rd party, and that could mean you block legit IP’s.
I haven’t build a Dashboard widget, regular widget or an option to show stats on a page/post. This could be implemented in a future release. A new release is scheduled as soon as I get my new development machine. (My old development machine died)
Thanks! About the stats, I’m showing them by myself (through SQL). But specific functions, along with a widget, would be way better!
I haven’t thought about the IP status being changed by the 3rd party… It makes sense. But, is the 3rd party access delay too big? I mean, to avoid blocking legit IP’s, shouldn’t the amount of days be minimum? What amount of days do you suggest?
