>1.  When I use the SPAMHEADERS test it picks up almost all SPAM we recieve 
>that the other tests I use miss,  but it also picks up some legitimate 
>email.  The legitimate email often has lower case name followed by capital 
>domain (EX: <mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED]) Is there 
>any way to modify the test to let the good email through while still 
>blocking the bad?

That's the holy grail of spam detection -- letting all the good E-mail 
through, while blocking the bad.

I don't believe that the SPAMHEADERS test checks the case of the headers 
(lowercase/uppercase).  If there are certain domains that this is happening 
to (which is likely, because few people send out mail with the domain 
capitalized), you can whitelist them:

         WHITELIST       FROM    @TOLLANDBANK.COM

Adding the above line to the \IMail\Declude\global.cfg file will prevent 
any E-mail coming from a user at TOLLANDBANK.COM from being treated as spam.

>2.  Is there any documentation on how to use the Whitelist and how we can 
>create our own tests?

You add (to \IMail\Declude\global.cfg) the word "WHITELIST", followed by 
"IP", "FROM", or "ANYWHERE", followed by the text to look for.  For 
example, "WHITELIST IP 127.0.0.1" would whitelist any E-mails coming from 
the IP address 127.0.0.1.  You could also use "WHITELIST IP 127.0.0." to 
whitelist any IP beginning with 127.0.0.

Some examples of FROM would be "WHITELIST FROM @declude.com" to whitelist 
any E-mail from declude.com, or "WHITELIST FROM [EMAIL PROTECTED]" to 
just whitelist E-mails from [EMAIL PROTECTED]

An example of ANYWHERE might be "WHITELIST ANYWHERE This is not spam" 
(although you wouldn't want to do that; most E-mail that contains "This is 
not spam" really is spam).

You can have up to 100 WHITELIST entries in your \IMail\Declude\global.cfg 
file.

>Also I posted a question earlier about why Declude is using Global.cfg 
>instead of $default$.JunkMail file settings on incoming email - do you 
>have any ideas why?

To get a better idea of what is happening, you can use the Declude debug 
mode.  To do this, change the "LOGLEVEL LOW" line in 
\IMail\Declude\global.cfg to "LOGLEVEL DEBUG".  Then, after an E-mail has 
come through that used the global.cfg settings instead of the 
$default$.JunkMail settings, you can switch it back to "LOGLEVEL LOW" (the 
debug mode adds huge amounts of information to the log file).  You can then 
send me the \IMail\Declude\vir####.log file, letting me know which E-mail 
was using the wrong settings, and I can take a look at it to see what the 
problem may be.
                                                -Scott

---

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".  You can E-mail
[EMAIL PROTECTED] for assistance.  You can visit our web
site at http://www.declude.com .

Reply via email to