Thanks, Scott. I also thought that whitelist files included all of the same
options as the whitelist commands that go into a global.cfg file.
No:
The D:\IMail\Declude\mywhitelist.txt file would then contain either one
E-mail address ("[EMAIL PROTECTED]") or domain ("@example.com") or subdomain
t;[EMAIL PROTECTED]>
To:
Sent: Monday, January 24, 2005 12:23 PM
Subject: Re: [Declude.JunkMail] whitelist not configured right?
>
> >So in the whitelist file for our domain name, I put
> >a line IP x.x.x.x, where x.x.x.x is my home IP address. However, the
> >Declude
So in the whitelist file for our domain name, I put
a line IP x.x.x.x, where x.x.x.x is my home IP address. However, the
Declude continues to scan messages sent from my home PC for spam, and to act
accordingly.
The problem is that whitelist files don't have an option of "IP x.x.x.x".
In this case
Hi,
We regularly use the whitelist feature with our clients, and it always
works. Now, however, when I try to use it with our own domain, it doesn't
seem to be operating.
When I connect to our mail server from home (using broadband cable) to send
messages, the system always gives me a high spam
