Instead, I propose that we add an attribute that RemoteDelivery will check, for the purpose of adding dynamic gateway support. If the attribute is present, RemoteDelivery treats it as the gateway for that Mail, otherwise RemoteDelivery operates as normal. A single mailet could check for mappings, and add the attribute as necessary. This would be a very simple change to RemoteDelivery, allows a data driven solution, and is far cleaner, at least in my mind.
I rather dislike this overloading approach to mailet configuration. I think you'll soon end up with another Redirect mailet that few understand and is trying to be another Swiss army knife.
-- Serge Knystautas President Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
