> ... >> 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.
Well, syslog-ng is a syslog replacement and therefore logs everything it gets, so nothing gets lost ... ... however, to /interpret/ the content of the logging you need to define your own rules and patterns, that's right. > A centrally maintained/supported solution (interface/lib/module > or at least log format documentaion) would be preferred. I definitely wouldn't mind having that! Is it Christmas already? - Karl -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
