Uwe Brauer writes:
BTW even this version only supports starttls, but no ssl?
STARTTLS *is* SSL. See RFC 2487. If Gmail has a different way of
supporting SMTP over SSL, I don't know about it. I suppose you could
have a dedicated port where TLS authentication/privacy negotiation is
done *before* connecting to the mail server, but a quick look doesn't
show any documentation for it.
I am asking, because gmail offers 2 ports for smtp:
- 587 with starttls
- 464 with ssl
Are you sure that's not port 465? The standard port for smtps is
465. This page:
says it's port 465. He also says he's never gotten it to work, nor
have most of the people he knows who have tried. (Scott is a friend
of mine, and quite reliable.)
Port 587 is a different protocol (the mail submission protocol, RFC
2476), which happens to use SMTP for its wire protocol. (Perhaps
that's confusing -- all the new restrictions are on what the receiving
MSA is allowed to do, so it doesn't actually need a new wire
protocol.) That RFC doesn't actually permit use of STARTTLS, but I
guess that's because it was published before 2487 was.
The problem is I have been in places where 587 was blocked and
smptmail did not work!
My commiserations. Seems like a very stupid thing to do to me, but I
don't know what their situation is.
I suspect that they just block *everything* under 1024 (or maybe
everything period) except for a few ports known to have strong
authentication (like 22, ssh) or considered organizationally essential
(like 80 and/or 442, http and https). I doubt they really care about
the difference between 587 and 465 (or 464).
XEmacs-Beta mailing list