On Tue, Oct 26, 2021 at 09:42:33AM -0400, Wietse Venema <wie...@porcupine.org> wrote:
> Vincent Pelletier: > > On Mon, 25 Oct 2021 12:36:35 -0400 (EDT), > > Wietse Venema <wie...@porcupine.org> wrote : > > > This would require a new setting, for example to make smtp_bind_address > > > failures a retryable error. > > > > > > smtp_bind_address_failure_action = warn (or defer) > > > > > > warn: current behavior > > > defer: treat as a faiilure to connect > > > > This looks like something I would want to use in my situation. Does the > > implementation complexity and maintenance cost look reasonable to you, > > for what seems to be a rather niche use (otherwise someone else would > > certainly have done the same mistake before) ? > > It does not complicate the code. I am more concerned about > discoverability (how would a user even find out that the behavior > has become configurable). > > A popular approach in OSS is to enable incompatible changes by > default. I hate that. > > Wietse I'm sure that Postfix users everywhere are glad that you hate it. Postfix's method for achieving default backwards compatibility by changing default behaviour only explicitly via compatibility_level is superb. As for discoverability, this issue probably doesn't occur often, and when it does, there is a warning message by default. Perhaps the warning could be changed to mention/suggest the new smtp_bind_address_failure_action parameter. cheers, raf
