On Tuesday, May 10, 2005, 1:03:18 PM, Matt wrote:
M> Pete,
M> My config file was completely unedited, i.e. every setting was commented
M> out. I verified that one and a half hours after the config change this
M> rule was still hitting until I had restarted the service. Maybe there
M> is a bug i
Pete,
My config file was completely unedited, i.e. every setting was commented
out. I verified that one and a half hours after the config change this
rule was still hitting until I had restarted the service. Maybe there
is a bug in the persistent engine reloading the config without
interventi
Matt,
Restarting the sniffer service seems to have done the trick. Thank you for
the suggestion!
Michael Stein
Computer House
[EMAIL PROTECTED]
- Original Message -
From: "Matt" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, May 10, 2005 12:46 PM
Subject: Re: [snif
On Tuesday, May 10, 2005, 12:41:42 PM, Matt wrote:
M> Warning!
M> When you add a RulePanic entry and are running Sniffer in persistent
M> mode, you have to restart the service for it to take effect.
You can also issue ".exe reload"
M> Pete, when you send out these notifications, would you ple
On Tuesday, May 10, 2005, 12:45:53 PM, Computer wrote:
CHS> Mail from Comcast is still getting caught, even with the panic rule in
CHS> place. Any suggestions?
* be sure you have updated .cfg
* be sure your entry is in the correct format. You will find examples
at the bottom of your .cfg file w
See my message below...restart your Sniffer service and it should work.
Matt
Computer House Support wrote:
Mail from Comcast is still getting caught, even with the panic rule in
place. Any suggestions?
Mike Stein
This E-Mail came from the Message Sniffer mailing list. For information and
(un)s
On Tuesday, May 10, 2005, 12:31:18 PM, Erik wrote:
E> Pete,
E> Is this in the "beta"/"free" release of Sniffer rules?
It may not be --- it's new enough that it may have been excluded from
the demo rulebase. To make sure you should make a quick scan of your
SNF log file for that rule number. In an
Mail from Comcast is still getting caught, even with the panic rule in
place. Any suggestions?
Mike Stein
This E-Mail came from the Message Sniffer mailing list. For information and
(un)subscription instructions go to
http://www.sortmonster.com/MessageSniffer/Help/Help.html
On Tuesday, May 10, 2005, 12:12:40 PM, Computer wrote:
CHS> Comcast messages still getting caught. Even after adding the panic rule.
CHS> Even this mail from the list got caught. Can you update my rulebase?
Hmmm... Be sure the format is correct and that it is not commented
out.
All rulebases a
Warning!
When you add a RulePanic entry and are running Sniffer in persistent
mode, you have to restart the service for it to take effect. I changed
this earlier and it had no effect until I restarted the service on my
box. Maybe I'm wrong about this, but just changing my config file had
no e
Pete,
Is this in the "beta"/"free" release of Sniffer rules?
Erik
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Colbeck, Andrew
Sent: Tuesday, May 10, 2005 6:20 PM
To: sniffer@SortMonster.com
Subject: RE: [sniffer] Rule 353039 - .
05 7:28 AM
To: sniffer@sortmonster.com
Subject: [sniffer] Rule 353039 - .comcast.net
Importance: High
Hello Sniffer Folks,
A rule was created today by one of the robots which targets
.comcast.net -- This happened when a number of blacklists including
SBL listed comcast IPs causing the robot t
0, 2005 11:57 AM
Subject: Re: [sniffer] Rule 353039 - .comcast.net
Whew! Just got done forwarding 90 false positives to mail clients. Sure
glad you caught it!
Michael Stein
Computer House
- Original Message -
From: "Pete McNeil" <[EMAIL PROTECTED]>
To:
Sent: Tuesda
Whew! Just got done forwarding 90 false positives to mail clients. Sure
glad you caught it!
Michael Stein
Computer House
- Original Message -
From: "Pete McNeil" <[EMAIL PROTECTED]>
To:
Sent: Tuesday, May 10, 2005 10:27 AM
Subject: [sniffer] Rule 353039 - .com
Hello Sniffer Folks,
A rule was created today by one of the robots which targets
.comcast.net -- This happened when a number of blacklists including
SBL listed comcast IPs causing the robot to be convinced that a
message in the spamtrap warranted tagging the domain.
The rule has been re
15 matches
Mail list logo
