[exim-dev] [Bug 3118] Allow a forced-fail for socks_proxy ex…

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Exim Bugzilla
Date:  
À: exim-dev
Sujet: [exim-dev] [Bug 3118] Allow a forced-fail for socks_proxy expansion to connect directly
https://bugs.exim.org/show_bug.cgi?id=3118

Jeremy Harris <jgh146exb@???> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Priority|medium                      |low
          Component|General execution           |Transports
           Assignee|unallocated@???        |jgh146exb@???
   Target Milestone|Exim 4.98                   |Exim 4.99


--- Comment #5 from Jeremy Harris <jgh146exb@???> ---
OK. This demands a bit of shuffling in the implementation, but feels
feasible. A forced-fail won't be required, just a zero-length result
for the expansion.

A wider-coverage alternative would be a fallback-transport, but that would
be far more invasive.

On running using modified code in Exim - I trust you realize that this
destroys any assumptions about how Exim operates, and thereby makes
support a random affair and possibly a total time-waster.

--
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/