https://bugs.exim.org/show_bug.cgi?id=3118
--- Comment #2 from Maxim Galaganov <max@???> ---
(In reply to Jeremy Harris from comment #1)
> Just set up suitable conditional choices in routers, pointing to separate
> transports?
The smtp transport docs say "the fallback queue is delivered by re-running the
same transports with the new host lists". There is no way to change the
transport between these two do_remote_deliveries() calls in deliver_message(),
IIUC. So I cannot connect to fallback hosts directly, bypassing the configured
socks_proxy setting on the transport.
The socks_proxy option is expanded each time in socks_sock_connect(). If forced
failure was a possibility then I could just bypass proxying for all internal
networks.
I don't see how a separate transport could help in the above fallback hosts
scenario. Am I missing your point?
Thanks!
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## subscription configuration (requires account):
##
https://lists.exim.org/mailman3/postorius/lists/exim-dev.lists.exim.org/
## unsubscribe (doesn't require an account):
## exim-dev-unsubscribe@???
## Exim details at
http://www.exim.org/
## Please use the Wiki with this list -
http://wiki.exim.org/
