[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: spamd loging
You should restart syslogd after you modify /etc/syslog.conf.
J. Spaceman
-----Original Message-----
From: owner-misc@openbsd.org [mailto:owner-misc@openbsd.org] On Behalf Of
Doros Eracledes
Sent: Tuesday, February 24, 2004 8:57 AM
To: misc@openbsd.org
Subject: spamd loging
spamd does not produce proper loging on my system.
i added the following in syslog.conf
!spamd
*.* /var/log/spamd
the only thing i get on /var/log/spamd is this:
listening for incoming connections.
i now start spamd using the following command
/usr/libexec/spamd -v -d > /var/log/spamd &
and get the following(in /var/log/spamd) :
64.127.101.77 connected for 626 seconds.
206.131.230.4 connected for 625 seconds.
216.108.233.9 connected for 625 seconds.
but i think that i should be getting more, like who the
spam mail is destined for etc.
note that before i put *.* in my syslog.conf file i put
!spamd
daemon.err;daemon.warn;daemon.info /var/log/spamd
as the spamd man page says, but no luck.
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.593 / Virus Database: 376 - Release Date: 2/20/2004
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.593 / Virus Database: 376 - Release Date: 2/20/2004
- References:
- spamd loging
- From: "Doros Eracledes" <Doros.Eracledes@gcc.com.cy>