Mark Rogers wrote:
Alex Tomlins wrote:
I'd second that...
I'm not sure about the IMAP idea. Something I like about dspam at
the moment is that it is a self-contained solution (that's most of
why I moved to it from spamassassin). If you start feeding stuff out
to IMAP servers etc, you end up with more external dependencies.
This seems to be a good argument against IMAP servers *AND* database
servers.
If anything, it's more likely that a typical mail server will have an
IMAP server already present than a database.
By database I was thinking whatever database backend dspam was using
(hash, mysql, postgres etc.), not specifically a RDBMS. While
implementing this it would make sense to put the user logs in there as
well. The advantage to doing this is that all the data for dspam would
be in one place as opposed to the current setup where some of it is in a
database, and some of it is on the filesystem.
Alex
--
Alex Tomlins
Email/Jabber: [EMAIL PROTECTED]
There are two kinds of people in the world: those who finish what they started.
