On 06/03/14 09:12, Alan Chandler wrote: > I have dovecot-antispam setup to e-mail back through postfix from user > ds...@chandlerfamily.org.uk (a non existent user) to a a dspam > retraining address with the following taken from my postfix master.cf file > > dspam-retrain unix - n n - - pipe > flags=Rhq user=dspam argv=/usr/bin/dspam --client --mode=teft > --class=$nexthop --source=error --user dspam > > However, my logs show that dspam doesn't like something because whenever > a retraining message arrives it says > > Unable to find a valid signature. Aborting. > Process message returned error -5, dropping message > > This thread went off in a side direction which I explored and got lost in. I want to bring it back to the real issue, which I have now.
I have reinstated dovecot-antispam sending the e-mails to the training address when I move them from my inbox to Junk (or vica versa). They arrive. and I get the error message as shown above. I have a file /var/spool/dspam/group with the contents dspam:shared:* and that is the user that I use in the postfix dspam-retrain command (see above). I had a poke around in the hash database. (or at least I presume that is what it is). There are directories for the domain the mail was sent to, and then inside the directory for the domain recipient there is the name of the user as alan.chandler (ie me) that the mail was sent to. inside that directory is a file called alan.chandler.log Inside that file was the signature I was looking for (I looked at the header X-DPAM_Signature of the original mail) ALSO there is a directory "local" with a directory inside that called "dspam" and inside that a directory called "dspam.sig" and inside that there is a with the name of the signature that I was looking for with a .sig extension. The content of this file is binary. So I am wondering - in this retraining do I have to somehow use the name "local"? ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
