Hello Sniffer Folks,
Message Sniffer is now directly supported in Len Conrad's IMGate.
IMGate + SNF allows you to move your spam filtering out in front of
your mail server improving scalability, stability, and performance.
Here are some links:
http://www.imgate.net/?page_id=101
Hi,
Hopefully, you'll be able to convince Alligate and ORF next to use your new
DLL API to scan the content during the SMTP connection without needing the
command line environment...
Best Regards,
Andy
-Original Message-
From: Message Sniffer Community [mailto:[EMAIL PROTECTED] On
Hello Andy,
Thursday, October 9, 2008, 12:27:53 PM, you wrote:
Hi,
Hopefully, you'll be able to convince Alligate and ORF next to use your new
DLL API to scan the content during the SMTP connection without needing the
command line environment...
We have approached Alligate and ORF about
Hi Pete,
SNF code spam threshold (ASSP_SNF_Threshold)
The SNF result code threshold that is considered spam. SNF result codes
at
this level or above will be considered spam for the purposes of ASSP
scoring. The default value of 20 is good in most cases.
Are the result codes
Hello Andy,
Thursday, October 9, 2008, 2:00:49 PM, you wrote:
SNF code spam threshold (ASSP_SNF_Threshold)
The SNF result code threshold that is considered spam.
snip/
If so, I don't think that this can be handled with a greater than type of
threshold, since your list from 20 to 63
Hi:
The design of the plugin at the moment is a binary decision-- either
the message is spam, or not.
I understand - but currently the plugin has a config option that performs a
Resultcode = Threshold test. I think it would be more appropriate to have
a Resultcode in (n, n, n...) test. It
