Hello Spam Neutralizers!
I now understand that there is a bug in SpamAssassin Re: trusted_hosts
and whitelist_from_rcvd.
The buggy behavior of checking only whitelist_from_rcvd if the ip is
not in trusted_hosts means that
whitelist_from_rcvd [EMAIL PROTECTED] mailhost.company.com
means that m
On Friday 09 January 2004 02:03 pm, Justin Mason wrote:
> I think so -- whitelist_from_rcvd is checking only untrusted headers, and
> not looking at the trusted ones, which is incorrect. could you open a
> bugzilla entry for this?
Yep. I created this bug.
http://bugzilla.spamassassin.org/show_bug.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Brett Simpson writes:
>On Friday 09 January 2004 11:37 am, Brett Simpson wrote:
>> Here's what I have in my user_prefs...
>> trusted_networks 207.156.7.
>> whitelist_from_rcvd [EMAIL PROTECTED]
>> ns2b.hillsboroughcounty.org
>
>I found that if I set t
On Friday 09 January 2004 11:37 am, Brett Simpson wrote:
> Here's what I have in my user_prefs...
> trusted_networks 207.156.7.
> whitelist_from_rcvd [EMAIL PROTECTED]
> ns2b.hillsboroughcounty.org
I found that if I set the trusted_networks to something other network so that
spamassassin treats m
For the below message I'm trying to whitelist_from_rcvd so it's always ok but it's
doesn't appear to be working.
Here's what I have in my user_prefs...
trusted_networks 207.156.7.
whitelist_from_rcvd [EMAIL PROTECTED] ns2b.hillsboroughcounty.org
spamassassin -D < zstmsg > out 2>&1;grep trust out
