On Fri, 27 May 2005, Philip Hazel wrote: > On Thu, 26 May 2005, Matthias Menk wrote: > > > The problem is that if someone sets the header to just allow delivery > > over TLS and the corresponding host doesn't support TLS I get an > > error "a TLS session is required for XXXX, but the server did not offer > > TLS support". Which is fine so far. BUT as soon as someone then wants to > > send a mail NOT using TLS, the host is still waiting for the next retry. > > The retry logic was invented a very long time ago, before TLS support > was even contemplated. It is not flexible enough for this.
How about a tls_failed retry error code, like the existing auth_failed error code? Tony. -- <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> http://dotat.at/ ${sg{\N${sg{\ N\}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}}\ \N}{([^N]*)(.)(.)(.*)}{\$1\$3\$2\$1\$3\n\$2\$3\$4\$3\n\$3\$2\$4}} -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
