I have reached a small impass with my spam retraining mechanisms, and I 
think it is because I don't understand signatures properly.

My basic set up is postfix <->dspam-milter<->dspam with the hash 
database as the backend. Postfix eventually deliverers via lmtp to 
dovecot. using sender_bcc_maps, each user gets their sent mail saved

I think that works because
a) the hash database has stuff in it
b) my messages have X-DSPAM headers in them

this was all done before I did the following

I added a file group to /var/spool/dspam  with a single line with 
dspam:shared:* in it

My rationale for this was two fold

1) There is only 3 of us with 4 accounts.  It is probably better to 
share the dictionary
2) See below on sending the training messages from a different user, so 
that the sender_bcc_maps don't save the training mail

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


Is this because the messages where originally trained as user alan and 
not dspam? or is it indicative of a real problem.

I don't quite yet know how to test this - I will probably have to 
forward it off an outside address and bring them back through to check, 
but I would really like to understand what is the problem first, and 
sending the e-mail to outside haves the risk that I will be seen as a 
spammer, so I would prefer to avoid it if possible.

Thanks

Alan Chandler








------------------------------------------------------------------------------
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

Reply via email to