I am using Spam module along with Pressflow, and I'm heavily relying on Spam module to keep the site clean. However when I look at spam logs' blocked IPs, I see that it has blocked 127.0.0.1 hundreds of times. I think it is the cause that sometimes none of users' posts gets published.

So I am lookingo for a solution: Either to excempt 127.0.0.1 from being flagged, or at least lower the block time to something less thatn 1 hour.

Thanks

Comments

AlexisWilke’s picture

AlexisWilke commented
Category: task » support

The spam filter permissions are what I'd use in a situation where someone should never be hit by the filter.

However, what you are describing sounds like the duplicate spam filter detecting the same IP being used over and over again. I'd turn off the Duplicate filter, simply. You could also set the IP blacklist threshold to unlimited. Then only similar messages are detected as duplicates.

Thank you.
Alexis Wilke

marko3’s picture

marko3 commented

Alexis, I've defined a 'trustee' role just to keep safe trusted users from the filter, just as you suggested. So the problem occurs only for 'ordinary' users.

I changed the IP blocklist treshhold to unlimited but I exclusively use Coustom filter in admin/settings/spam/filters so I don't know the change would fix my problem, or there is any other solutions? Probalby a way to set 'Discard spam logs older than' to a time shorter than 1 hour?

Cheers

AlexisWilke’s picture

AlexisWilke commented

The Custom filters are different from the Duplicate filter... and I think that the problem you're experiencing is in link with the latter. There are no existing function to auto-discard the logs. Anyway, it would be done the other way around: do not take logs older than X in account.

Thank you.
Alexis Wilke

marko3’s picture

marko3 commented

Sorry, can you please elaborate on how to "do not take logs older than X in account."?

AlexisWilke’s picture

AlexisWilke commented

It's not implemented. If it were, that's how it would be.

marko3’s picture

marko3 commented

What about disabling the spam log altogether? Or at least reducing its minimum life cycle to some value closer to zero than one hour? Is either possible?

If neither is possible, what table should I truncate to get rid of the logs?

Thanks

AlexisWilke’s picture

AlexisWilke commented

Well... deleting the log itself doesn't change anything. Logs are there to help you determine what's going on.

Now, the different filters have tables that start with spam_... and those could indeed be truncated. At least some of them. But it would be preferable to first make sure that we determined which filter actually prevents the posts and not shrink the info to hastily.

For example, if the Bayesian filter is the problem, then there isn't much you can do because the Bayesian filter doesn't use any kind of time and it could make it much worse to randomly truncate that table.

Could you post some of those logs here? The logs should say which filter does what, more or less.

Thank you.
Alexis Wilke

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Issue summary: View changes
Status: Active » Closed (outdated)

I am closing this issue, since it's for a Drupal version no longer supported.