Hello Pi-Web,
ERROR_MSG_FILE means that SNF could not open the file to be scanned.
Be sure the you pass the full path of the message file and that
permissions are correct so that SNF can open the file.
Hope this helps,
_M
Wednesday, January 16, 2008, 12:31:58 PM, you wrote:
No its not the
It seems right - but no go:
In /var/spool/snfilter/msg/
-rw--- 1 snfilter snfilter 2965 Jan 16 18:35 20080116183528_10882.msg
(deleted after process finished)
Result:
s u='20080116173528' m='20080116183528_10882.msg' code='69'
error='ERROR_MSG_FILE'/
sniffer setup:
Adding $INSPECT_DIR to the $SNIFFER_EXE $AUTHENTICATION $INSPECT_DIR$MSGFILE ||
{ command
Now it seems to work.
It seems right - but no go:
In /var/spool/snfilter/msg/
-rw--- 1 snfilter snfilter 2965 Jan 16 18:35 20080116183528_10882.msg
(deleted after process finished)
Result:
s
Hello Pi-Web,
Yep.
The clue was in the log:
m='20080116183528_10882.msg'
Note that the path was missing - only the file name was present.
Now your logs should look more like:
m='/var/spool/snfilter/msg/20080116183528_10882.msg'
Best,
_M
Wednesday, January 16, 2008, 1:23:14 PM, you wrote:
