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
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: sniffer@sortmonster.com
Sent: Tuesday, May 10, 2005 10:27 AM
Subject: [sniffer] Rule 353039
: [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 to be convinced that a
message
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 - .comcast.net
Thanks
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
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: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 any
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
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 rulbase.cfg
* be sure your entry is in the correct format. You will find examples
at the bottom of your .cfg
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 license.exe reload
snip/
M Pete, when you send out these notifications, would
] Rule 353039 - .comcast.net
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
11 matches
Mail list logo
