> So that makes it unusable for dial up connections. > Still can be useful for our wireless clients, those are assigned fixed IPs. > But we will have to "hijack white list" all the Dial up IPs, correct ?
No, it makes it still usable for dial up connections. If user A sends out enough messages to trigger HOLD2, the IP is held. (You need to have a script running to check HOLD2 and notify.) You need it to stay held until you know what is going on. If User A then disconnects, reconnects and gets a different IP, so what. You go back to your logs, see why that IP was held, look to see who was using that IP at the time, and nail them, or convince them to use a list service if legit. Remember, and IP caught by HOLD2 means something is not right and against your policy, so you need to take action to investigate. John Tolmachoff Engineer/Consultant/Owner eServices For You --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
