Author: jori.hamalainen Date: To: exim-users Subject: [exim] Best way to pass information between message and its' bounce
Hi all,
when messages come in I set certain acl_m_* -variables at ACL to message.
Now if next hop is permamently denying the relay, so I get bounce message written by template.
My experiment shows me that I cannot access original message acl_m_ -variables. I'd like to use those in generation of bounce message. Naturally I acknowledge that I can access original message's headers. But transferring variable data through headers (headers_add in ACL&router and headers_remove in transports) seems to be non-optimal, and I am not quite sure if I use headers_add in router to add header, if I can refer to it at bounce template.
--
Also can I set variables in routers? My skill of RTM does not help me on that. Naturally variables are called _ACL_m which hints where to set those. What if I want to generate counter for example how many times message is tried to be routed or set variable for next router in line? Or something similar.
--
Third, can there be global exim variables with access from /proc or by signal? Those could be used for easier SNMP monitoring instead of crude parsing log by intervals. For example $stats_exim_deny, $stats_exim_accept, $stats_exim_transport etc... So counter for every ACL 'verb' (accept, log, deny, drop,...) and also for transport (how many gone out successfull or how many delayed, bounced etc) and perhaps something how many msgs we have in queue (this last one might be a bit trickier as listening daemon does not list the queue?).
Have I missed some obvious FAQ answers on my questions?
