On 04/02/2013 14:03, Ian Eiloart wrote:
On 28 Jan 2013, at 15:51, plot.lost <[email protected]> wrote:
Is it possible to configure exim to use a specific routing option by setting a
custom header value?
So, for example, within the email headers having something like:
From: [email protected]
To: [email protected]
EximRoute: use.this.server.com
That value would be available as $header_EximRoute.
route_list isn't expanded, so you can't just say "route_list =
$header_EximRoute"
However route_data is expanded, so you might be able to say the following, if
the headers are available
route_data = ${lookup{$header_EximRoute}dbm{/etc/routes}}
Thanks for the info. Is there any way to do this without having to
update any config files (even ones like dbm files) - would like to be
able to have the sending application be able to add new routes as
needed, and it won't be able to make config changes etc.
Where the value in the EximRoute (or whatever header...) would be used as a
manualroute option for this message. It would always only contain a single
server name, and it would always be used as manualroute bydns. The header would
be stripped out before forwarding the message on.
If there are any delivery errors etc causing the message to be queued, then any
retries must still be sent via the specified route.
If no 'EximRoute' header is present, then just route the message as normal.
The exim server would only be accepting requests from a locally running
application, no external access to the server would be possible.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
