Dear Dspam Community, Just today I upgraded my debian installation from 3.8 to the most recent deb package, 3.9.1~rc1+git20100826-1 . The upgrade was surprisingly flawless :) I am glad to say that as I was quite afraid of the upgrade.
However, the documentation and support for the hash driver maintenance is still not too sophisticated. As far as I know, there are three steps for a nightly maintenance. First, remove all .sig files that are older than 14 days. Thats easy. Then run cssclean on the .css databases, and then csscompress. Is that correct? My concerns are: - Running cssclean on a database of 103M yields an other db of size 115M. Is that okay that cssclean increases the size? - Running csscompress on this db of 115M yields an other of 122M. Now that's definitely bad. - Running cssclean again on this db of 122M dies with floating point exception, and dspam does not work with it either... I would kindly ask anyone who uses hash driver backend to provide me information on how he/she does the nightly maintenance, and what is considered to be a normal css db size with let's say 200 mails a day. Thank you! Regards, Peter ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
