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

[Matthijs Mohlmann]

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

Daniel Kahn Gillmor wrote:
> Package: dspam
> Version: 3.6.8-5
> Severity: wishlist
> 
> Version 3.8.0 of dspam is now available:
> 
>   http://dspam.nuclearelephant.com/download.shtml
> 
> We should probably treat this new release as an opportunity to think
> through some of the packaging questions that have come up on the list
> over the last couple months.
> 
> In particular, we should think about what configurations we want to
> support and encourage with our packaging.  I've already documented
> problems with daemon mode, related to its LMTP handling and its use in
> conjunction with the hash driver.
> 
> It would probably be a good idea to provide a default configuration in
> lenny that doesn't run afoul of these problems (unless they're fixed
> in 3.8.0).
> 
> does anyone have a test rig that they can use to really slam a dspam
> installation?  I'm concerned that, as a link in the MTA chain, it
> needs to be really robust under high loads and there are certain
> configurations which 3.6.8 (at least) has fallen down.
> 
> 	--dkg
> 

Hi,

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.

About the packaging questions, you are right. And according #366478 we
need to look into the documentation too. I'm not really comfortable with
the documentation that is delivered with dspam.

What kind of configurations do you think about especially ? Currently I use:

postfix - dspam - cyrus

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.

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.

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.

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.

Regards,

Matthijs Mohlmann

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 :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGIjTy2n1ROIkXqbARAtjDAJ9jlZZHZPH6NCLEMxnOlIexPmUKcwCeP7cW
syxwjUZJT3gCGerKtkX07L4=
=U0xD
-----END PGP SIGNATURE-----