Gary Dale <[email protected]> writes: > /home/garydale# exim -v -M 1YY9QG-0006Yj-AV > delivering 1YY9QG-0006Yj-AV > R: smarthost for [email protected] > T: remote_smtp_smarthost for [email protected] > Transport port=25 replaced by host-specific port=465 > Connecting to sunspot.dnchosting.com [199.7.109.2]:465 ... connected > LOG: MAIN > Remote host sunspot.dnchosting.com [199.7.109.2] closed connection > in response to initial connection > LOG: MAIN > == [email protected] R=smarthost T=remote_smtp_smarthost defer > (-18): Remote host sunspot.dnchosting.com [199.7.109.2] closed > connection in response to initial connection > > The autoconfigure file contains the line tls_on_connect_ports = 465 and
This changes the listen port behaviour (Exim as a server), not the client behaviour. > .ifndef DCsmarthost > DCsmarthost=web002.dnchosting.com::465 > .endif If protocol = smtps is set in the remote_smtp_smarthost transport, the port number needn't be specified. The above log suggests that it isn't, please check it again. You could also tcpdump the traffic to make sure it's doing TLS on connect. Please show us the section starting by "remote_smtp_smarthost:" in the file named by exim4 -bP configure_file. > exim -bP transports seems to hang. It's been several minutes and it's > not completed. That's unexpected. Try strace to find out what it's waiting for. -- Feri. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
