Fritz Borgstedt wrote: >> I think that 3 would make the most sense and be the easiest of the 3 >> to write, but they would still all be tough to implement. >> Actually, I had something a bit more simple in mind - and a (very) brief look at ASSP code seems like it wouldn't be a big deal to implement. In the filepath configuration section, add an option for "Treat paths as Maildirs". Then, in the locations where the logged mails are saved - based on that config setting - either use the default behaviour or (spam as an example) write to $spamlog/tmp, move to $spamlog/new - and have rebuildspamdb look to $spamlog/cur. I barely know enough about perl to write "hello, world!" - but looking at the code for ASSP gives lie to the belief that perl has to be unreadable.
Timeout here for a sincere compliment on the code used by the ASSP developers. I'm selfish. Just because it would be NICE to support every backend, doesn't mean we have to. I run Linux, I use maildir, ASSP already is designed to work with the mails as individual files in folders - looks like a simple add-on. For those who do not use maildirs - they don't have the option and continue to use the email-interface. > > It is not necessary to move files between the directories after the > first rebuild. > The email-interface is quite capable of adjusting the spamdb and the > error-folders are a quite nice longtime-memory. > This is true - and I do use the email-interface - but a folder management interface can be much easier for an administrator to utilize. -- Daniel ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
