<strong>Maildrop Logging</strong>
<A HREF=">Patrick McDonald came up with a good way of setting up Maildrop's logging to use multilog. His Maildrop with multilog page details the installation as well as why he did it this way:

Maildrop provides a logging functionality. This functionality allows you to log what actions maildrop is taking with your messages and where you want it to write. There are a couple of problems with the maildrop logging functionality. First, there is no means to limit the size of the log file. This means the logfile could grow to fill the partition and/or filesystem. Second, it does not possess the ability to rotate files by criteria. Programs such as logrotate while capable of handling these problem, do not posses an automatic restart capability and are not OS agnostic.

Patrick's method requires creating a logger service using a named pipe and having maildrop log to the named pipe. For the purposes of this example, the named pipe will be "/tmp/log-maildrop". To create the maildrop-logger service:

Create the symbolic link to start the service:

Wait about 10 seconds then confirm that the service is running:

To really confirm that it is running, in one shell window, watch the maildrop-logger log file:

In another shell window, echo some text onto the named pipe /tmp/log-maildrop. You should see the text in the service log: