On Tue, 21 Jul 2009 02:28:31 am Michael Watkins wrote: > I wrote: > > cat themailmessage | dspam --user global --class=spam --source=error > > --deliver=summary --process --stdout > > ... fails. I forgot to add that classifying the already classified message > as source "corpus" does succeed and the output indicates that indeed the > sig is being found. > > cat themailmessage | dspam --user global --class=spam --source=corpus > --deliver=summary --process --stdout > X-DSPAM-Result: global; result="Spam"; class="Spam"; probability=1.0000; > confidence=1.00; signature=4a64767266215213795745 > > Note the signature is the same as contained within the message which had > previously been assigned a false negative result. > This is getting too deep for me. If I had one of the ones that sneaked past, and said "source-error" dspam would say that it couldn't find a sig. I have never tried to retrain an error as corpus. Perhaps in that case, dspam sees the signature as more text?
I have just received my second spam to retrain, and it was accepted O.K. Doug. ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Dspam-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspam-user
