Ok, USER_IN_WHITELIST has nothing to do with the AWL, but yes, it does look
at Sender:
Snipping from EvalTests.pm's subroutine all_from_addrs, which is used in
check_from_in_whitelist:
return $self-{main}-find_all_addrs_in_line
($self-get ('From') . # std
Roman Katzer said:
On Monday, January 20, 2003, 21:36:07, you wrote:
It is pretty trivial, but I wondered if anyone else has yet
found that helpful and should it be a suggestion for an enhancement - maybe
report_header_nonspam 1 or something??
Count me in!
What did you change?
I
Hi.
I'm on a debian Linux machine, running sarge/testing.
Whenever I try to start spamd or spamassassin, they consume all available
memory until they're killed by the system.
Just for kicks, I added 5 GB of swap space. That's right, 5 Gigabytes. Then
I started spamd again.
It used up all 5GB
Greetings,
First let me apologize if this has been covered before but for the last
several days I have been unable to search the arcchives for this list (the
search allways times out).
That said...I've been using spamassassin (currently 2.31) for a long time
now on an old PII-266 under a
sabat said:
This is a patch I always find myself making whenever I install SA on our
servers. It's useful to always have the spam report included in the
headers, even if a mail is not tagged as spam -- we often want to know
what rules the mail triggered, and maybe why it didn't get
