On Tue, Jun 22, 2004 at 12:26:12PM +0200, Matthias Andree wrote:
Sam Varshavchik <mrs...@courier-mta.com> writes:
I would try to determine the owner of the maildrop process,
The owner of the maildrop process is the userid the message is being
delivered to.
I can see two solutions without knowing off-hand if maildrop implements
either already:
1. offer to run a separate (and possibly restricted) configuration file
BEFORE dropping privileges when setuid-root
2. offer to log into a command instead of a file. That might then be
setgid and be as simple as a read and a write.
3. implement syslog type logging in mailfilters. (#2 could provide this
functionality using the logger(1) program but would be more CPU/disk
intensive.)
4. Create a FIFO and set that as your logfile, then have a program
drain the FIFO into a seperate logfile. (Not much different than
just logging to a file but you could put some smarts into the
draining program, disk usage limits and whatnot.) Heck, you could
even have the drainer dump to syslog.