Tommy Braun wrote: > >> What about user role? Is it possible to configure special actions, e.g. >> learn antispam ham/spam, set spam score, and similar? > > No, QUICA just supports managing Users. There is one > [EMAIL PROTECTED] account which can do everything - users might > login to their accounts only to change the password.
That is already available in Courier's native "Preferences" web page. >[...] > When it comes to Userbased-Antivir/Spam-Settings I think Maia > mailguard http://www.maiamailguard.com/ does something quite > interesting here, but of course this is not a courier-specific tool, > it operates on amavisd-new. The point with amavisd-new is that it has "Only one Bayes database for all users", as stated in http://www.maiamailguard.com/caveats.php IMHO that's not acceptable. Spammers are just now learning how to counteract Bayesian filters. Since such filters are not based on a theoretically sound ground, I don't think admins want to be blamed for their configuration. There has to be one database per user. > [...] > Also there are some open source panels out there here are just a few: > > http://www.vhffs.org/new/doku.php > http://syscp.org/ > http://vhcs.net/new/ > http://www.web-cp.net/ > http://chaogic.com/vhost/ > > find more here: > http://www.gplhost.com/software-dtc_9competitors.html Thanks for the pointers. > [...] > I think it would be good to focus on a small feature set - in your > case mail user administration - and use something to implement it, > that is easily extendable and brings most basic functionality > already... one of the rails-like web-frameworks could be a good start > - they bring all the nifty frontend stuff automagically and will help > to concentrate on a good backend, that detects manual changes (FAM) > and help admins to make things more easy, not more complicated. At the > moment I would favor django http://www.djangoproject.com/ for such a > thing, but, of course, the stack for nice projects I would like to do > is still much too big... Courier's design leaves users management entirely up to admins. That feature makes it easy to adopt any structure, from a couple of simple shell scripts to a fully fledged multilevel management system. For the web user interface, Courier's CGI has some interesting points: * It is acceptably secure. Sam has always been careful in avoiding vulnerabilities and webmail is no exception. * It is integrated in Courier. In case new features are added, e.g. for shared folders, webmail establishes a reference implementation of the client functions. * It is as usable as a web based mail client can be. Webmail already has almost all the stuff that a mail clients need. I'd like to find out how to inject some custom code into it, in order to add functionality for the end user. My (vague) idea is to have a shared library that exposes a few well defined callbacks. Webmail should load it and allow the callbacks to do their jobs. Anyone could then implement their own libraries, e.g. one for running PHP scripts, one for Python, etcetera. From a designer perspective, that's not much different than the way global filters currently plug in the SMTP module. From an admin perspective, it should then be easier to match the corresponding user management framework. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
