On 14/03/15 11:08 AM, Jörg-Volker Peetz wrote:
Perhaps. I read it as my exim4 client connecting to a poorly-configured remote smarthost.Gary Dale wrote on 03/14/2015 15:46:On 14/03/15 09:34 AM, Jörg-Volker Peetz wrote:Gary Dale wrote on 03/14/2015 06:00: <snip>I did add tls_on_connect_ports = 465 to exim4.conf.localmacros, which is supposed to cover the SSL on connect issue.Besides the dc_smarthost addition "::465", I added protocol = smtps in the "transport/30_exim4-config_remote_smtp_smarthost" section and didn't change "tls_on_connect_ports". Don't know if this works when adding it in "exim4.conf.localmacros" (maybe you try that first?). Also, don't forget to add an appropriate entry in "passwd.client".Ignore previous e-mail. It didn't work. Tried it with and without the tls_on_connect_ports line in local_macros.As far as I understand the documentation, tls_on_connect_ports regards clients connecting to your exim4 server.
I considered that (previous experience with google) and used *.com in the passwd.client line since I just have the one server I'm connecting to.Also, the entry in passwd.client would be the same as for the unencrypted connection, unless I'm missing something.Take a look into the log file. In my case the server exim4 tries to connect to, does answer with another server name than the one given in dc_smarthost. I therefore added a line with the name of the responding server and same username and password.