From: "Bowie Bailey" <[EMAIL PROTECTED]>
Evan Platt wrote:
At 01:37 PM 10/6/2006, you wrote:
> > > :0fw: spamassassin.lock
> > > |spamd -L -c -s 512000
>
> This should be:
>
> spamc -c -s 512000
>
> > Now it appears spamassassin isn't checking mail at all, as the
> > mail isn't marked up at all.
> >
> > My cron entry upon bootup is:
> >
> > /opt/local/bin/spamd -L
What the <censored> are you running spamd from cron for? It is
usually started from your init sequence and runs as a daemon.
"spamd -d -c -m3 -Hi --max-conn-per-child=15" is the usual sort
of incantation to start it off. Then it stays running forever.
Without the -d option it does not daemonize.
>
> Get rid of the '-L'.
That went from bad to worse... It looked for a while like all
messages were being scored as 0, but it actually is basically
blackholing messages. I'd ses entries in my mail log, but no mail in
my inbox:
<removed log info>
Then took out
> :0fw: spamassassin.lock
> |spamc -c -s 512000
From my procmail, and it's fine - well obviously no spamassassin
scores.
OF COURSE NOT - you probably do not have spamd running at that time.
Or if it is it's not listening for you.
I'm at my wits end, and the fact that I'm sick isn't helping much
either. :(
I'm not familiar with the procmail syntax. When you do "|program",
what is the expected output of the command? If it expects to get the
filtered email back from the program, you will need to leave off the
'-c' like this:
|spamc -s 512000
He might try "| /usr/bin/spamc -s 512000".
I use this:
:0 fw: spamassassin.lock
* < 500000
* !^List-Id: .*(spamassassin\.apache.\org)
| /usr/bin/spamc -t 150 -u jdow
{^_^}
