Wietse Venema:
> Ralf Hildebrandt:
> > * Viktor Dukhovni <postfix-users@postfix.org>:
> >
> > > It is far easier to enable fast delay notices, or set a very short
> > > maximal queue lifetime if fast failure is more appropriate than
> > > eventual success for the messages being sent.
> >
> > Yes, but the delay notice is (probably!) too cryptic for the end-user.
>
> Nonsense. It is the exact same error message that you want Postfix
> to send in a bounce email.
The error mesage being one of:
TLS is required, but host %s refused to start TLS: %s
TLS is required, but was not offered by host %s
TLS is required, but our TLS engine is unavailable
%s: TLS is required but unavailable, don't know why
TLS is required, but unavailable
Cannot start TLS: handshake failure
If you are concerned about confusing error messages, making the
soft error hard is obviously not sufficient. You will also need to
massage the error message text. That requires a filter for error
messages that I already alluded to in my early analysis.
Come to think of it, it is no extra effort to apply this to all
error messages, not just the SMTP client. Just hook into the code
at a lower level in the function-call hierarchy.
Wietse
