Line 49:
Line 49:
signal-event email-update
signal-event email-update
+
+
==Statistics==
+
+
You can follow how DSPAM is doing by use of the dspam_stats command. Below is an example where I started the tagging process before training was complete. Here you can see that 4 emails where False Negatives meaning DSPAM claimed they were ham and SpamAssassin scored them as Spam (above spamlevel).
+
+
[root@mx]# dspam_stats -H
+
qpsmtpd:
+
TP True Positives: 71
+
TN True Negatives: 66
+
FP False Positives: 0
+
FN False Negatives: 4
+
SC Spam Corpusfed: 5890
+
NC Nonspam Corpusfed: 872
+
TL Training Left: 1562
+
SHR Spam Hit Rate 94.67%
+
HSR Ham Strike Rate: 0.00%
+
PPV Positive predictive value: 100.00%
+
OCA Overall Accuracy: 97.16%
+
==FAQ==
==FAQ==