Ви не можете вибрати більше 25 тем Теми мають розпочинатися з літери або цифри, можуть містити дефіси (-) і не повинні перевищувати 35 символів.

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106
  1. MINIMI ( Minimal IMail Insert for SNF)
  2. This program makes it possible to scan messages on IMail using
  3. SNF_Server without the need for additional software.
  4. The SNFIMailShim.exe program is called in place of the normal IMail
  5. delivery agent (smtp32.exe). SNFIMailShim.exe locks the message in
  6. the IMail/spool and then contacts the SNF_Server for scanning. When
  7. the scan is completed SNFIMailShim.exe takes some appropriate action
  8. on the message based on it's configuration. If the message is to be
  9. delivered then SNFIMailShim.exe will unlock the message and call the
  10. original delivery agent (smtp32.exe).
  11. Depending upon the result code from SNF_Server, MINIMI can take one
  12. of the following actions:
  13. pass - Allow the message to be delivered normally*
  14. hold - Move the D and Q file for the message to a folder.
  15. drop - Delete the D and Q file and NOT call smtp32.exe.
  16. * Messages may be altered by SNF_Server before delivery. Most commonly
  17. SNF_Server might inject headers indicating data about the scan. IMail
  18. rules can then be used to react to these headers.
  19. ____________
  20. Installation
  21. Copy the SNFIMailShim.exe and SNFIMailShim.xml files to the IMail
  22. directory -- the same directory where smtp32.exe is found.
  23. Adjust the contents of SNFIMailShim.xml according to your needs.
  24. Especially make sure that the following elements are correct for your
  25. system:
  26. <delivery program='d:\IMail\smtp32.exe'/>
  27. The <delivery/> element describes the program that will be called by
  28. MINIMI to deliver messages. This is normally IMail's smtp32.exe.
  29. <hold path='d:\IMail\spool\spam\'/>
  30. The <hold/> element describes the full path to the directory where
  31. held messages will be moved by default. Be sure to include the \ at
  32. the end - this "path" is prepended to the Q and D file before it is
  33. written to disc.
  34. Note: You can set the mode (pass, hold, drop) for each result code
  35. that may come from SNF_Server. The result code generally represents
  36. the rule group that matched the message -- roughly analogous to the
  37. "type of spam". A zero result [generally] indicates that no patterns
  38. matched the message.
  39. IMPORTANT: Be sure that any paths you reference in the configuration
  40. exist on the system before proceeding.
  41. Final Step: Assuming you already have SNF_Server running you can now
  42. update IMail to use SNFIMailShim.exe for delivery.
  43. *IMail Administrator
  44. localhost
  45. Services
  46. SMTP
  47. Advanced
  48. Delivery Application
  49. IMPORTANT: Be sure to enter the full path to SNFIMailShim.exe
  50. Apply, Stop SMTP, Start SMTP
  51. SNF_Server will produce logs and status information indicating that
  52. messages are now being scanned.
  53. _______________
  54. Operation Notes
  55. If MINIMI encounters problems it will create .err files in the spool.
  56. The .err files will be named for the message files and will contain
  57. information about the error.
  58. Normally you should not see .err files! If you don't see .err files
  59. and SNF_Server is showing messages being scanned then MINIMI is ok.
  60. When a message is locked, MIMINI makes a copy of the Q file named
  61. with a ~ in place of the Q and an extension of .lck. The original
  62. Q file is deleted (not renamed). The .lck file is created before the
  63. Q file is deleted for safety.
  64. If something goes wrong with MINIMI then you may find a .lck file. If
  65. you need to recover the original Q file, simply rename the .lck file
  66. to the original form.
  67. MINIMI is a lightweight utility - it is intended to do as little as
  68. possible, to do it quickly, with as few resources as possible, and
  69. to do it reliably.
  70. HOWEVER -- if you have a problem on a busy server then .lck and .err
  71. files may proliferate quickly!
  72. Have fun!
  73. _M
  74. madscientist@armresearch.com