Yes you are reading the log correctly.
You've probably scheduled a updates of the surbl, so they probably removed it
somewhere along the line.
If it's in the body it is fair game because of the way the BODY filter works. As
always with filters, the shorter the comparison, the more dangerous it is. That's why
full non-filter support for SURBLs would be a great addition to Declude.
I have these in my SURBL exclude file:
edu.au
ne.jp
ly.to
oo.to
Scott Fisher
Director of IT
Farm Progress Companies
>>> [EMAIL PROTECTED] 07/20/04 11:43AM >>>
Hi,
>From the Declude log
07/19/2004 08:04:24 Qb8bf32820036f483 Filter SURBL: Not skipping E-mail
due to current weight of 8.
07/19/2004 08:04:25 Qb8bf32820036f483 Triggered CONTAINS filter SURBL on
ly.to [weight->0; [EMAIL PROTECTED]
07/19/2004 08:04:26 Qb8bf32820036f483 CMDSPACE:8 nNOLEGITCONTENT:-5
SURBL:7 . Total weight = 10.
07/19/2004 08:04:26 Qb8bf32820036f483 Msg failed SURBL (Message failed
SURBL test (line 435, weight 7)). Action=WARN.
Does this mean that the line the SURBL filter tripped on was
[EMAIL PROTECTED] and then it assigned a weight of 7 to the
score.
I looked in my SURBL.txt file and the above does not appear??
Am I reading the log right?
Thanx
Goran Jovanovic
The LAN Shoppe
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
