Hello,
I didn't get an update since 5 March (1908044).
FreeBSD 12.4-RELEASE-p2
spamassassin 4.0.0_2
Mar 17 08:19:41.458 [41854] dbg: channel: metadata version = 1908044,
from file /var/db/spamassassin/4.00/updates_spamassassin_org.cf
Mar 17 08:19:41.471 [41854] dbg: dns: 0.0.4.updates.spam
nt forward?
Kris Deugau writes:
sa-list wrote:
Thanks!
Instead of messing with the /etc/sysconfig/spamassassin file, I just
commented out those lines. Any reason to keep this configuration, other
than wanting more headaches in the future when I try to figure this out
again?
Well, like I said, /
Thanks!
Instead of messing with the /etc/sysconfig/spamassassin file, I just
commented out those lines. Any reason to keep this configuration, other than
wanting more headaches in the future when I try to figure this out again?
Kris Deugau writes:
sa-list wrote:
I can't seem to g
I can't seem to get SA & Syslog to log messages to a log file other than
maillog.
I changed the spamassassin start up script to add "-s local5" to the spamd
start up options. I modified syslog.conf to add local5 as an entity. I
restarted syslog, courier and spamd. I still get logging messages
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
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
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_
