On Wednesday, May 15, 2002, at 11:48 AM, dman wrote:
> | :0:
> | * X-Spam-Level: **
> | /dev/null
>
> Are you sure this does what you think it does? I think this regex
> reads like this :
>
> 0 or more occurences of
Well, I typed it in, not copied and pasted. So yes, you need to escape
> Although I would prefer a way to bounce it (with spamassasin headers), on
> the off chance that there is ever legitimate mail with a spam score over 10.
>The only once I've ever seen was a sample sent to this list with a score
> of 39. Everything else over 8 has been spam.
Rather than bo
On Wed, 2002-05-15 at 08:26, LuKreme wrote:
> :0:
> * X-Spam-Level: **
> /dev/null
Doesn't that have to be
* X-Spam-Level: \*\*\*\*\*\*\*\*\*\*
in regexp syntax?
> Although I would prefer a way to bounce it (with spamassasin headers), on
> the off chance that there is ever legitimate
On Wed, May 15, 2002 at 09:26:50AM -0600, LuKreme wrote:
| On Tuesday, May 14, 2002, at 08:24 PM, Sidney Markowitz wrote:
| >On Tue, 2002-05-14 at 18:28, Ron Carter wrote:
| >
| > :0:
| > * ^X-Spam-Status: Yes
| > /dev/null
| >}
| >
| >I agree with Theo that piping to /dev/null is not a good idea
> On Tuesday, May 14, 2002, at 08:24 PM, Sidney Markowitz wrote:
> > On Tue, 2002-05-14 at 18:28, Ron Carter wrote:
> >
> > :0:
> > * ^X-Spam-Status: Yes
> > /dev/null
> > }
> >
> > I agree with Theo that piping to /dev/null is not a good idea because
> > spamassassin is
> > not perfect.
>
>
On Tuesday, May 14, 2002, at 08:24 PM, Sidney Markowitz wrote:
> On Tue, 2002-05-14 at 18:28, Ron Carter wrote:
>
> :0:
> * ^X-Spam-Status: Yes
> /dev/null
> }
>
> I agree with Theo that piping to /dev/null is not a good idea because
> spamassassin is
> not perfect.
I have
:0:
* X-Spam-Level
> :0
> * ! ? test -f $HOME/.nospamcheck
>
> :0fw
> | spamassassin -P
>
> :0:
> * ^X-Spam-Status: Yes
> /dev/null
Hummm, if I understand well procmail receips, what you do is:
if $HOME/.nospamcheck exists, then
empty here, do nothing
for all messages, filter through SA
if the message is fl
On Tue, 2002-05-14 at 18:28, Ron Carter wrote:
> :0
> * ! ? test -f $HOME/.nospamcheck
>
> :0fw
> | spamassassin -P
>
> :0:
> * ^X-Spam-Status: Yes
> /dev/null
Theo gave you one workable answer, but you probably meant to do was:
:0
* ! ? test -f $HOME/.nospamcheck
{
:0fw
| spamassassin -P
:0
On Tue, May 14, 2002 at 09:40:01PM -0400, Theo Van Dinter wrote:
> > :0
> > * ! ? test -f $HOME/.nospamcheck
> >
> > :0fw
> > | spamassassin -P
>
> of course, you don't do anything to check the output of the previous command. Try
>
> ":0fwe" instead.
Actually, you're testing if the file _does
On Tue, May 14, 2002 at 07:28:24PM -0600, Ron Carter wrote:
> This is the first of two problems we are having in
> the implementation of spamassassin system-wide.
>
> We want to give users the ability to "opt-out" of
> the spamassassin processm but the following:
>
> :0
> * ! ? test -f $HOME/.no
Howdy all...
This is the first of two problems we are having in
the implementation of spamassassin system-wide.
We want to give users the ability to "opt-out" of
the spamassassin processm but the following:
:0
* ! ? test -f $HOME/.nospamcheck
:0fw
| spamassassin -P
:0:
* ^X-Spam-Status: Yes
/
11 matches
Mail list logo
