> >Nope, nothing wrong with the config. I've intentionally set it to 3 months. > > Really a bad idea, ime. The algorithm should attack fast, maintain the > block continuously as long as the IP repeatedly connects, and then release > the block when an IP goes quiet for an hour max.
Unfortunately the program doesn't have the ability to perform smart blocking in this way Len. Besides, I thought you hated Subscriber Nets :) > >BI just doesn't seem to be able to handle a large(ish) firewall.ini file. > >99.9% of the entries in this file are subscriber networks and don't deserve > >a generous block of only an hour. :) > > But there are increasingly millions of those IPs worldwide. Holding them > for 3 months will make the IP database way too big. If the IPs are stored > a text file, the text file will be too large on disk for read/add/delete, > and the in-memory db will be enormous. You're right. This is exactly the problem experienced. We would like to implement IMGate to counter these limitations of BI/Windows, but we have a few design type issues that I think are preventing us from moving forward. Our users connect via external networks (VISP) to check their mail / send mail. Currently the mail clients are set to mail.areatech.com for POP3 and SMTP. Wouldn't we have to change this setup before we implemented IMGate as a solution? Thanks, Jason To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
