On Wed, Mar 18, 2015 at 05:45:43PM -0400, Gary Dale wrote:
> Transport port=25 replaced by host-specific port=465
> Connecting to sunspot.dnchosting.com [199.7.109.2]:465 ... connected
This server supports SMTP inside SSL on port 465 (rather than
STARTTLS inside SMTP as generally used on port 587).
posttls-finger: Connected to 199.7.109.2[199.7.109.2]:465
posttls-finger: 199.7.109.2[199.7.109.2]:465: subjectAltName: *.dnchosting.com
posttls-finger: 199.7.109.2[199.7.109.2]:465: subjectAltName: dnchosting.com
posttls-finger: 199.7.109.2[199.7.109.2]:465 CommonName *.dnchosting.com
posttls-finger: Untrusted TLS connection established to 199.7.109.2[199.7.109.2]:465: TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)
posttls-finger: < 220-sunspot.dnchosting.com ESMTP Exim 4.85 #2 Fri, 20 Mar 2015 13:57:48 -0500
posttls-finger: < 220-We do not authorize the use of this system to transport unsolicited,
posttls-finger: < 220 and/or bulk e-mail.
posttls-finger: > EHLO amnesiac.invalid
posttls-finger: < 250-sunspot.dnchosting.com Hello amnesiac.invalid [192.0.2.1]
posttls-finger: < 250-SIZE 52428800
posttls-finger: < 250-8BITMIME
posttls-finger: < 250-PIPELINING
posttls-finger: < 250-AUTH PLAIN LOGIN
posttls-finger: < 250 HELP
posttls-finger: > QUIT
posttls-finger: < 221 sunspot.dnchosting.com closing connection
Is your Exim client configured to use SSL-wrapped SMTP? Does Exim
support this mode of operation as a client?
> Remote host sunspot.dnchosting.com [199.7.109.2] closed connection in
> response to initial connection
My guess is no.
--
Viktor.
