Dominic Raferd wrote
Do you have reason to think your system
is suffering heavy load as a result, or are you concerned that some of
the DNSBLs might block you for reaching commercial-use levels of
lookups?
On 05.03.19 13:50, Mayhem wrote:
No, but the problem seems to be getting worse this past year, and I was
looking for ways to further tackle the situation before it really got out of
hand. I figured giving the offending IP's a 24 hour timeout would be a nice
solution.
if an IP is blacklisted for an hour and delisted after that, blacklisting it
locally for another 23 hours seems not a good idea to me.
I also have nginx/apache and sql running on the same dedicated machine, I
just want to make sure that my mail server getting hammered won't eventually
have an adverse effect on those other running services.
I could think of locally maintained dnsbl with such sites, although it's
really uncertain whether it wouldn't make bigger load than just rechecking.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Spam is for losers who can't get business any other way.
