Matt,
your email in fact pointed out a bit of sloopiness on my part in the
logging. I have changed
it so it now should show correctly which messages actually trigger a
call to spamc without
me having to look at the verbose log listings.
Thanks again,
Pete
HERE IS THE NEW rc.spam
# send ma
Matt,
Thanks for the prompt reply. Indeed you ask a very good question.
No the size of the message seems to not matter. When I turn on the
expanded logging I can see that the message is in fact "assigned" to the
spamc process.
Other ideas?
Pete
Matt Kettler wrote:
Question,
Are the
Question,
Are the "failed" messages > 256000 bytes in size?
If so, you procmail rules are bypassing the calls to spamc. Hence you see the
"first pass" message, but never a pass/fail message afterwards.
> # send mail through spamassassin
> DROPPRIVS=yes
> LOG="FIRST PASS THROUGH SPAMC
> "
> :0fw
I have been running spamassassin for many years with great success.
Recently though I noticed more spam getting through so I updated to
SA 3.1 on my Redhat 9 system. I also added some additional cf's for SA
using ruledujour in hopes of catching more spam. Now however, lots of
messages never seem
