Changes

==Statistics==

==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).

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 reported as False Negatives meaning DSPAM claimed they were ham and SpamAssassin scored them as Spam (above spamlevel).

[root@mx]# dspam_stats -H

[root@mx]# dspam_stats -H

===Can I force it to start scoring even though training hasn't completed?===

===Can I force it to start scoring even though training hasn't completed?===

Yes (I will not advice to do so), you can do this by changing config:

Yes, you can do this by changing config:

  config setprop dspam action tag

  config setprop dspam action tag

  signal-event email-update

  signal-event email-update

===Can I alter the score given to DSPAM classified emails?===

===Can I alter the score given to DSPAM classified emails?===

Yes, you have to manually edit the dspam.cf file located in /etc/mail/spamassassin/dspam.cf. Notice that an upgrade of sme-dspam later, will overwrite your modifications. When you have made your modification issue an:

Yes, you have to manually edit the /etc/mail/spamassassin/dspam.cf file. Notice that an upgrade of sme-dspam later, will overwrite your modifications. When you have made your modification issue an:

  signal-event email-update

  signal-event email-update