[Pkg-dspam-misc] Issues with the package and possible solutions.

Matthijs Mohlmann matthijs at cacholong.nl
Sun Jan 8 00:47:13 UTC 2006

Hash: SHA1


The last upload to experimental has fixed several issues. But there are
still a few to go that needs to be fixed before we really can launch it
to unstable.

1.) The installation is not good yet. (First install)
When I issue the following command then dspam get installed in the
following order:
apt-get install dspam libdspam7 libdspam7-drv-mysql

First is libdspam7-drv-mysql installed and setup, then libdspam7 and
finally dspam, while I think that first libdspam7 should be installed
and after that the backend packages and or the frontend package. Also
when I issue the above command the hash backend gets installed. As it
now stays we have the default configuration to the hash backend.

Possible solution is to remove the hash backend and integrate that into
the libdspam7 package. And let the other backends provide libdspam7-drv
and Suggests it in dspam or libdspam7. What do you think about this ?

This solves installation problems with libdspam7-drv-mysql and

I don't know if this is really an issue: the PostgreSQL backend on a
Sarge system (with dspam backported) is very slow. Queries takes almost
600ms to 1.1 second. This has to do with the query planner of PostgreSQL
that makes some wrong decission (PostgreSQL 8.1 does it ok and that's
the one we compile against in unstable)

Another issue I found in the PostgreSQL backend is that the
lookup_tokens (plpgsql function) takes two times more then a normal
select query (Select 4 a 5ms and the lookup_tokens 9 a 10ms), are we
going to fix this and remove the lookup_tokens queries ?

I don't know more issues...


Matthijs Mohlmann
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org


More information about the Pkg-dspam-misc mailing list