On Wed, 28 Apr 2004, Scott Russell wrote: > I would be interested to hear more about the spam/ham training folders. > How do you (or others) keep users from deleting them, for example? It > seems a per-user folder solution would be the most intuitive, for both > the user and the client interface.
The way I'd envision integrating DSPAM is that the spam/ham folders would be virtual (users might not even be able to open them -- they just have them as "targets" for filing). Thus, they can't be deleted or changed in any way. > I assume a script solution would look something like this and run say > once every other hour or so. > > 1) get a list of users > 2) check for is-spam folder > 3) feed any contents of is-spam folder into bayes db for $user > 4) remove contents of is-spam folder > 5) repeat steps 2-4 for the is-not-spam folder > 6) move on to next $user Seems reasonable for a scripted solution -- however, libdspam provides a C API that could allow for *much* tighter integration of the two products. -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
