On 18/03/15 01:11 PM, Heiko Schlittermann wrote:
> Gary Dale <garydale@???> (Di 17 Mär 2015 16:00:24 CET):
>> 2015-03-17 10:49:17 1YXso1-0004vW-2v <= <sending address> U=root P=local
>> S=785
>> 2015-03-17 10:49:17 1YXso1-0004vW-2v == gary@??? R=smarthost
>> T=remote_smtp_smarthost defer (-53): retry time not reached for any host
> Force a delivery and show us the output
>
> exim -v -M 1YXso1-0004vW-2v
>
> You may even use
>
> exim -d -v -M 1YXso1-0004vW-2v
>
> And, how do you know that your Exim uses SMTPS when talking to the
> remote server on port 465. I do not know anything about the debian style
> of configuration, but the autogenerated config file (check it's name
> with
>
> exim -bP configure_file
>
> should contain references to the remote_smtp_smarthost transport.
> Ideally you can send us the output of
>
> exim -bP transports
>
/home/garydale# exim -v -M 1YY9QG-0006Yj-AV
delivering 1YY9QG-0006Yj-AV
R: smarthost for gary@???
T: remote_smtp_smarthost for gary@???
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
== gary@??? 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
.ifndef DCsmarthost
DCsmarthost=web002.dnchosting.com::465
.endif
exim -bP transports seems to hang. It's been several minutes and it's
not completed.