You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Jim Maul <jm...@elih.org> on 2004/06/25 13:58:47 UTC

prevent spamd from logging to syslog

Does anyone know how to stop spamd from logging to the syslog?  only options i
can find have to do with setting which syslog facility to log to, but i want to
turn it off completely.

Any ideas?

Thanks,
Jim

Re: prevent spamd from logging to syslog

Posted by "Malte S. Stretz" <ms...@gmx.net>.
On Friday 25 June 2004 13:58 CET Jim Maul wrote:
> Does anyone know how to stop spamd from logging to the syslog?  only
> options i can find have to do with setting which syslog facility to log
> to, but i want to turn it off completely.
>
> Any ideas?

Depends on which version you use. In the upcoming 3.0 you can specify the 
facility "null" which will disable logging completely.

In 2.6x it was already possible to use the facility "stderr" which would 
pump everything there. Ie. you start it as "spamd -d -s stderr 
$YOUROPTIONSHERE &>/dev/null" and it will be quiet, too.

See 'man spamd' for more infos.

Cheers,
Malte

-- 
[SGT] Simon G. Tatham: "How to Report Bugs Effectively"
      <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
[ESR] Eric S. Raymond: "How To Ask Questions The Smart Way"
      <http://www.catb.org/~esr/faqs/smart-questions.html>

Re: prevent spamd from logging to syslog

Posted by Jim Maul <jm...@elih.org>.
Quoting Scott Rothgaber <sc...@palmetto.tv>:

> Jim Maul wrote:
>  >
>> Does anyone know how to stop spamd from logging to the syslog?
>
> Send output to LOCAL0, add the following syslog.conf and restart syslogd.
>
> LOCAL0     /dev/null
>
> Remember to use tabs, not spaces! Why would you not want logging, BTW?

I dont want logging because i have qmail-scanner logging to syslog which
duplicates the spamd info and then some.

Each message that arrives look like:

Jun 25 10:54:12 external spamd[3586]: connection from localhost [127.0.0.1] at
port 36392
Jun 25 10:54:12 external spamd[14129]: processing message
<40...@localhost> for user@domain.com:512.
Jun 25 10:54:14 external spamd[14129]: clean message (-4.9/5.0) for
user@domain.com:512 in 1.7 seconds, 4856 bytes.
Jun 25 10:54:14 external qmail-scanner[14122]:
Clear:RC:0(209.237.227.199):SA:0(-4.9/5.0): 2.554093 4856
spamassassin-users-return-11459-user=domain.com@incubator.apache.org
user@domain.com Re:_Question_about_spoofing <40...@localhost>
1088175251.14124-0.external.elih.org:2812
orig-external.elih.org108817525147914122:4856

As you can see, it basically logs the spam info twice, once from spamd and the
other from qmail-scanner.


Thanks for the suggestion btw, i'll try it out in a bit.

Jim

Re: prevent spamd from logging to syslog

Posted by Scott Rothgaber <sc...@palmetto.tv>.
Jim Maul wrote:
 >
> Does anyone know how to stop spamd from logging to the syslog?

Send output to LOCAL0, add the following syslog.conf and restart syslogd.

LOCAL0     /dev/null

Remember to use tabs, not spaces! Why would you not want logging, BTW?


Re: prevent spamd from logging to syslog

Posted by Matt Kettler <mk...@comcast.net>.
At 07:58 AM 6/25/04 -0400, Jim Maul wrote:
>Does anyone know how to stop spamd from logging to the syslog?  only options i
>can find have to do with setting which syslog facility to log to, but i 
>want to
>turn it off completely.

Hmm, since that would leave spamd with no logging at all, I don't think 
that's been asked for before.

Really all I can suggest is to send spamd's output to an un-used LOCAL 
facility and then configure your syslogd to ignore messages from it.

That or patch the source to remove the logging (could be quite messy)