Jeff Abrahamson:
> On 04/06/18 22:34, Greg Strange wrote:
> > Hi,
> >
> > I am trying to track a single email throughout the entire postfix
> > process. The idea is that when a customer calls us and says that a
> > certain email never reached them, we can quickly trace the email
> > through the logs and see that it died due to RBL, virus threshold, etc.
> >
> > Ideally, I'd like to be able to get or set a unique message ID and
> > then be able to match that ID in the logfiles to see what the outcome
> > of a specific email was. Is there a way to trace a single email
> > through everything postfix does to it?
>
> We want to do the same thing.? The current candidate is to use logwatch
> to gather the information and forward to a database where we post-process.
>
> The project hasn't quite made it high enough on the priority list to get
> implemented yet.? If you do something, please do report back to the list
> how it works out.
>
> (In passing, email message id's may be considered to contain PII.?
> IANAL, just a techy heavily bombarded by GDPR mails of late.)
This could build on the "collate" tool, which groups Postfix log
records one "session" at a time based on queue ID and process ID
information.
This tool ships with Postfix source code as:
auxiliary/collate/collate.pl
auxiliary/collate/README
Wietse
