dspam daemon use flags for ebuild 3.6.6 could be improved. Daemon support requires one of mysql or pgsql, so why not make the ebuild check that instead of having the build proccess fail to tell us that? configure: error: daemon mode requires one of the following storage drivers: mysql_drv pgsql_drv
Ok, one aditional note, the check exists, but it should make the ebuild fail right on that check instead of having us to wait until the build process fails.
Yet another thing, and about daemon, although I might not choose to run in daemond mode, I still need to be able pass --enable-daemond so I can use lmtp delivery for example.
dspam does *not* require mysql and/or pgsql for running as a daemon, it can use its own default hashing method as well. Quoting README: *T hash_drv: None (Self-Contained Hash-Based Driver) Legend: * Default storage driver T Thread-safe (Required for running DSPAM in server daemon mode Now that method has issues ( this might be related to it -> http://article.gmane.org/gmane.mail.spam.dspam.devel/2458/ ) but that's a totally different bug/concern.
takeover the maintainership from st_lim.
The only requirement is to have a thread-safe driver, which I think most of them are (except maybe sqlite-2).
