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/.nospamcheck
>
> :0fw
> | spamassassin -P
of course, you don't do anything to check the output of the previous command. Try
":0fwe" instead.
> :0:
> * ^X-Spam-Status: Yes
> /dev/null
>
> does not work (that is, the process still deletes the
> SPAM instead of the desired effect of letting that
> email go on through to the user) if ".nospamcheck"
> is placed in a user's home directory.
You really don't want to do this. False Positives do get tagged, and you don't want
to throw
away those mails. They should either go into a different folder for the user to peruse
occasionally, or it should forward to someone for review ([EMAIL PROTECTED]).
--
Randomly Generated Tagline:
"I do not like Santiago. I've always thought that a leader should have a
strong chin. He has no chin, and his Vice-President has several. This to me
is not a good combination."
- Ivonova, Babylon 5 (Midnight on the Firing Line)
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
