[Pkg-dspam-misc] Bug#418736: dspam: New upstream release (3.8.0) available

[Daniel Kahn Gillmor]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun 2007-04-15 10:21:38 -0400, Matthijs Mohlmann wrote:

> I have a few production environments where I can test it. But I'll
> set it up first in a test environment. I can run some automated
> tests with the test environment.

That would be great!  what sort of automated tests do you have in
mind?

> What kind of configurations do you think about especially ?
> Currently I use:
>
> postfix - dspam - cyrus

I use this as well.  not daemonized, either, and with the hash driver.

> In other words, I use it as a delivery proxy. I am pretty
> comfortable with that configuration, but I can understand that
> someone needs another type of configuration. Probably we should
> support most of them.

sigh.  as long as they have a chance of being supported upstream.  I
don't know that i'm prepared to support something like dspam's LMTP
implementation, which has had several well-defined problems reported
(leading . duplication, line length, etc) without a clear response
from upstream on dspam-dev, afaict.

> According to the documentation (README) there are 3 major configurations
> possible:
> - delivery agent proxy
> - pop3 proxy
> - smtp relay
>
> I think we should support those configurations.

i've never even tried to handle the pop3 proxy, and using dspam as an
smtp relay i saw firsthand the LMTP errors i mention above, but you're
right that we should either handle them or explicitly explain why we
discourage their use.

> In daemon mode there are some problems with the hash driver. So I
> think we need to issue a warning if someone wants to enable such a
> configuration. So only the mysql and pgsql driver are thread safe
> and can be used in daemon mode.

Yes, that's what it seems like to me.

> There are also several configurations you need to enable on compile time
> that makes the packaging also a bit complicated. Probably we can change
> them to configuration time parameters ? (For example the filesystem
> scale options and the driver specific configure options)
>
> First things todo (IMO):
> - Make example configurations in Debian for a 'delivery agent proxy',
> 'pop3 proxy' and 'smtp relay'.
> - Get rid of the compile time options that should be configuration
> options (if possible)
> - Create documentation for Debian how to integrate dspam.
>
> This is an initial TODO list, please correct me if I am wrong or add
> more TODO items.

This looks like a good start to me.  We also need to sort out how to
cleanly handle the UPGRADING notes.  3.8.0's UPGRADING file says:

UPGRADING FROM 3.6
- ------------------

1. Add 'Tokenizer' setting to dspam.conf
   The 'Tokenizer' setting in 3.8.0 replaces tokenizer definitions in the 
   "Feature" clause of previous version configurations. See src/dspam.conf
   (after make) for more information about this seting.
 
2. Check calls to dspam_logrotate
   Earlier versions of 3.6 did not prepend a leading "-l" flag to specifying
   log file selection. This is now required.

3. Ensure 3.6.0 malaligned hash databases are converted
   Version 3.6.0 failed to align hash databases to 8-byte boundaries. If you
   are upgrading from v3.6.0 and are using the hash_drv storage driver, you
   should run cssconvert to upgrade your .css files to a fully aligned format.

4. Invert "SupressWebStats" setting in dspam.conf
   SupressWebStats has been changed to simply WebStats, and the setting is
   inverted. Be sure to update this in dspam.conf.

5. Add "ProcessorURLContext" setting in dspam.conf
   ProcessorURLContext has been added to toggle whether URL specific tokens
   are created in the tokenizer process. The "on" value is default for previous
   versions of DSPAM.



> PS: Sorry that I was not so active lately, I was pretty busy at work
> and when I arrived home it was time to go to bed. My work conditions
> are getting better now so I can spend some time on Debian :)

Hey, i'm in the same boat.  There's always a lot of other stuff going
on, i think.

Thanks for the feedback,

    --dkg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>

iD8DBQFGIjwYiXTlFKVLY2URAgr6AJkB3NcRyZSHworr/u5v/hsEOywtiwCgmrG2
ByPLAFTxT22a09TmN4aOzh0=
=yJXE
-----END PGP SIGNATURE-----