Justin Mason <[EMAIL PROTECTED]> wrote: > Matt Kettler writes: > > No, at present there's no way to defeat spamd's use of syslog. > > > > Really, spamd is intended to be a system daemon. It's not > > intended to be a "restricted to one user" tool. > > ...and, actually, in 3.0.0 you can log to file or to stderr.
Even in 2.63 you can use "spamd -s stderr" to log to stderr. It's what those of us who run it under daemontools generally do (redirecting then to stdout, which gets handled by multilog). So the original poster should be able to redirect it from there to a file. -- Keith C. Ivey <[EMAIL PROTECTED]> Washington, DC
