On Nov 29, 2005, at 11:00 PM, Will Leshner wrote:
I think this has come up before, but I'm trying to connect to Gmail
with an SMTSecureSocket and I'm not getting very far. The mail
never gets sent. But I'm also not getting any errors back. Has
anybody successfully connected to Gmail with an SMTPSecureSocket?
To answer my own email, I've looked into this a bit and it would seem
that Gmail's recommendation to use port 587 is part of the problem.
Apparently the "standard" port for doing SSL over SMTP is 465. I am
able to send email if I use port 465. But not reliably. Many times
the connection just doesn't finish. But if I use a vanilla SSLSocket,
I can connect to smtp.gmail.com every time on port 465. So I've
started writing my own SecureSMTPSocket. So far, things look good. I
have a very simple SMTP client that appears to be able to send email
every time. Which suggests that the problem with SMTSecureSocket is
not a problem with SSLSocket itself, but with the SMTP client built
on top of it.
--
REALbasic news and tips: http://rbgazette.com
KidzMail & KidzLog: http://haranbanjo.com
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
|