madscientist
/
PKG-SNF-CS-NIX
Volgen 1
Ster 0
Vork 0
Code Kwesties 0 Pull-aanvragen 0 Publicaties 0 Wiki Activiteit
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
121 Commits
1 Branch
Tree: e417c03c04
Branches Labels
${ item.name }
Maak branch ${ searchTerm }
van 'e417c03c04'
${ noResults }
PKG-SNF-CS-NIX/SNF_CS_Developer_Package/SNF4SA/SNF4SA_README

SNF4SA_README 2.8KB
Ruw Blame Geschiedenis

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061 
  1.                SpamAssassin SNF4SA Plugin for SNFServer

  2.                              README file

  3. 

  4.               Copyright (C) 2009 ARM Research Labs, LLC.

  5. 

  6.            See www.armresearch.com for the copyright terms.

  7.                                    

  8. This directory contains the SpamAssassin plugin for SNFServer.

  9. 

  10. The plugin implements a rule that checks the email message with

  11. SNFServer.

  12. 

  13. If SNFServer determines that the email message is spam, then the

  14. plugin calculates a plugin score that depends on the SNFServer result.

  15. The plugin score for each SNFServer result is specified in the

  16. configuration file using the "snf_result" configuration line (please

  17. see the INSTALL file for further info).

  18. 

  19. The GBUdb scan result also changes the plugin score by:

  20. 

  21.   abs(p * c) ^ 0.5 * sign(p) * MaxWeight

  22. 

  23. where p is the probability and c is the confidence returned by the

  24. GBUdb scan, sign(p) is -1 if p < 0 and +1 otherwise, and MaxWeight is

  25. specified in the configuration file.  If SNFServer is not configured

  26. to insert the GBUdb scan results into a header in the message, or

  27. MaxWeight is not specified in the configuration file, then the

  28. plugin score is not affected by the GBUdb scan results.

  29. 

  30. If SpamAssassin supports dynamic score reporting (SpamAssassin version

  31. 3.2.0 or later), then the plugin score is added to the score of the

  32. message.

  33. 

  34. If the version of SpamAssassin is earlier than 3.2.0, then the plugin

  35. behavior is different.  In this case, if the plugin score is equal to

  36. or above a threshold specified in the configuration file, then a fixed

  37. value specified in the configuration file is added to the score of the

  38. message.  If instead the plugin score is below the threshold, then the

  39. score of the message is not changed by this plugin.  The fixed value

  40. is specified by the "score" configuration line, and the threshold is

  41. specified by the "pre_3.2_static_sa_score_threshold" configuration

  42. line.  Please see the INSTALL file for further info.

  43. 

  44. In addition to scanning the message, the plugin inserts headers into

  45. the email.  The SNFServer must be configured to generate the

  46. X-headers.  Please see the SNFServer documention for configuration

  47. instructions.  The plugin obtains the headers from SNFServer (using

  48. the XCI interface), and inserts the headers into the email message.

  49. The following headers are inserted by the plugin into the message if

  50. SNFServer is configured to generate them:

  51. 

  52.   1) 'X-SPAM-MessageSniffer-Scan-Result' contains the body of the

  53.   X-MessageSniffer-Scan-Result header inserted by SNFServer.

  54. 

  55.   2) 'X-SPAM-MessageSniffer-Rules' contains the body of the

  56.   X-MessageSniffer-Rules header inserted by SNFServer.

  57. 

  58.   3) 'X-SPAM-GBUdb-Analysis' contains the body of the X-GBUdb-Analysis

  59.   header inserted by SNFServer.

  60. 

  61. Please see the INSTALL file for installation and configuration.