In a recent update I by mistake did not put an entry in the database field.. and the following was resulted without knowing..
HEADERS 0 CONTAINS
...
We really need a fail safe for CONTAINS ... no blank entry should be allowed.. I can't see a single reason for such a filter.. since for blanks you have devised a test, namely ISBLANK.
Is this with 1.75? That shouldn't happen. Are you sure there aren't any characters other than spaces/tabs after "CONTAINS"? I'll need to do some testing on this, but in any line in a filter, Declude JunkMail should automatically convert a blank 4th section (where the search string goes) into a hard-coded string that should never appear in an E-mail. As a result, none of the filters should fail if they are missing the 4th section.
-Scott
---
Declude JunkMail: The advanced anti-spam solution for IMail mailservers.
Declude Virus: Catches known viruses and is the leader in mailserver vulnerability detection.
Find out what you have been missing: Ask for a free 30-day evaluation.
--- [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.
