Bug 2623 - Request: spamd to have logging levels
Summary: Request: spamd to have logging levels
Status: RESOLVED WORKSFORME
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamc/spamd (show other bugs)
Version: unspecified
Hardware: Other other
: P5 enhancement
Target Milestone: Future
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-23 06:31 UTC by Jesus Climent
Modified: 2021-04-18 09:46 UTC (History)
1 user (show)



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description Jesus Climent 2003-10-23 06:31:06 UTC
For each message checked, spamd logs four lines:

|connection from localhost [127.0.0.1] at port 33426
|info: setuid to kimiko succeeded
|processing message <xx@xx> for kimiko:101.
|identified spam (6.2/5.0) for kimiko:101 in 0.7 seconds, 157816 bytes.

The first one (connection from) is not useful since I only accept
connections from localhost and the port is a random one anyway.
The second one (setuid) is also not useful, unless the setuid failed.
I don't want to see a succesful setuid for every message, only the
ones for which it fails.
The third line (processing) is also not useful. Of course the message
is being processed. If it wasn't, spamd wouldn't function.
Only the last line (identified spam or clean message) is useful, but
even there, I don't really need the time it took to process the
message or the user #.

In summary, I'd like to see an option added to spamd to limit its log
output to the bare minimum: spam/ham & user, with score & length
being optional. Only when things go wrong (failed setuid or message
too long, or whatever) should it log more than that.

Kimiko
Comment 1 Daniel Quinlan 2004-10-25 09:12:36 UTC
We could do this via the info() vs. dbg() distinction if logging was
consolidated.
Comment 2 Daniel Quinlan 2005-03-30 01:08:20 UTC
move bug to Future milestone (previously set to Future -- I hope)
Comment 3 Henrik Krohns 2021-04-18 09:46:56 UTC
Closing old stale bug, logging is already improved.