I would be wrong, but a recipe like
:0:
...
| /usr/bin/spamc
would eat the message, and nothing would be delivered
You may try this instead:
:0fw:
...
| /usr/bin/spamc
This recipe treat spamc as a filter (indicated by flag 'f'), and the
processed message will be passed to the rest recipes. Anyw
On Mon, 1 Dec 2003, Monique Y. Herman wrote:
> (Please don't top post.)
I'll try my best ;-)
>
> Maybe I'm being pedantic, but do you see it in ps? Here's what I see:
>
> # ps -eaf | grep spamd
> root 27187 1 0 Oct24 ?00:00:17 /usr/sbin/spamd -m 10 -d
> --pidfile=/var/run/spam
On Mon, 01 Dec 2003 at 10:22 GMT, Scott Ehrlich penned:
> Yes:
>
> more /etc/default/spamassassin # /etc/default/spamd.conf # Duncan
> Findlay # November 2001
>
> # WARNING read README.spamd before using. THERE ARE SECURITY RISKS!
>
> # Change to one to enable spamd ENABLED=1
>
> # Options # S
Yes:
more /etc/default/spamassassin
# /etc/default/spamd.conf
# Duncan Findlay
# November 2001
# WARNING read README.spamd before using. THERE ARE SECURITY RISKS!
# Change to one to enable spamd
ENABLED=1
# Options
# See man spamd for possible options. The -d option is automatically
added.
OPT
On Sun, Nov 30, 2003 at 08:48:32PM -0500, Scott Ehrlich wrote:
> Well, I mentioned my incoming email was not getting spam-tagged, and still
> isn't.
>
> Someone (sorry, lost the email :-( pointed me to:
>
> http://dman13.dyndns.org/~dman/config_docs/exim-spamassassin/node11.html
>
> which did
Well, I mentioned my incoming email was not getting spam-tagged, and still
isn't.
Someone (sorry, lost the email :-( pointed me to:
http://dman13.dyndns.org/~dman/config_docs/exim-spamassassin/node11.html
which didn't seem to do much even after I added it.
I have been using SA successfully on
6 matches
Mail list logo
