Hi,
On Thu, May 06, 2010 at 01:25:11PM +0200, Karl Fischer wrote:
> Am 06.05.2010 10:20, schrieb Ron White:
...
> How about a different approach? Have you looked at syslog-ng?
> Having exim write to syslog and having syslog-ng write to SQL DB might
> be it ...
>
> see: http://www.balabit.com/network-security/syslog-ng/
or
http://wiki.rsyslog.com/index.php/EximAmalgamatedLog
Negative point to all these approaches (exilog and similar ones
as well): Every single user needs to maintain the rules and
pattern and will never be sure to have the complete logging
until a detailed and complete walk through the exim logging-code
and the pattern provided by the log-project in question.
The code-walk is to be repeated with every new exim version.
A centrally maintained/supported solution (interface/lib/module
or at least log format documentaion) would be preferred.
--
Regards
Frank
