Re: [exim-dev] TLS on connect for remote_smtp transport [PAT…

Top Page
Delete this message
Reply to this message
Author: Andreas Metzler
Date:  
To: exim-dev
Subject: Re: [exim-dev] TLS on connect for remote_smtp transport [PATCH]
On 2009-08-22 Arnold Metselaar <arnold.metsel@???> wrote:
> Op zaterdag 22 augustus 2009, schreef Andreas Metzler:
> > Hello,
> >
> > gmail does not require tls_on_connect afaict, it suports
> > STARTTLS.
> >
> > ametzler@argenau:~$ swaks -tls -q helo -s smtp.gmail.com
> > === Trying smtp.gmail.com:25...

[...]

> I only get:
> $ swaks -tls -q helo -s smtp.gmail.com
> === Trying smtp.gmail.com:25...
> *** Error connecting 0.0.0.0 to smtp.gmail.com:25:
> ***     IO::Socket::INET: connect: timeout


> I think it depends on the originating ip-address.


Your internet access provider blocks outgoing connections to port 25.

> Apparently other mailhosts can use port 25 and STARTTLS,
> while 'ordinary' gmail users must use tls on connect and port 465
> or 587.


465 is TLS on connect. gmail provides STARTTLS on 587.

ametzler@argenau:~$ swaks -tls -q helo -s smtp.gmail.com -p 587
=== Trying smtp.gmail.com:587...
=== Connected to smtp.gmail.com.
<- 220 mx.google.com ESMTP l12sm772238fgb.11
-> EHLO argenau.downhill.at.eu.org
<- 250-mx.google.com at your service, [62.47.245.143]
<- 250-SIZE 35651584
<- 250-8BITMIME
<- 250-STARTTLS
<- 250-ENHANCEDSTATUSCODES
<- 250 PIPELINING
-> STARTTLS
<- 220 2.0.0 Ready to start TLS
=== TLS started w/ cipher RC4-MD5
~> EHLO argenau.downhill.at.eu.org
<~ 250-mx.google.com at your service, [62.47.245.143]
<~ 250-SIZE 35651584
<~ 250-8BITMIME
<~ 250-AUTH LOGIN PLAIN
<~ 250-ENHANCEDSTATUSCODES
<~ 250 PIPELINING
~> QUIT
<~ 221 2.0.0 closing connection l12sm772238fgb.11
=== Connection closed with remote host.

cu andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'