24. Apr 2016 09:01 by wie...@porcupine.org: > If someone has the time, they can propose a patch (considering that > this code was written in 1997, I don't see it as an urgent problem). > While they are at it, they might also enforce that the transcript > is sent to the recipient that is configured for the notification > class (and of course do something reasonable when the notification > covers multiple classes). Right now, the Postfix SMTP server and > SMTP client send the transcript to the error recipient, not necessarily > the recipient that is configured for the notification class.
Right now I understand there are only four difference notice recipients. I can do this bounce_notice_recipient = postmaster+bou...@somewhere.tld 2bounce_notice_recipient = postmaster+2bou...@somewhere.tld error_notice_recipient = postmaster+er...@somewhere.tld delay_notice_recipient = postmaster+not...@somewhere.tld But you see that error_notice_recipient gets the email for many different notify_classes. So it it not always clear what the cause is. Im just thinking it could be be useful to have the effect of notify_class_recipient = postmaster+<notify_class> Or maybe better in the Subject or Body just Notify Class: <notify class> I will be sending in time all messages and logs from all servers to an ElasticSearch / LogStash server. When all messages from all servers are merged into the 'master' server, and all messages have the benefit of a very easy way to identify just from reading both the <server> and the <problem>, then its very useful. But yes you can look into the logs for each message to see the cause. Its not as efficient and requires that the reader have the access. I agree although its not urgent.
