I think you have something here. Checking the maildroprc script shows it
calling spamassassin instead of spamc. Changing this and restarting Courier
now gives me log messages in the new log file defined by syslog.conf.
Thanks for the insight!
Matt Kettler writes:
At 09:58 PM 3/22/2005, you
sa-list wrote:
> I am using Courier and Maildrop. The scanning seems to be working
> since I can see the header information and I have SA configured to
> "rewrite_header" and this is happening correctly for spam with scores
> higher than 5.0.
> Does this answer your question? What else would you n
I am using Courier and Maildrop. The scanning seems to be working since I
can see the header information and I have SA configured to "rewrite_header"
and this is happening correctly for spam with scores higher than 5.0.
Does this answer your question? What else would you need to see to have a
At 09:58 PM 3/22/2005, you wrote:
I am having problems getting logging to work.
I changed the configuration to use syslog hoping it would start logging
the spamd messages. Before setting up syslog for this, I did not get any
of the messages in maillog either.
The syslog settings seem to be worki
I am having problems getting logging to work.
I am using SA 3.02 on RHEL3. SA is working. Mail headers show the headers
such as:
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.domain.org
X-Spam-Level:
X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,
SGID_FROM_MTA_
