Bug 3464 - Logging in spamassassin script
Summary: Logging in spamassassin script
Status: NEW
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: spamassassin (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other Linux
: P5 enhancement
Target Milestone: Future
Assignee: SpamAssassin Developer Mailing List
: 5093 (view as bug list)
Depends on:
Reported: 2004-06-03 08:04 UTC by sehh
Modified: 2006-09-08 11:09 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 sehh 2004-06-03 08:04:49 UTC
We would appriciate it, if the 'spamassassin' script supported similar
logging facilities as spamd/spamc do. This is due to some hosting services
and administrated servers which do not allow daemons to run like spamd.

This is per request from email in spamassassin-users list:

"I don't believe there's syslog support in the spamassassin script. It
could be added, preferably in 3.1.x (it's too late for inclusion in
3.0.x.) First we'd need an RFE in Bugzilla, then a patch..."

It is vital to support logging in a custom log file in the users home
dir since in most cases there won't be any root access.

Thank you.
Comment 1 Daniel Quinlan 2005-03-30 01:08:25 UTC
move bug to Future milestone (previously set to Future -- I hope)
Comment 2 Daniel Quinlan 2005-04-29 02:15:36 UTC
This is more feasible now that logging has been rewritten for 3.1, but it won't
happen until 3.2 -- probably with the replacement command for "spamassassin" if
we manage to rewrite it.
Comment 3 Theo Van Dinter 2006-09-08 18:09:24 UTC
*** Bug 5093 has been marked as a duplicate of this bug. ***