Using user_deny.db

We have many recalcitrant, bad, accounts constantly checking IMAP, long 
after the student has graduated.  I would like to use user_deny.db to 
simply tell them to go away.

First, would this offer an advantage?  That is, does "login" check 
user_deny.db before authenticating, or after?

Second, any examples of how to use cyr_dbtool (or other tool) to put 
entries into user_deny.db?

Finally, my reading of the documentation (2.4.17/18) is that 
user_deny.db is a flat file by default, so I will need to set 
userdeny_db to something like skiplist, or berkeley, etc.  Any 
suggestions on a good choice assuming the list could grow to a few 
thousand?  Any documentation on the sql option?

Thank You,

Mike
-- 
Michael D. Sofka               [email protected]
ITI Sr. Systems Programmer,   Email, TeX, Epistemology
Rensselaer Polytechnic Institute, Troy, NY.  http://www.rpi.edu/~sofkam/
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus