Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608
  1. 2009-05-23 Alban Deniz <adeniz@skidmark.localdomain>
  2. * SNFClient/Makefile.am (LIBS): Search SNFMulti library before
  3. CodeDweller.
  4. * SNF2Check/Makefile.am (LIBS): Search SNFMulti library before
  5. CodeDweller.
  6. * CodeDweller/Makefile.am (noinst_HEADERS): Added faults.hpp and
  7. mangler.hpp.
  8. (libCodeDweller_a_SOURCES): Added mangler.cpp.
  9. * SNFMulti/Makefile.am (noinst_HEADERS): Removed tcp_watchdog.hpp
  10. and mangler.hpp.
  11. (libSNFMulti_a_SOURCES): Removed tcp_watchdog.cpp and mangler.cpp.
  12. 2009-05-18 Alban Deniz <adeniz@skidmark.localdomain>
  13. * configure.ac: Incremented version to 3.0.5. This contains
  14. SNF4SA version 0.9.2 (contribution to SA score submitted correctly
  15. by $permsgstatus->{conf}->{scoreset). This addresses the problem
  16. with amavisd-new always having a score of 1.
  17. 2009-02-06 Alban Deniz <adeniz@skidmark.localdomain>
  18. * SNFMulti/SNFMulti.cpp: Replaced with file from Pete, Jan 29,
  19. 2009.
  20. * DEVELOPER_NOTES: Update list of required software (curl replaces
  21. gzip and wget).
  22. * configure.ac: Removed check for wget and gzip, added check for
  23. curl.
  24. * cleanForDist: Added script to clean developer distribution.
  25. * Scripts/getRulebase.in: Modified to use curl instead of wget and
  26. gzip.
  27. 2009-01-27 Alban Deniz <adeniz@skidmark.localdomain>
  28. * DEVELOPER_NOTES: Renamed user tarball name from SNFServer to
  29. snf-server.
  30. * configure.ac: Changed docs to Docs.
  31. * Makefile.am (SUBDIRS): Changed docs to Docs.
  32. * DEVELOPER_NOTES: Updated to include prerequisites for building,
  33. and other new features (OTL #19).
  34. 2008-12-18 Alban Deniz <adeniz@skidmark.localdomain>
  35. * Scripts/Makefile.am: Install snfServer in final destination.
  36. 2008-12-17 Alban Deniz <adeniz@skidmark.localdomain>
  37. * Scripts/Makefile.am (snfServerControl.sample): Replace
  38. configuration file path and name
  39. @sysconfdir@/@PACKAGE_NAME@/@PACKAGE_NAME@.xml.
  40. 2008-12-16 Alban Deniz <adeniz@skidmark.localdomain>
  41. * INSTALL: Added instructions for integration with sendmail.
  42. * Scripts/Makefile.am: Added snfSnifferFilter script.
  43. 2008-12-09 Alban Deniz <adeniz@skidmark.localdomain>
  44. * Scripts/snfSniffer.in: Generate additional temporary filenames
  45. by adding a suffix to MSGFILE rather than a prefix.
  46. * SNFServer/main.cpp: Made VERSION_INFO const char *.
  47. * SNFClient/main.cpp: Made VERSION_INFO const char *.
  48. * SNFMulti/SNFMulti.cpp (enum PatternResultTypes): Remove
  49. 'typedef'.
  50. (snf_EngineHandler::scanMessageFile): Make XHDRInjState const char *.
  51. (snf_EngineHandler::scanMessage): Make DebugInfo const char *.
  52. * SNFMulti/GBUdb.cpp (GBUdbAlert::toXML): Make FlagName a pointer
  53. to const char *.
  54. * SNFMulti/FilterChain.hpp (class FilterChainHeaderAnalysis): Pass
  55. const char * to SetFollowPattern. Make MatchPattern a pointer to
  56. const char *.
  57. * Scripts/snfSniffer.in: Copied from
  58. snfv2-3.5-PostfixExample/sniffer.
  59. * SNFServer/Makefile.am: Moved configuration files to
  60. config_files.
  61. * Makefile.am (SUBDIRS): Added config_files.
  62. 2008-12-08 Alban Deniz <adeniz@skidmark.localdomain>
  63. * SNFServer/main.cpp: Use PACKAGE_VERSION for version string.
  64. * SNF2Check/main.cpp: Removed reference to SNF_Service in #include
  65. directives.
  66. * SNFClient/main.cpp: Removed reference to SNF_Service in #include
  67. directives. Use PACKAGE_VERSION for version string.
  68. * configure.ac: Split SNF_Service into CodeDweller and SNFMulti
  69. directories.
  70. 2008-10-01 Alban Deniz <adeniz@skidmark.localdomain>
  71. * snf.openbsd: Start with /bin/sh rather than /bin/bash. Rename
  72. function stop to stopFunction. Removed $ from beginning of string
  73. constants.
  74. 2008-09-30 Alban Deniz <adeniz@skidmark.localdomain>
  75. * compile: Added -O3 switch, and change first line back to
  76. /bin/sh.
  77. 2008-09-30 Alban Deniz <adeniz@skidmark.localdomain>
  78. * compile: Changed first line back to /bin/sh.
  79. 2008-09-30 Alban Deniz <adeniz@skidmark.localdomain>
  80. * compile: Changed first line back to /bin/sh.
  81. 2008-09-30 Alban Deniz <adeniz@skidmark.localdomain>
  82. * install: Changed the first line to /bin/sh.
  83. * clean: Changed the first line to /bin/sh.
  84. * build: Changed first line to /bin/sh.
  85. 2008-09-24 Alban Deniz <adeniz@snuffy.localdomain>
  86. * snf.freebsd (stop_cmd): Added message when stopping.
  87. 2008-09-24 Charlie Root <adeniz@snuffy.localdomain>
  88. * DEVELOPER_NOTES: Corrected installation for FreeBSD.
  89. 2008-09-21 Alban Deniz <adeniz@skidmark.localdomain>
  90. * DEVELOPER_NOTES: Updated.
  91. 2008-09-20 <adeniz@puffy.localdomain>
  92. * snf.openbsd: Initial revision.
  93. * snf.freebsd: Renamed from snf.bsd.
  94. 2008-09-20 <adeniz@puffy.localdomain>
  95. * install (destdir): Added -m to su command on last line.
  96. * DEVELOPER_NOTES: Updated for OpenBSD.
  97. 2008-09-15 Alban Deniz <adeniz@skidmark.localdomain>
  98. * snf.redhat (snfStartCmd): Use su to start daemon, and specify
  99. shell.
  100. * snf.suse (SNFServer_BIN): Specify shell when issuing su command.
  101. 2008-09-13 Alban Deniz <adeniz@wormy.home>
  102. * snf.bsd: Tested.
  103. 2008-09-13 Alban Deniz <adeniz@wormy.home>
  104. * DEVELOPER_NOTES: Initial revision.
  105. 2008-09-10 Alban Deniz <adeniz@sleepy.localdomain>
  106. * snf.ubuntu: Tested start, stop, reload, status commands.
  107. 2008-09-09 Alban Deniz <adeniz@>
  108. * FilterChain.hpp: Included string.h.
  109. * GBUdb.hpp: included stdlib.h.
  110. 2008-09-09 Alban Deniz <adeniz@sleepy.localdomain>
  111. * snf.suse: Added description to structured comment after
  112. chkconfig.
  113. 2008-09-09 Alban Deniz <adeniz@>
  114. * snf.suse: Initial revision.
  115. 2008-09-09 Alban Deniz <adeniz@sleepy.localdomain>
  116. * install (destdir): Create the user and group first.
  117. 2008-09-09 Alban Deniz <adeniz@>
  118. * install (destdir): Corrected useradd command.
  119. 2008-09-08 Alban Deniz <adeniz@skidmark.localdomain>
  120. * compile: Removed .exe extension.
  121. 2008-09-08 Alban Deniz <adeniz@skidmark.localdomain>
  122. * compile: Removed the .exe extension.
  123. 2008-09-08 Alban Deniz <adeniz@skidmark.localdomain>
  124. * compile: Removed the .exe extension.
  125. 2008-09-08 root <adeniz@skidmark.localdomain>
  126. * getRulebase: Removed .exe from program names.
  127. * snf.redhat: Initial revision.
  128. 2008-09-08 Alban Deniz <adeniz@skidmark.localdomain>
  129. * clean: Create script to remove executables generated by build.
  130. * install: Created script to install applications, files, and
  131. download rulebase.
  132. * build: Created script to build applications.
  133. SNF Command Line & SNFMulti Engine / Client Change Log
  134. ------------------------------------------------------------------------------
  135. 20080710 - Version 3.0.1
  136. Minor change to SNFServer main.cpp:59 - removed cast to (int) which caused
  137. a precision loss error when compiling on 64 bit systems. This changes the
  138. thread pointer info in debug mode slightly (better).
  139. 20080626 - Version 3.0, It's official.
  140. Changed build information.
  141. Removed extraneous comments from configuration file.
  142. 20080524 - Version V2-9rc2.25.7
  143. Optimized networking library for additional speed & stability by moving
  144. receive buffer allocation from heap to stack (automatic).
  145. Optimized timing parameters in SNFClient for improved speed. Polling dealys
  146. are now reduced to 10ms from 30ms.
  147. Removed speed-bug in SNFClient, 100ms guard time between retries was always
  148. executed after an attempt (even a successful attempt). The guard time is now
  149. condition and only fires on unsuccessful attempts.
  150. Updated XCI server logic to ensure non-blocking sockets for clients in all
  151. socket implementations.
  152. 20080424 - Version V2-9rc2.24.6
  153. Refactored snfScanData.clear() to reduce heap work and fragments.
  154. Added mutex to scanMessageFile() entry point just in case some app attempts to
  155. put multiple threads through a single engine handler. scanMessage() is already
  156. protected and fully wraped by the new scanMessageFile() mutex.
  157. Added non-specific runtime exception handling to XHDR injection code.
  158. Added 2 retries w/ 300ms delay to remove original message in XHDR inject code.
  159. If remove fails after 3 attempts the injector throws.
  160. Added 2 retries w/ 300ms delay to rename temp file to msg in XHDR inject code.
  161. If rename fails after 3 attempts the injector throws.
  162. 20080416 - Version V2-9rc2.23.6
  163. Fixed bug where SNCY open() would fail on some Win* platforms with
  164. WSAEINVAL instead of the standard EINPROGRESS or EALREADY which were expected.
  165. Also added WSAEWOULDBLOCK to cover other "ambiguities" in windows sockets
  166. implementations. InProgress() on Win* now test for any of:
  167. WSAEINPROGRESS, WSAEALREADY, WSAEWOULDBLOCK, WSAEINVAL
  168. 20080413 - Version V2-9rc2.22.6
  169. Fixed bug in TCPHost.open() where EALREADY was not counted as a version of
  170. EINPROGRESS. This would cause open() to throw an unnecessary exception when
  171. an open() required extra time.
  172. 20080413 - Version V2-9rc2.21.6
  173. Extended timeout for SYNC session open() to the full session length. This way
  174. if a session takes a long time to open it still has a shot at success.
  175. 20080411 - Version V2-9rc2.20.6
  176. Adjusted snfNETmgr to use non-blocking open in SYNC sessions. Open timeout
  177. is 1/3 of the session timeout. Session timeout is 2 * Session pacing. Open
  178. polling uses golden spiral delay from 10ms to 340ms.
  179. 20080410 - Version V2-9rc2.19.6
  180. Adjusted XCI manager to use new snfCFGPacket paradigm in checkCFG().
  181. Adjusted snf_RulebaseHandler::addRulePanic() to use MyMutex and eliminated
  182. the AutoPanicMutex and waiting scheme.
  183. Refactored scanMessage() to use a ScopeMutex() rather than lock()/unlock().
  184. Refactored scanMessage() to use MyCFGPacket.isRulePanic() test.
  185. Redesigned snfCFGPacket handling to automate grab() / drop() functions.
  186. Fixed lock-up bug: Redesigned AutoPanic posting and checking mechanisms to
  187. eliminate potential dead-lock condition. Under some conditions a precisely
  188. timed auto-panic posting could cause the RulebaseHandler mutex and the
  189. AutoPanicMutex to become intertwined leading to a cascading deadlock. When
  190. this occurred all XCI processing threads and eventually the XCI listener
  191. thread would become blocked waiting to get the current configuration.
  192. 20080409 - Version V2-9rc2.18.6
  193. Enhanced XCI exception handling and logging to provide additional detail.
  194. Added code to explicitely check for zero length files in scanMessagFile().
  195. Previously a zero length file would cause the CBFR module of the filter
  196. chain to throw an invalid buffer exception. Now if the message file is empty
  197. scanMessageFile() will throw a FileError stating FileEmpty!.
  198. 20080407 - Version V2-9rc2.17.6
  199. Enhanced exception reporting in snfXCImrg
  200. 20080405 - SNFServer V2-9rc2.16.6
  201. Reduced safetly limits on status reports to 100K for status reports and 100K
  202. for samples. Previous values were 10M. Most full sessions from the busiest
  203. systems are < 50K total.
  204. Recoded sendDataTimeout() to break uploads into 512 byte chunks and insert
  205. delays only when a chunk is fragmented. This methodology improves reliability
  206. on Win* systems without any significant penalty on systems that don't need
  207. socket sends() to be in smaller chunks.
  208. Fixed TCPClient::transmit() and TCPHost::transmit() bug where returned byte
  209. count might be -1. Now returned byte counts can only be 0 or more.
  210. 20080403 - SNFServer V2-9rc2.15.5
  211. Minor modifications to networking module to better support non-blocking open()
  212. Updated SNFClient with new timing and non-blocking open(). Worst case return
  213. time from SNFClient estimated at 200 seconds (theoretically impossible). No-
  214. connection return time from SNFClient estimated at 20 seconds.
  215. 20080326 - SNFServer V2-9rc2.15.4
  216. Refactored snfNETmgr::sync() to consolidate non-blocking io routines.
  217. Added detailed thread status data to XCI listener thread.
  218. Fixed minor bug in main (not changing revision), Debug flag for internal use
  219. was left on in the last build cycle. It is commented out now.
  220. 20080325 - SNFServer V2-9rc2.14.4
  221. Updated snfNETmgr with comprehensive thread status data.
  222. Refactored snfNETmgr::sync() to check a Timeout, removed TCPWatchdog.
  223. 20080325 - SNFServer V2-9rc2.13.4
  224. Upgraded TCPWatcher code to use new threading features (type, status).
  225. 20080324 - SNFServer v2-9rc2.12.4
  226. Added a "Rulebase Getter" feature as part of the snf_Reloader. When enabled
  227. the Rulebase Getter will launch a user defineable system() call whenever a
  228. new rulebase file is available. The call will be repeated until the condition
  229. is cleared by a successful update of the rulebase file. The Rulebase Getter
  230. will wait a configurable "guard time" between attempts. The default system()
  231. call is "getRulebase" with a guard time of 3 minutes. In most cases this will
  232. launch the provided getRulebase script which should be present in the start
  233. location of SNFServer on most systems. Best practice is to configure the full
  234. path to the update script. The system() call is made in a separate thread so
  235. that if the system() call hangs for some reason only the Rulebase Getter is
  236. stuck.
  237. Built thread monitoring function for SNFServer.exe (Full status report / sec).
  238. The thread monitoring report is turned on when the program is renamed to
  239. SNFDebugServer.exe or if "debug" appears in the file path to the program.
  240. Refactored XCI channels to leverage new thread monitoring.
  241. Refactored Threading to eliminate inline code.
  242. Improved exception handling/reporting in scanMessageFile().
  243. Updated scanMessagFile() header injection code to accommodate messages with
  244. no body. Previous version would throw an exception when it could not find an
  245. injection point. The new version makes the injection point byte 0 and puts
  246. the injected headers at the top of the message using it's best guess about the
  247. type of line endings (CRLF or LF) to use.
  248. Updated Threading library to include high level thread state tracking and
  249. naming. Also creates a global Threads object that can produce a real-time
  250. status report on all threads.
  251. Updated Networking library to use SO_REUSEADDR by default on listeners.
  252. 20080318 - SNF2-9rc1.11.exe Consolidated several mods/fixes
  253. Corrected scan error logging bug. Was posting <s/> now posts <e/>.
  254. Updated scan error logging to be more uniform with non-scan errors.
  255. Developed various script prototypes for postfix integration & automated
  256. updates on win* systems using the new UpdateReady.txt file mechanism.
  257. Fixed a bug in scanMessageFile() where an \n\n style insertion point
  258. would never be detected.
  259. Modified scanMessageFile() header injection to strip <CR> from line ends
  260. when the message file provided does not use them. The line-end style of
  261. the message file is detected while locating the insertion point. If the
  262. insertion point (first blank line) does not use <CR><LF> then the SNF
  263. generated X-Headers are stripped of <CR> in a tight loop before injection.
  264. Enhanced error and exception reporting in SNFMulti.cpp scanMessageFile().
  265. Enhanced exception handling in networking module. All exceptions now
  266. throw descriptive runtime_error exceptions.
  267. 20080306 - SNF2-9rc1.8.exe (FIRST RELEASE CANDIDATE for VERSION 3!)
  268. Added Drilldown Header Directive Functions - When the candidate source IP
  269. comes from a header matching a drilldown directive the IP is marked "Ignore"
  270. in GBUdb and the candidate is no longer eligible to be the source for that
  271. message. This allows SNF to follow the trusted chain of devices (by IP) down
  272. to the actual source of the message. It is handy for ignoring net blocks
  273. because it can match partial IPs but it is designed to allow SNF to learn
  274. it's way through the servers at large ISPs so that the original source for
  275. each message can be evaluated directly.
  276. Added Source Header Directive Functions - This feature allows SNF to acquire
  277. the source IP for a message from a specific header rather than searching
  278. through the Received headers in the message. This is useful when the original
  279. source for a message is not represented in Received headers. For example:
  280. Hotmail places the originating source IP in a special header and does not
  281. provide a Received header for that IP. This feature is protected from abuse
  282. by a "Context" feature which only activates the source header directive when
  283. specific content is found in a specific received header. Using the above
  284. example, this feature can be configured so that a Hotmail source header would
  285. only be read if the top Recieved header contained "hotmail.com [" indicating
  286. that the ptr lookup for the header matched the hotmail domain. Note: When a
  287. source is pulled from a header directive that source is put into a synthetic
  288. Received header and injected into the scanning stream (not the message) as
  289. the first Received header.
  290. Added forced source IP to XCI - It is now possible to "inject" or "force"
  291. the source IP for any message by providing that IP in the XCI request or
  292. directly in a scan...() function call. This allows the calling application
  293. to provide the source IP for a message ahead of any Received headers that
  294. might be in the message. This is useful when the calling application knows
  295. the original source IP for the message but that IP is not represented in
  296. the Received headers and it is not desireable to use the Source Header
  297. Directive mechanism.
  298. Added forced source IP mode to SNFClient - It is now possible to call the
  299. SNFClient utility with an IP4Address using the syntax:
  300. SNFClient -source=12.34.56.78
  301. The -source mode of SNFClient exercises the forced source IP feature in
  302. the XCI (see above)
  303. Added Status Report features to SNFClient and XCI - It is now possible to
  304. request the latest status.second, status.minute, or status.hour data via
  305. the XCI and SNFClient. The syntax for requesting a status report using the
  306. SNFClient is:
  307. SNFClient -status.second
  308. SNFClient -status.minute
  309. SNFClient -status.hour
  310. In addition to providing status reports the SNFClient in this mode will
  311. return a nonzero value (usually 99) if it is unable to get a status report
  312. from SNFServer. This feature can be used to verify that SNFServer is up
  313. and responding. If SNFServer is OK then the result code returned is 0.
  314. Added result codes to SNFClient -test and XCI IP test functions - The XCI
  315. engine has been upgraded to provide the range value for the IP under test
  316. as well as the symbolic result code associated with that range. This allows
  317. the -test function to provide results that are consistent with the GBUdb
  318. configuration without additional processing: For example, if the IP falls
  319. in the Caution range then the Caution result code will be returned just
  320. as if a message had been scanned with the same IP and no pattern match
  321. occurred. The same is true for Truncate and Black range hits.
  322. Added Timestamp and Command Line Parameter data to SNFClient.exe.err - When
  323. an error occurs with SNFClient that may not appear in the SNFServer logs an
  324. entry is appended to the SNFClient.exe.err file. That in itself is not new.
  325. The new feature is that the entries added to the SNFClient.exe.err file now
  326. include timestamp and command line data to aid in debugging.
  327. Added BIG-ENDIAN Conversion - When the SNFServer program is compiled on a
  328. system that uses a BIG-ENDIAN processor (such as a power-mac) the rulebase
  329. load process now includes a routine to convert the token matrix from it's
  330. native LITTLE-ENDIAN format to a BIG-ENDIAN format. This solves a bug where
  331. Power-Mac (and presumably other BIG-ENDIAN systems) could compile and run
  332. the SNF* software but were unable to capture spam because the token matrix
  333. in the rulebase file was misinterpreted.
  334. Note: The BIG-ENDIAN Conversion feature is still considered experimental
  335. because it has not yet been thoroughly tested.
  336. Updated the Configuration Log to include all of the current configuration
  337. features and to improve it's readability.
  338. 20080207 - SNF2-9b1.7.exe
  339. SYNC Timeout now 2x SYNC Schedule
  340. SNFServer now produces an UpdateReady.txt file when the UTC timestamp on
  341. the SYNC server is newer than the UTC timestamp of the active rulebase. It
  342. is presumed that a suitable update script or program will run periodically
  343. and download a fresh rulebase file if the UpdateReady.txt file is present.
  344. The update script should remove the UpdateReady.txt file when it completes
  345. a successful download of the new rulebase file.
  346. Added available rulebase UTC in status reports <udate utc.../>
  347. Added Automatic path fixup for ending / or \
  348. Added option to use local time in log rotation <rotation localtime='no'/>
  349. The default is still utc.
  350. 20071102 - SNF2-9b1.6.exe
  351. Increased MAX_EVALS from 1024 to 2048.
  352. Adjusted defult range envelopes in snf_engine.xml to be more conservative.
  353. 20071017 - SNF2-9b1.5.exe
  354. Added a missing #include directive to the networking.hpp file. The
  355. missing #include was not a factor on Linux and Windows systems but
  356. caused compiler errors on BSD systems.
  357. Corrected a bug in the GBUdb White Range code where any message with a
  358. white range source IP was being forced to the white result code. The
  359. engine now (correctly) only forces the result and records the event when
  360. a black pattern rule was matched and the White Range IP causes that
  361. scan result to be overturned. If the scan result was not a black pattern
  362. match then the original scan result is allowed to pass through.
  363. Corrected a bug in the Header Analysis filter chain module that would
  364. cause the first header in the message to be ignored in some cases.
  365. Corrected an XML log format problem so that <s/> elements are correctly
  366. open ended <s ....> or closed (empty) <s..../> according to whether they
  367. have subordinate elements.
  368. Adjusted the GBUdb header info format. The order of the Confidence
  369. figure and Probabilty figure is now the same as in the XML log files
  370. (C then P). The confidence and probability figures are now preceeded
  371. with c= and p= respectively so that it's easy to tell which is which.
  372. 20071009 - SNF2-9b1.4.exe
  373. Tightened up the XCI handler code and removed the watchdog. The watchdog
  374. would restart the listener if there were no connections in 5 minutes. It
  375. was originally added to provide additional stability, however in practice
  376. there have been no "stalled listeners". Also, a stalled listener would
  377. likely be a sign of a different problem that the watchdog would tend to
  378. hide.
  379. Modified and refactored the XCI configuration management code. All XCI config
  380. changes and up-down operations are now handled in a single function except
  381. upon exit from the main XCI thread where XCI_shutdown() is always called.
  382. Added some more detailed exception handling code to the XCI component so that
  383. more data will be logged in the event of an error.
  384. 20071008 - SNF2-9b1.2.exe
  385. Added support for passing Communigate Message Files directly. Communigate adds
  386. data to the top of the message file. That data stops at the first blank line and
  387. the rfc822 message begins. The SNFServer engine can now be told to ignore this
  388. extra data using the following option:
  389. <msg-file type='cgp'/> <!-- type='cgp' for communigate message files -->
  390. If the msg-file type is anything other than 'cgp' then it will treat the message
  391. file as a standard rfc822 message in the usual way. The default setting is
  392. <msg-file type='rfc822'/>