<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> <html> <head> <title>acua ban</title> </head> <body background=back.gif bgcolor=White link=Blue vlink=Black alink=Black> <h1>acua ban [-l] [-p] <expire> <login>|<phone_no></h1> <b>acua ban</b> bans a phone number or group of phone numbers.<br> <ul> <b>-l</b> - List all banned numbers.<br> <b>-p</b> - Prefix ban. All numbers beginning with the specified prefix will be banned.<br> <br> <b><expire></b> - An expiry date for the ban. The same syntax and rules apply to <expire> here as in <a href="acua_addRec.html">acua addRec</a> and others.<br> <br> <b><login></b> - Ban a specific user. The specified user will be kicked off of the system immediately (if they are on), their account deleted, and their phone number banned. <b><i>Extreme prejudice!</i></b><br> <br> <b><phone_no></b> - Ban a phone number. No new user will be permitted to use this number when creating an account with <a href="acua_verify.html">acua_verify</a>.<br> </ul> The <b>first</b> thing you should do if you plan to use call-back verification is to ban local phone numbers with a series of commands such as: <ul> <b>acua ban</b> -p 0 (don't bother telco operators)<br> <b>acua ban</b> -p 1 (prevent long distance calls)<br> <b>acua ban</b> -p 911 (<b><i>definitely</i></b> don't bother <b>9-1-1</b> operators)<br> <b>acua ban</b> <b><police dept. #></b><br> <b>acua ban</b> <b><fire dept. #></b><br> </ul> Of course, you won't be able to get them all... This is the draw-back of call-back verification -- there is no way to totally prevent malicious people from abusing it.<br> <br> <br> <hr size=5> <address><a href="mailto:acua@acua.ebbs.com.au">Robert Davidson</a></address> </body> </html>
