Pete,
Should we change the license info in the plugin.cfg file to match our
license info or should we wait to do so until the release version comes out?
Jim Matuska Jr.
Computer Tech2, CCNA
Nez Perce Tribe
Information Systems
[EMAIL PROTECTED]
- Original Message -
From: Pete McNeil
On Wednesday, April 20, 2005, 1:15:37 PM, Jim wrote:
JM Pete,
JM Should we change the license info in the plugin.cfg file to match our
JM license info or should we wait to do so until the release version comes out?
Please go ahead and make the change. The current code is considered to
be
Pete,
Is there a difference between the normal .snf files I have been downloading
and the one for the plugin? I have setup my script to download the .snf
file and noticed it is a couple mb's smaller than the included demo .snf
file.
Jim Matuska Jr.
Computer Tech2, CCNA
Nez Perce Tribe
Pete, I've been using this plugin for the last couple of months and can say
it's been rock solid. Nice work!
One little feature request though would be to add an option to auto prune
the sniffer log file to so many days, or X killobytes.
-Original Message-
From: [EMAIL PROTECTED]
Tip for MDaemon plug-in users.
Sniffers .cfg file has an option 'not' to scan files larger than 'X'. If
this option is set than no sniffer headers will be placed into the message
(if the message is larger than 'X').
Beware, if you use MD's Content Filter to instruct where to send messages
based
On Wednesday, April 20, 2005, 4:19:48 PM, Jim wrote:
JM Do you configure rules similar to in the previous versions, or by using this
JM as a plug in is there a GUI for configuration.
We configure the rulebase the same way we have in the past. Using the
plugin is not different from using the
_M i'll try this one,
Jim, you will keep all of your Content Filter rules the same 'except' you
will disable (or delete) the two Sniffer entries 'Run Message Sniffer' Add
Headers'. Those two functions will be generated from the plug-in.
Also, if you are using the results codes (in the Content
That will work, we are actually migrating from another email platform so I
am doing this from scratch. Is there any way I can set this rule to attach
the original spam message to a warning message rather than move it to a
separate directory, like you can for the built in spam tests in Mdaemon?
On Wednesday, April 20, 2005, 3:36:14 PM, Dave wrote:
DK Pete, I've been using this plugin for the last couple of months and can say
DK it's been rock solid. Nice work!
DK One little feature request though would be to add an option to auto prune
DK the sniffer log file to so many days, or X
