On 09.07.2012 20:19, Terry Barnum wrote: > On Jul 7, 2012, at 1:27 AM, Stevan Bajić wrote: > >> On 06.07.2012 23:18, Terry Barnum wrote: >>> [...] >>> >>> Just me, the one test user. >>> >>> $ sudo ls -l /opt/local/var/dspam/data/te...@digital-outpost.com/ >>> total 19008 >>> -rw-rw---- 1 root mail 9562536 Jul 6 13:54 te...@digital-outpost.com.css >>> -rw-rw---- 1 root mail 0 Jun 8 09:50 >>> te...@digital-outpost.com.lock >>> -rw-rw---- 1 root mail 160454 Jul 6 13:54 te...@digital-outpost.com.log >>> drwxrwx--- 776 root mail 26384 Jul 6 13:54 te...@digital-outpost.com.sig >>> -rw-rw---- 1 root mail 16 Jul 6 13:54 >>> te...@digital-outpost.com.stats >> You are not using SQLite. The data you have there indicates that you use >> the Hash driver. > Aha! It seems either I or macports misconfigured the storage driver path. It > was set to: > StorageDriver /opt/local/lib/dspam/libsqlite3.dylib > but should be: > StorageDriver /opt/local/lib/libsqlite3.dylib > > I corrected the StorageDriver path and reloaded dspam, but the contents of > /opt/local/var/dspam/te...@digital-outpost.com/ look the same. What should be > in there if sqlite is the active driver?
SQLite3 driver should automatically create the necessary databases. What happens if you empty or move the content of /opt/local/var/dspam/* and then you let DSPAM recreate everything with the SQLite3 driver enabled? You should have *.sdb files in that directory when SQLite3 is active. >>> Here's another weird thing. After adding the spamSubject="" for default, >>> incoming email now has the the DSPAM tag also at the bottom of the email >>> body. >>> >>> Maybe I don't understand the priority of preferences. I thought it was: >>> - Use dspam.conf (my preference changes here aren't being recognized). >>> - if AllowOverride is set in dspam.conf, default.prefs will override. >>> - If AllowOverride is set in dspam.conf, user prefs will override. >> Ahhh... no. You think that AllowOverride is there for allowing you to >> override preferences hierarchy. But this is not the case. AllowOverride >> is there to allow USERS to overwrite configuration. So if you >> AllowOverride spamSubject then you allow end users to set the spam >> subject on the command line (using dspam_admin) or in the web-UI. > This is how I understand it too--that AllowOverride allows users or a default > to override the prefs. Sorry if my explanation didn't express that clearly. > >> You still have not sent me the content of that default.prefs file. > $ sudo cat /opt/local/var/dspam/default.prefs > spamSubject= > signatureLocation=headers > > Both of these are already set in dspam.conf. Something is not working right. You have in dspam.conf and in the default.prefs signatureLocation=headers and in the other mail you wrote that the signature is now showing up in the message body. > Thanks, > -Terry > >> -- >> Kind Regards from Switzerland, >> >> Stevan Bajić > Terry Barnum > digital OutPost > http://www.dop.com > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
