I have tracksources set to:
TrackSources spam nonspam virus
Yet only innocent messages are shown. IE:
Jan 15 16:09:28 mail dspam[2837]: innocent message from xxx
Any ideas?
What are the possible options for TrackSources?
-Eric
> Date: Fri, 15 Jan 2010 13:52:13 +0100
> From: [email protected]
> To: [email protected]
> Subject: Re: [Dspam-user] Logging with dspam-3.9.0-rc2
>
> Steve wrote:
> > -------- Original-Nachricht --------
> >> Datum: Fri, 15 Jan 2010 11:29:46 +0000
> >> Von: David Williams <[email protected]>
> >> An: Paul Cockings <[email protected]>
> >> CC: [email protected]
> >> Betreff: Re: [Dspam-user] Logging with dspam-3.9.0-rc2
> >
> >> Paul Cockings wrote:
> >>> If we got them into syslog, what are you wanting to do next? I
> >>> mean... what are you trying to do overall?
> >>>
> >> Hi Peter
> >>
> >> Thanks for the reply.
> >>
> >> My purpose is to make it easier to setup, maintain and debug a whole
> >> system.
> >>
> >> If Dspam logged to syslog I could see the whole processing of emails in
> >> the one mail log. That way I could see that dspam was receiving the
> >> email correctly ,was processing it and either delivering, sending it to
> >> quarantine, or possibly experiencing an error all within the context of
> >> an emails progress through the system.
> >>
> >> Currently I'm using Exim as MTA and Dovecot as IMAP server and LDA, both
> >> of these log to syslog as does Spamassassin so I can see all the log
> >> messages in one place and it's really helpful for spotting problems.
> >>
> >> I realize other people may have other ideas but if it were an option to
> >> send the messages to syslog the the administrator could configure syslog
> >> to send them where desired.
> >>
> > You should look at "TrackSources" in dspam.conf. That's what you want and
> > not system.log (which is btw just a journal).
> >
>
> Information about TrackSources in dspam.conf seems to indicate that it
> is only useful for debugging purposes: to debug the session of an
> already-known sender/receiver. Enabling it with default settings does
> not send any output to syslog for an incoming (innocent) message.
>
> What I would like to see (and I think David means the same) is that
> dspam sends a line to syslog (or to target file of --with-logfile
> configure option) for every activity it does. Currently syslog only
> receives messages upon startup/shutdown, and in case of error.
>
> This could look something like:
>
> dspam[1234]: message received for known user <[email protected]> from
> socket /var/run/dspam/dspam.sock
> dspam[1234]: message processed, tokens=35,
> signature=4b505b5b161107953319323, result=innocent, action=deliver
> dspam[1234]: message for <[email protected]> delivered to DeliveryHost
> 127.0.0.1, result=Sent
>
> Adding some internal id (like queue id in smtp) would be nice, so you
> can find multiple lines that show the complete processing of a message.
> Adding more information depending a new config value
> LogLevel={debug,info,critical}. Currently, dspam behaves as if it only
> logs critical information :)
>
> I agree that contents of system.log and user.log are meant for other
> things, and should be treated separate from this.
>
> --
> Regards,
> Tom
>
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
http://clk.atdmt.com/GBL/go/196390708/direct/01/------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Dspam-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspam-user
