Re: [Bump] No log to syslog after upgrade
Sorry I took so long to respond to this. Of course it was me who should RTFM :-P Since we are using CGPSA we are not using SPAMD if I understand it right. From the CGPSA website ( http:// www.tffenterprises.com/cgpsa/ ): The filter works efficiently, by directly using the SpamAssassin API. It does not rely on a daemon process such as spamd or on the execution of shell scripts (as the usual process for utilizing SpamAssassin with CommuniGate servers does). I guess what I saw in our old logs must have been from tests with SPAMD, unless something changed between versions (I upgraded CGPSA and SA at the same time). Thanks for your help Theo and John, much appreciated. I also got to agree with Kurt about the possibility for SA to write to syslog. It would help to analyze and adjust SA if you could pull out some statistics (or is that possible another way?). Thomas 7 sep 2006 kl. 18.33 skrev Theo Van Dinter: On Thu, Sep 07, 2006 at 09:11:22AM -0700, John D. Hardin wrote: [server]spamassassin --lint -D [22110] dbg: logger: adding facilities: all [22110] dbg: logger: logging level is DBG snip Is your syslog daemon configured to discard debug-level messages? [...] At last check, spamassassin doesn't log to syslog. spamd does. -- Randomly Generated Tagline: ... advise the users that although it can help, they are known problems ... - Stanislav Meduna Here's our setup: OSX 10.3.9, Communigate 4.2.8, CGPSA 1.4, SA 3.1.3
RE: [Bump] No log to syslog after upgrade
This is news to me - I'll have to dig into the docs again, and see what I can find. Sigh. I must be getting old or something. | -Original Message- | From: Stuart Johnston [mailto:[EMAIL PROTECTED] | Sent: Thursday, September 07, 2006 15:27 | To: Kurt Buff; users@spamassassin.apache.org | Subject: Re: [Bump] No log to syslog after upgrade | | | Kurt Buff wrote: | I've requested an account, and am waiting for the password. | | I understand about command line tools and their use, but SA | is a bit of a | special case, as it's used as more than simply a command line tool - | especially when you consider its use with Amavis, etc. | | amavisd-new has its own logging facilities including the | option to log to syslog or a separate log | file. There is also an option to log debugging output from | SA. You should ask on the amavis list | if you need more details. |
Re: [Bump] No log to syslog after upgrade
On Thu, 7 Sep 2006, Thomas Ericsson wrote: [server]spamassassin --lint -D [22110] dbg: logger: adding facilities: all [22110] dbg: logger: logging level is DBG snip Is your syslog daemon configured to discard debug-level messages? Are the messages being logged to /var/log/message (or whatever your default is) rather then mail.log? After our upgrade from SA 2.6.3 to SA 3.1.3 we do not get any logs written to /var/log/mail.log anymore. Any ideas why this could be? Here's our setup: OSX 10.3.9, Communigate 4.2.8, CGPSA 1.4, SA 3.1.3 -- John Hardin KA7OHZICQ#15735746http://www.impsec.org/~jhardin/ [EMAIL PROTECTED]FALaholic #11174pgpk -a [EMAIL PROTECTED] key: 0xB8732E79 - 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- Liberals love sex ed because it teaches kids to be safe around their sex organs. Conservatives love gun education because it teaches kids to be safe around guns. However, both believe that the other's education goals lead to dangers too terrible to contemplate. --- 10 days until The 219th anniversary of the signing of the U.S. Constitution
Re: [Bump] No log to syslog after upgrade
On Thu, Sep 07, 2006 at 09:11:22AM -0700, John D. Hardin wrote: [server]spamassassin --lint -D [22110] dbg: logger: adding facilities: all [22110] dbg: logger: logging level is DBG snip Is your syslog daemon configured to discard debug-level messages? [...] At last check, spamassassin doesn't log to syslog. spamd does. -- Randomly Generated Tagline: ... advise the users that although it can help, they are known problems ... - Stanislav Meduna pgpUOy6qk5iRG.pgp Description: PGP signature
RE: [Bump] No log to syslog after upgrade
| From: Theo Van Dinter [mailto:[EMAIL PROTECTED] | On Thu, Sep 07, 2006 at 09:11:22AM -0700, John D. Hardin wrote: | [server]spamassassin --lint -D | [22110] dbg: logger: adding facilities: all | [22110] dbg: logger: logging level is DBG | snip | | Is your syslog daemon configured to discard debug-level messages? | [...] | | At last check, spamassassin doesn't log to syslog. spamd does. And that seems a bit silly, doesn't it? Or was there a good reason for that decision? Perhaps an invocation flag could be added? Kurt
Re: [Bump] No log to syslog after upgrade
On Thu, Sep 07, 2006 at 01:26:08PM -0700, Kurt Buff wrote: Perhaps an invocation flag could be added? You can feel free to open an enhancement BZ ticket if you like. Generally speaking commandline tools don't log to syslog though. -- Randomly Generated Tagline: If ignorance is bliss, why aren't more people happy? pgp3obpzE1wDb.pgp Description: PGP signature
RE: [Bump] No log to syslog after upgrade
I've requested an account, and am waiting for the password. I understand about command line tools and their use, but SA is a bit of a special case, as it's used as more than simply a command line tool - especially when you consider its use with Amavis, etc. Kurt | -Original Message- | From: Theo Van Dinter [mailto:[EMAIL PROTECTED] | Sent: Thursday, September 07, 2006 13:32 | To: users@spamassassin.apache.org | Subject: Re: [Bump] No log to syslog after upgrade | | | On Thu, Sep 07, 2006 at 01:26:08PM -0700, Kurt Buff wrote: | Perhaps an invocation flag could be added? | | You can feel free to open an enhancement BZ ticket if you like. | Generally speaking commandline tools don't log to syslog though. | | -- | Randomly Generated Tagline: | If ignorance is bliss, why aren't more people happy? |
RE: [Bump] No log to syslog after upgrade
Entered as # 5093. | -Original Message- | From: Kurt Buff | Sent: Thursday, September 07, 2006 14:27 | To: users@spamassassin.apache.org | Subject: RE: [Bump] No log to syslog after upgrade | | | I've requested an account, and am waiting for the password. | | I understand about command line tools and their use, but SA | is a bit of a | special case, as it's used as more than simply a command line tool - | especially when you consider its use with Amavis, etc. | | Kurt | | | -Original Message- | | From: Theo Van Dinter [mailto:[EMAIL PROTECTED] | | Sent: Thursday, September 07, 2006 13:32 | | To: users@spamassassin.apache.org | | Subject: Re: [Bump] No log to syslog after upgrade | | | | | | On Thu, Sep 07, 2006 at 01:26:08PM -0700, Kurt Buff wrote: | | Perhaps an invocation flag could be added? | | | | You can feel free to open an enhancement BZ ticket if you like. | | Generally speaking commandline tools don't log to syslog though. | | | | -- | | Randomly Generated Tagline: | | If ignorance is bliss, why aren't more people happy?
Re: [Bump] No log to syslog after upgrade
Kurt Buff wrote: I've requested an account, and am waiting for the password. I understand about command line tools and their use, but SA is a bit of a special case, as it's used as more than simply a command line tool - especially when you consider its use with Amavis, etc. amavisd-new has its own logging facilities including the option to log to syslog or a separate log file. There is also an option to log debugging output from SA. You should ask on the amavis list if you need more details.
