On Fri, 27 May 2005, Tony Finch wrote: > > 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?
That would not help! It would just allow you to set a different retry time, but for the same host. If, for example, you set it to 1 minute, you would get a retry 1 minute after a TLS failure for that host - whether you were trying a TLS connection or not - and after a non-TLS failure you would get a retry 15 minutes later (assuming normal retry rules) - whether you were trying a TLS connection or not. What is needed is two different retry times, not two different rules. So Exim could know to "wait 15 minutes before attempting a TLS connection" and "go right ahead with a non-TLS connection" simultaneously. (Though having that error code is - orthogonally - not an unreasonable idea.) -- Philip Hazel University of Cambridge Computing Service, [EMAIL PROTECTED] Cambridge, England. Phone: +44 1223 334714. Get the Exim 4 book: http://www.uit.co.uk/exim-book -- ## 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/
