Вы не можете выбрать более 25 тем Темы должны начинаться с буквы или цифры, могут содержать дефисы(-) и должны содержать не более 35 символов.

V2-V3-Upgrade-Readme.txt 2.8KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485
  1. SNF V2.x to V3.x Source Distribution Readme
  2. Version 3.x of SNF is a departure from previous versions of Message
  3. Sniffer on many levels. Though the core scanning engine and rulebase
  4. files are the same, the new version uses a client/server model.
  5. The client and server programs connect via TCP/Localhost port 9001.
  6. If this is your first experience with SNF in a *nix environment then
  7. please use the snfv2-3.5-PostfixExample as a guied.
  8. The new SNF engine and client are designed to work in parallel
  9. with prior versions of SNF so that it is easy to switch back if
  10. neede. In general all you need to do to switch between versions is
  11. to swap out the client executable in your scripts that scan messages
  12. with SNF. Be careful to read and understand your configuration!
  13. The SNFClient program is compatible with the old snf program when
  14. used as a scanner.
  15. The SNFServer program takes the place of a persistent instance of SNF
  16. and is required for the new version.
  17. The old program will generally ignore the new program and the new
  18. program will generally ignore the old program.
  19. The easiest way to convert a system from the previous (2-3) version
  20. of SNF to the new version is:
  21. * Copy the source distribution to it's own directory.
  22. * Run . compile in each of the client and source directories.
  23. * Copy the working files to your /var/spool/snfilter directory.
  24. cp SNF_Service/SNFServer.exe /var/spool/snfilter
  25. cp SNF_Client/SNFClient.exe /var/spool/snfilter
  26. cp identity.xml /var/spool/snfilter
  27. cp snf_engine.xml /var/spool/snfilter
  28. cp GBUdbIgnoreList.txt /var/spool/snfilter
  29. * Follow the SNFServer_readme.txt instructions and carefully
  30. configure your snf_engine.xml, identity.xml, and GBUdbIgnoreList.txt
  31. files.
  32. When you are ready to go, launch the SNFServer.exe program with
  33. the full path to the configuration file.
  34. /var/spool/snfilter/SNFServer.exe /var/spool/snfilter/snf_engine.xml
  35. If you run this from the console you will see a handy real-time
  36. monitor.
  37. To cleanly shut down the SNFServer use:
  38. SNFClient.exe -shutdown
  39. __________________________________________________________
  40. IF YOU ARE USING THE snfilter SCRIPT or something similar:
  41. * Modify your snfilter script to call the new SNFClient.exe
  42. SNIFFER_EXE=/var/spool/snfilter/SNFClient.exe
  43. * If your script is designed to inject headers then you could use
  44. the new xheader feature in the new engine. To do this:
  45. ** Comment out the section of your script which modifies the message.
  46. ** Turn on xheader injection in the snf_engine.xml file
  47. <xheaders>
  48. <!-- X-Header formatting and output options -->
  49. <output mode='inject'/>
  50. _________________________________________
  51. IF YOU ARE USING THE SpamAssassin Plugin:
  52. Adjust your snfilter.pm to point to the new SNFClient.exe
  53. my $sniffer='SNFClient.exe';
  54. Note: The SNFClient.exe program will accept and ignore the
  55. authentication string so there is no reason to change your
  56. $key.