Hm. Where do you need to stich them together when they have unique queue IDs? That's pretty straight forward with almost every logging stack available and a hundred of different patterns plus a rock solid MTA. :) And: every single component is free.
> Am 20.11.2020 um 16:45 schrieb Maarten Oelering via mailop > <[email protected]>: > > > We have built integrations with many MTA’s and SMTP services. I would rather > see all information available in the logs of the Exim, than a common scheme > provided by all MTAs. > It would also be helpful is the logs report on “transaction” level (deferral, > bounce, delivery) and not on process level like Postfix where you need to > stitch log lines together to get the full context. > An example of an MTA with JSON logs (in NDJSON format) is PowerMTA: > https://www.sparkpost.com/docs/tech-resources/pmta-50-features/ > > Maarten > >> On 20 Nov 2020, at 09:01, Andrew C Aitchison via mailop <[email protected]> >> wrote: >> >> >> The has been a request for Exim to have the ability to save the >> server mainlog in json format 'to make it easier to "consume" it' >> https://bugs.exim.org/show_bug.cgi?id=2610 >> >> The developers would like to use a "standard" schema; >> does anyone use or know of a JSON schema for mail servers logs ? >> >> Thanks, >> >> -- >> Andrew C. Aitchison Kendal, UK >> [email protected] >> _______________________________________________ >> mailop mailing list >> [email protected] >> https://list.mailop.org/listinfo/mailop > > _______________________________________________ > mailop mailing list > [email protected] > https://list.mailop.org/listinfo/mailop
_______________________________________________ mailop mailing list [email protected] https://list.mailop.org/listinfo/mailop
