Hi,
On Tuesday 15 March 2005 09:44, you wrote:
Can explain me better... What is RTMF? HowCourier-IMAP use courierlogger?
Well, first of all, I meant myself with RTFM (Read the Fine manual), because
right on the first page of the manpage for courierlogger it reads:
facility=subsystem
Use subsystem for classifying messages.
How can I set the facility type whose curierlogger must use?
I've looked into this a little deeper and this isn't as easy as it seemed at
first. Because courierlogger is execl'd by couriertcpd with only one argument
allowed, and this argument must not start with a dash (-), or else
courierlogger assumes that it is started in standalone-mode and then
complains about the missing -name-option. But since there's only one argument
allowed that must not start with a dash, your're stuck.
I'ld even happy If I can separate mail logs from courier-IMAP logs? Then,
If I could separate Corier IMAP logs per protocol, It would be the best? ;)
This can be done if you tell couriertcpd not to log to courierlogger, but to a
logfile. For this you have to edit the startup-scripts of your daemons
(courier-imapd, courier-pop3d and so on). Somewhere in the start-function it
reads:
${exec_prefix}/sbin/couriertcpd -address=$ADDRESS \
-stderrlogger=/usr/sbin/courierlogger \
-stderrloggername=imapd \
You have to replace -stderrlogger and -stderrloggername with only one option:
-stderr=/path/to/logfile
For each daemon you can specify a separate logfile. That would give you what
you want, BUT: this has one (major) drawback: There will be no timestamps in
your logfiles since those are added by the syslogger...
If this is a problem, you're back to square one: Use an alternative
syslog-daemon like metalog or syslog-ng.
6 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Courier-IMAP logs
