Re-use existing patterns; I like apache's dictionary approach. - so establish the indicators for imap, pop, delivery, timsieve sessions that are of interest. - add a session-global dictionary that keeps track of the session data - define custom-log directives in the config-file - write a single line at each session's end that follows the specified log-format - allow writing to syslog, a pipe or a file.
As long as the basic datasets are rich enough, that will produce all you'll ever need. Blake Mitchell wrote: > It seems there is a lot of differing opinion about logging, what should > be included, storage format, etc. So perhaps the way to go is abstract > out the logging, like the database layer has been. This way custom > loadable logging modules could be created by folks with custom logging > requirements. Certainly not as simple as: "Paul and Aaron make it like I > want. :-D" But perhaps a better solution for all. > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
