Jason Webb wrote:
> I need to develop a system to force mail delivery of certain domains
> to go to certain hosts.
> RemoteDelivery would be enhanced to support the following extra config
> directives (for example):
> SMTP routes would take priority over all other forms of mail host
> resolution including gateways.
> If this is generally useful I will roll it into James proper.
-1 on the ground that it seems to a be hardcoded hack with limited benefit.
I do offer an alternative solution, below. As Serge noted:
> All we do is add an extra configuration or two with a matcher on the
> special domains and a RemoteDelivery mailet setup to gateway to that
> host. Works fine as is. Do you need a large set of mappings?
So, yes, you could do it with matcher and mailet pairs. It is not
data-driven (the configuration is hardcoded), but neither was your solution.
And it also has the overhead of another matcher and mailet for each mapping.
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.
Thoughts?
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
