problem with whitelist

[Peter Marshall <pe...@caris.com>]

Hi guys,

I am having a problem with my whitelist and I am not sure how to fix it.

When I first set up spamassassin with procmail on my rh9 box), I told it to
auto whitelist any main that originated from my internal network
(192.168.200.x/21).  However, for some reason, it did not seem to work and
people were getting annoyed as internal mail was sometimes getting marked as
spam.  To fix the problem I made a rule to auto-whitelist my mail domain.
This worked great .. until I stared getting loads of spam to root@mydomain
and postmaster@mailserv.mydomain and root@mailserv.mydomain etc .... I am
sure you get the picture ... So .. I removed the entry I had for
auto-whitelisting mydomain .. but it still gives any main going to my domain
a -40 or something ....

So,  my questions are:
1.  How do I remover my domain from the whitelist
2.  How do I auto-whitelist based on IP's ?

Thank you for your help

Peter

)

Re: problem with whitelist

[Matt Kettler <mk...@comcast.net>]

At 11:28 AM 7/9/04 -0300, Peter Marshall wrote:
>So,  my questions are:
>1.  How do I remover my domain from the whitelist
>2.  How do I auto-whitelist based on IP's ?

You don't do any of this using the AWL.. the key here is that it's an 
AUTOMATIC whitelist. It's not intended for manual configuration. Those 
manual commands are intended to be temporary corrections, not forced entries.

Also the AWL never white/blacklists on IP alone, that's entirely against 
it's nature.


First, obliterate your AWL db and start fresh.

Next, set up whitelisting correctly:

Use whitelist_from_rcvd in your configfiles to whitelist your local domain. 
Make sure to use whitelist_from_rcvd, not whitelist_from, and make sure the 
rcvd part contains a RDNS string that will match your internal hosts.

OR

create a procmail rule so that local mail skips spamassassin entirely 
(probably a better solution, as it saves CPU time).