Richard Freeman <[EMAIL PROTECTED]> wrote: > Elias Oltmanns wrote: >> Could you please examine your >> sample message to find out what might cause dspam to miss the signature? >> > > Dspam must need reading glasses: > > # grep DSPAM /tmp/msg.txt | /usr/bin/dspam --source=error --class=spam > --user root
Try the following and tell us about the results. If any of these commands should succeed, your database will be changed. For further testing purposes you might consider keeping a backup. 1. Specify the actual user instead of root on the commandline. 2. Execute # /usr/bin/dspam --source=error --class=spam --user root --signature=1000,47601b27117601804284693 3. The same with user instead of root. 4. Add --mode=TEFT to the commandline options. > > dspam[9607]: Unable to find a valid signature. Aborting. > dspam[9607]: process_message returned error -5. dropping message. > If you keep seeing these messages for all the commands above, I'd suggest you double check your dspam configuration. In particular, make sure that mysql is the selected storage driver and that dspam actually uses the databases and tables it is supposed to use. Perhaps you'd want to do a whole classify + retrain cycle with a test message like this: # dspam --user testuser --stdout < prestine.msg > tagged.msg # dspam --source=error --class=[previous result] --user root < tagged.msg [...] > Maybe I should take a look at the gentoo patches - assuming this works > for lots of other 3.8.0 users... I'm still using 3.6.8, so I can't warrant for 3.8.0, vanilla or patched. Regards, Elias
