On Wed, 2003-11-12 at 13:39, Matt Kettler wrote:
> At 12:13 PM 11/12/2003, Kiryl Hakhovich , [EMAIL PROTECTED] wrote:
> >am I missing something here?
> >
> >here is a headers for email that should be going through:
> >
> >---
> >
> >Received: from
> >mail-gateway.exchan
At 12:13 PM 11/12/2003, Kiryl Hakhovich , [EMAIL PROTECTED] wrote:
am I missing something here?
here is a headers for email that should be going through:
---
Received: from
mail-gateway.exchange.goodwillny.org ([10.0.1.27]) by
winxchnge2-2kab.exchange.goodwillny.org
At 01:46 AM 7/16/03 -0400, Gorm Jensen wrote:
I run spamassassin 2.55 on a Redhat 7.2 system
The attached email is spam, but it was not filtered because of the
"USER_IN_WHITELIST" assessment. I studied my whitelist, and neither
the originator nor strings containing the originator are listed, so I
Close. I whitelisted myself, and the spam's "Return-Path" points to
me.
Thanks, Bob.
> Even without seeing the missing attachment, I'm guessing the message
> matched something in the default whitelists in
> /usr/share/spamassassin/60_whitelist.cf
>
> Amazon?
>
> -- Bob
---
Hi,
On Wed, 16 Jul 2003 01:46:17 -0400 "Gorm Jensen" <[EMAIL PROTECTED]> wrote:
> I run spamassassin 2.55 on a Redhat 7.2 system
>
> The attached email is spam, but it was not filtered because of the
> "USER_IN_WHITELIST" assessment. I studied my whitelist, and neither
> the originator nor stri
Slava Madrit said:
> We are using Spamassassin on win32 along with Guinevere 2 for our
> GroupWise 6 system. I have a user who does not want his spam marked by
> spamassassin. So I added an entry into the whitelist that says ALL_SPAM_TO=
> [EMAIL PROTECTED] so that it will not get marked. It s
Shane Williams said:
> I've noticed that whitelisting_to only seems to work when the
> recipient address in question is the first (maybe only) address listed
> in either To: or CC: headers.
Agh, well illustrated -- I've found it. That's a bug alright.
Looks like there'll be a 2.1 bugfix releas
