Tom You were right about the tokenizer. Once I corrected that, the chain part of the error message went away. But even if I follow Sydney's suggestion and run
/usr/local/bin/dspam --client --user root --class=spam --source=error instead of just dspam --user root --class=spam --source=error I still get the following errors. I check mysql database and I can find the signature in dspam_signature_data. 29041: [06/04/2007 23:18:52] Signature retrieval for '2,46641fad191982947017269' failed 29041: [06/04/2007 23:18:52] Unable to find a valid signature. Aborting. 29041: [06/04/2007 23:18:52] process_message returned error -5. dropping message. My current compile switches are --enable-daemon --with-storage-driver=mysql_drv --with-mysql-libraries=/usr/lib/mysql --with-mysql-includes=/usr/include/mysql --enable-mysql4-initialization --enable-preferences-extensions --enable-virtual-users --enable-debug --with-dspam-owner=dspam --with-dspam-group=dspam I am going it again without the --enable-mysql4-initialization and with the --enable-verbose-debug and see if that points me in the correct direction. ---- Tom Bombadil <[EMAIL PROTECTED]> wrote: > > It seems like you are you are using 3.8.0 binary with 3.6.8 config file. > > From the UPGRADING file: > 1. Add 'Tokenizer' setting to dspam.conf > The 'Tokenizer' setting in 3.8.0 replaces tokenizer definitions in the > "Feature" clause of previous version configurations. See src/dspam.conf > (after make) for more information about this seting. > > You need: > Tokenizer chain > > > > > Tejas Jin wrote: > > If I read your message correctly using > > > > /usr/local/bin/dspam --client --user root --class=spam --source=error > > should fix it, but I'm getting the same error. > > > > I've actually backed up and installed 3.6.8 to try and figure out whether > > it is a version problem. > > For me it appears to be a configuration problem. I've loaded 3.8.0 now and > > am getting another error on top of the old one. > > > > 28909: [06/04/2007 10:13:30] No such feature 'chained' > > 28909: [06/04/2007 10:13:30] Signature retrieval for > > '2,46641fb5191984127714242' failed > > 28909: [06/04/2007 10:13:30] Unable to find a valid signature. Aborting. > > 28909: [06/04/2007 10:13:30] process_message returned error -5. dropping > > message. > > > > > > My guess is that it running a query against mysql and not getting the > > correct results. MySQL appears to be configured correctly, because when I > > get mail it adds signatures. > > > > > > ---- Stephen Carr <[EMAIL PROTECTED]> wrote: > >> Dear Tejas > >> > >> I think I have a workaround instead of using dspamc use dspam with > >> --client added to the command line. > >> > >> I had a similar messages as you had below adding the --client seemd to fix > >> the problem. My dspam is built with --enable-daemon. > >> > >> I am now using traindspam with dspamc replaced with dspam --client > >> > >> Regards > >> Stephen Carr > >> > >> Tejas Jin wrote: > >>> When I go into mutt, I pipe a spam message to > >>> /usr/local/bin/dspam --user root --class=spam --source=error > >>> > >>> 8349: [06/03/2007 05:14:06] Signature retrieval for > >>> '2,46628bb6130139463419170' failed > >>> 8349: [06/03/2007 05:14:06] Unable to find a valid signature. Aborting. > >>> 8349: [06/03/2007 05:14:06] process_message returned error -5. dropping > >>> message. > >>> > >>> if I go into mysql and manually search for this signature I have no > >>> problem finding the signature or signatures > >>> > >>> Select * from dspam_signature_data where > >>> signature='2,46628bb6130139463419170'; > >>> > >>> > >> > >> -- > >> Stephen Carr > >> Computing Officer > >> School of Civil and Environmental Engineering > >> The University of Adelaide > >> Tel +618-8303-4313 > >> Fax +618-8303-4359 > >> Email [EMAIL PROTECTED] > >> > >> CRICOS Provider Number 00123M > >> ----------------------------------------------------------- > >> This email message is intended only for the addressee(s)and contains > >> information that may be confidential and/or copyright. If you are not the > >> intended recipient please notify the sender by reply email and immediately > >> delete this email. Use, disclosure or reproduction of this email by anyone > >> other than the intended recipient(s) is strictly prohibited. No > >> representation is made that this email or any attachments are free of > >> viruses. Virus scanning is recommended and is the responsibility of the > >> recipient. > >> > >> > > >
