Configurable sender address

The way I am using integrations to produce better alerts from LM would solve this problem as well.  The general strategy I have settled on is to submit all the tokens via email into our helpdesk (this has caused issues because the tokens available are not actually the best tokens for certain requirements, which I am still struggling with).  The raw input is processed by a template system, into which all the tokens are available as template variables, and the layout driver produces the desired output.  A procmail recipe filters the original message into a properly formatted final message with context-sensitive data added, conditional formatting, etc., and that is routed into the helpdesk.  The alertid value is used to keep related messages in the same incident.

I can influence behavior of the helpdesk (RT in our case) via instructions in headers (stripped from the raw input to avoid security problems), so an alertstatus of "clear" will trigger a ticket autoclose, for example.  By including suitable properties, the behavior you describe could be achieved via properties set within each customer top-level (also sent via the raw token list in the integration definition) -- you would simply override the From address in your headers template based on the customer-specific properties.  So far, the results have been quite promising, but I am still in the early phase of development.  Something like this could potentially work for you, but I imagine the integration method would be significantly different.

Regards,

Mark