Whitelist not working

[Elsa Andrés <e....@ist-sci.com>]

Hello,

I am trying to get manual whitelisting to work without success.

Some background:

- SA is running as daemon every time the system is started
- SA version is 3.0.0
- SA is installed on a SuSE 8.2 box
- Using /etc/mail/spamassassin/local.cf sitewide rules
- E-mails trajectory is as follows:

(1) Fetchmail > (2) Postfix > (3) SA > (4) Cyrus

1. Fetchmail downloads e-mails from various POP3 servers
2. Fetchmail delivers e-mails to Postfix
3. Postfix "filters" e-mails to SA
4. SA marks the e-mails and then delivers to Cyrus POP3 account

All these points (1-4) are working as expected, including SA bayes
databases, AWL, etc. The only thing I cannot get it to work is
"whitelist_from" parameter, although is configured O.K.

In /etc/mail/spamassassin/local.cf:

whitelist_from *@domain1.com *@domain2.com
whitelist_from *@domain3.com *@domain4.com
whitelist_from *@domain5.com *@domain6.com
whitelist_from *@domain7.com *@domain8.com

But e-mails coming from "user@domain1.com" or "user@domain5.com" are not
marked with USER_IN_WHITELIST. When I say "from" I refer to "From:" field
listed in e-mails header.

I am aware this can be the easiest parameter to configure in SA but I cannot
guess where the error could be.

Any idea on how to get around this issue will be appreciated.

Re: Whitelist not working (solved)

[Marco van den Bovenkamp <ma...@linuxgoeroe.dhs.org>]

Elsa Andrés wrote:

> Wow... I'm impressed!
> 
> I added "-x" option to spamd start script as you mentioned (to prevent "user
> prefs" to become active) and, sure it works!
> 
> Thank you very much for you tip. I was being crazy to find the error, and
> looked and re-looked the local.cf and anything seemed O.K. I think SA admins
> should add a little note in documentation in order to prevent SA user's
> sanity...

Not that impressive; I got hit by it myself when I started using spamd 
instead of spamassassin directly :-)

It's fixed in the new version (3.0.1), so you might consider upgrading 
to that.

-- 

		Groeten,

			Marco.

RE: Whitelist not working (solved)

[Elsa Andrés <e....@ist-sci.com>]

>You're probably getting hit by bug 3855 ('whitelist_from in local.cf
>ignored after whitelist_from loaded from users prefs').
>
>Either disable the user_prefs (if you are not using them) by giving
>spamd the '-x' option, or upgrade to 3.0.1, where it's fixed.

Hi Marco,

Wow... I'm impressed!

I added "-x" option to spamd start script as you mentioned (to prevent "user
prefs" to become active) and, sure it works!

Thank you very much for you tip. I was being crazy to find the error, and
looked and re-looked the local.cf and anything seemed O.K. I think SA admins
should add a little note in documentation in order to prevent SA user's
sanity...

:-D

Greetings.

Re: Whitelist not working

[Marco van den Bovenkamp <ma...@linuxgoeroe.dhs.org>]

Elsa Andrés wrote:

> Any idea on how to get around this issue will be appreciated.

You're probably getting hit by bug 3855 ('whitelist_from in local.cf 
ignored after whitelist_from loaded from users prefs').

Either disable the user_prefs (if you are not using them) by giving 
spamd the '-x' option, or upgrade to 3.0.1, where it's fixed.

-- 

		Regards,

			Marco.

RE: Whitelist not working

[Elsa Andres <e....@ist-sci.com>]

>Matt Kettler wrote:
>> Suggestion: do ONE whitelist per whitelist_from statement, not two.
>> whitelist_from should only accept one parameter.
>>
>> whitelist_from_rcvd expects two parameters, but the second parameter
>> is not a From: address, so perhaps looking at those got you
>> confused..
>
>Barring major changes to the configuration for whitelist_from since 2.64
>(and back at least as far as 2.4x), whitelist_from should accept
>multiple entries on each line.
>
>For practical reasons, you may need multiple lines (I have serveral
>users with ~30-odd lines of whitelist_from entries, totalling ~80-100
>specific entries) and they work just fine for 2.64.
>
>You're right about whitelist_from_rcvd though.

Hello Matt and Kris,

As per SA documentation, "whitelist_from" can understand several formats,
such as:

whitelist_from *@domain.com user1@domain2.com
whitelist_from user2@domain3.com

And so on. So the problem was not pointing to there. Marco told me the
solution, that pointed to SA bug, and once applied his solution, anything is
working as expected.

Thanks, anyway, for your ideas.

Regards,

Re: Whitelist not working

[Kris Deugau <kd...@vianet.ca>]

Matt Kettler wrote:
> Suggestion: do ONE whitelist per whitelist_from statement, not two.
> whitelist_from should only accept one parameter.
> 
> whitelist_from_rcvd expects two parameters, but the second parameter
> is not a From: address, so perhaps looking at those got you
> confused..

Barring major changes to the configuration for whitelist_from since 2.64
(and back at least as far as 2.4x), whitelist_from should accept
multiple entries on each line.

For practical reasons, you may need multiple lines (I have serveral
users with ~30-odd lines of whitelist_from entries, totalling ~80-100
specific entries) and they work just fine for 2.64.

You're right about whitelist_from_rcvd though.

-kgd
-- 
Get your mouse off of there!  You don't know where that email has been!

Re: Whitelist not working

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

At 11:54 AM 10/25/2004 +0200, Elsa Andrés wrote:
>whitelist_from *@domain1.com *@domain2.com
>whitelist_from *@domain3.com *@domain4.com
>whitelist_from *@domain5.com *@domain6.com
>whitelist_from *@domain7.com *@domain8.com
>
>But e-mails coming from "user@domain1.com" or "user@domain5.com" are not
>marked with USER_IN_WHITELIST. When I say "from" I refer to "From:" field
>listed in e-mails header.

Um, does the above pass spamassassin --lint?

Suggestion: do ONE whitelist per whitelist_from statement, not two. 
whitelist_from should only accept one parameter.

whitelist_from_rcvd expects two parameters, but the second parameter is not 
a From: address, so perhaps looking at those got you confused..