On Mon, 2004-06-21 at 20:56, David Relson wrote:
Hi,
I've been running postfix+procmail on my mail server. Since a friend
has recommended using maildrop, I thought I'd give it a try. Naturally,
I ran into a snag almost immediately.
This seems almost like a hole in procmail - it sounds like it is opening
the log before it drops the root permissions in favor of the permissions
of the delivering user. If, in fact, it is doing that as opposed to
trying to be sure it does nothing it is supposed to not do.
In any case, the Unix "solution" for logging is syslog. Syslog allows
you to take messages from any source, sort them by import and general
type, and then put them in files, forward them to other systems, scream
and shout, or drop them on the floor.
It seems that syslog logging would be a good addition to maildrop.
Something as simple as
logfile syslog logclass logimport
To set the logging target to syslog, specify the class, and specify the
default import.
It might be nice to have a verb added to syslog - if the first "word" in
the logged statement matches a standard import level it is used as an
import instead of part of the line.
18 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] replacing procmail wi...
