On 20/06/2009, at 08:29, Chris Lewis wrote:
I do all my logging by a variation of logterse, which logs reasons
and various additional things in addition to what the published
logterse does.
One log line for every email that contains everything there is to
know about the email. Since the reasons are a common format, post-
processing the logs to derive reason effectiveness (right down to
which entry in which config file triggered it) is trivial.
[snip]
I strongly believe that one of qpsmtpd's biggest impediments to
broad deployment is the adhoc/inconsistent nature of the plugin
suite, particularly all the inconsistent configuration directives.
Another thing is the essentially useless logging (the released
qpsmtpd doesn't even include logterse I think).
You can't build an "enterprise level" MTA out of the current plugin
suite. You have to recode them all for consistent behaviour and
construct your own logging. The qpsmtpd _core_, on the other hand,
is just fine as is ;-)
Thanks for the plug for logterse, Chris :-)
Are we perhaps in need of a two-channel logging strategy where all
debug/error messages go to stderr and stdout just logs a [terse :-)]
one-line summary of the transaction?
If that was the case then the logterse functionality could be brought
closer in to the core. I imagine some folks who don't use multilog
might find it a pain to have to extract the logterse lines from the
rest of the info in the log output, so this would help them.
Charles
