Vikas Rawal wrote:
>
>> From the laptop, what happens when you
>> telnet smtp.gmail.com <http://smtp.gmail.com> 25
>
> telnet smtp.gmail.com <http://smtp.gmail.com> 25
> Trying 66.249.93.109...
> Trying 66.249.93.111...
> telnet: Unable to connect to remote host: Connection refused
>
> But gmail does not only use port 25. It uses port 465 (with ssl) and
> 587 (with tls) as well.
>
> I can telnet to port 465.
>
> telnet smtp.gmail.com <http://smtp.gmail.com> 465
> Trying 66.249.93.111...
> Connected to gmail-smtp-msa.l.google.com
<http://gmail-smtp-msa.l.google.com>.
> Escape character is '^]'.
>
It occurred to me when I wrote the above that my postfix was using
port 587. I have now changed the transport and sasl_passwd files to
point them to port 465. The log now has the following.
Jan 9 05:52:53 panahar postfix/smtp[8128]: 683BC11B785: conversation
with smtp.gmail.com <http://smtp.gmail.com>[66.249.93.109] timed out
while receiving the
initial server greeting
Jan 9 05:53:53 panahar postfix/smtp[8157]: 37F8711B773: conversation
with smtp.gmail.com <http://smtp.gmail.com>[66.249.93.111] timed out
while receiving the
initial server greeting
Any ideas?
Vikas
Postfix doesn't support client connections with the deprecated
SSL wrapper mode, but it's pretty easy to work around with
stunnel.
http://www.postfix.org/TLS_README.html#client_smtps
But rather use TLS on port 587 if your new location allows
connections to that port. Try "telnet smtp.gmail.com 587" and
see if you get connected with the 220 greeting, or a timeout.
If you get a timeout, contact whoever is in charge of the
firewall there.
--
Noel Jones
