After upgrading to 3.2.1 from 3.1.1 and not installing with an rpm, i am
unable to get any shell script to work for spamd. Our old spamd script
was logging to a syslog server. So, using the /usr/bin/spamd binary, is
it possible to log to a syslog server? If so, how would i do this?
Chris
On Mon, Jul 09, 2007 at 02:27:47PM -0400, [EMAIL PROTECTED] wrote:
After upgrading to 3.2.1 from 3.1.1 and not installing with an rpm, i am
unable to get any shell script to work for spamd. Our old spamd script
was logging to a syslog server. So, using the /usr/bin/spamd binary, is
it possible
It does so by default, to the mail facility.
I should have asked this differently...I need it to log to a different
facility (local4 facility and a file named spamd.log)
Just to verify, you have the Sys::Syslog module installed? (I believe it's
standard with perl, and spamd would likely crash w/
On Mon, Jul 09, 2007 at 02:48:46PM -0400, [EMAIL PROTECTED] wrote:
I should have asked this differently...I need it to log to a different
facility (local4 facility and a file named spamd.log)
man spamd :)
I also would like to know how to start/stop spamd using /usr/bin/spamd?
spamd doesn't
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, /etc/init.d/spamassassin will
The current SA install was from my initial install of RHEL 4 and using
up2date to get the packages all current. I figured I would stop using
up2date from this point on and switch to CPAN upgrades in the future. The
CPAN method is what I had used before and it worked nicely, plus I can stay
sa-list wrote:
The current SA install was from my initial install of RHEL 4 and using
up2date to get the packages all current. I figured I would stop using
up2date from this point on and switch to CPAN upgrades in the future.
Be sure to *uninstall* the RPM package before installing from CPAN -
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 in
sa-list wrote:
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.
[snip]
... on RHEL4.
[snip]
The top part of my /etc/init.d/spamassassin is:
[snip]
# Set default
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 get SA
10 matches
Mail list logo
