I'm moving this over to satalk, because this is really not a question for the saDev list since it has nothing to do with development and everything to do with day-to-day system admin type knowledge.

If you want spamd to have it's own logfile, change the log facility using spamd -s.. Find one of the local facilities not used by your system like local6. By default it uses the mail facility, thus goes in with all the messages from your MTA.

then Re-configure your system logger to output local6.* to /var/log/spamd. in most cases you do so in syslog.conf, but some systems use a different configuration for syslog-ng.

The following is an example based on redhat 7.x's syslog.conf:

# Log all the mail messages in one place.
mail.* /var/log/maillog
# Log spamd sepparate
local6.* /var/log/spamd

You'll probably need to add "local6.none" to the limits of your /var/log/messages entry too:

*.info;mail.none;authpriv.none;cron.none;local6.none /var/log/messages


At 09:29 PM 1/9/2003 -0800, Marc Perkel wrote:
How do I get spamd to create it's own log file?


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Spamassassin-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-devel


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to