On Oct 5, 2008, at 11:18 PM, Tannis Baker wrote:
Sorry, but I hate Mail. Nearly everything about it. Especially the
colour! Pale blue - ew! And I not fond of webmail either.
So don't use Mail, use any other modern email client.
But I do not mind Gyazmail - which I haven't attempted to configure
yet! Can't wait. ;-)
That is one possible choice.
Anyway, the weird thing here, Chris, is that my new ISP absolutely
cannot do SSL - they were adamant about it. And so, when I finally
figured out how to configure Mail to send using [EMAIL PROTECTED],
it was with SSL unchecked. And it works.
See my other emails, but your ISP can't do SSL on *their* mail
server. But you don't care about that if you use gmail's mail server.
If this sending is working, then you almost certainly have the
outbound (SMTP) server for that account set to your ISP's account.
Mail allows you to do this.
So, I doubt that Gmail does require it. That being so, why can't I
configure CE (P3)?
I'm nearly positive at one point they did require it. I know I have
it turned on with my two accounts, and I would not have done so
unless it was required. That doesn't mean they still require it.
Assuming it is not required, then I can't tell you why it doesn't
work with CE-P3. Assuming you have everything set correctly, it
should work. You would use the following settings:
Email Account: [EMAIL PROTECTED]@pop.gmail.com
SMTP Server: smtp.gmail.com
Email Address [EMAIL PROTECTED]
Those would work, assuming gmail supports Login type SMTP
Authentication.
However, I just tried telnetting to smtp.gmail.com (on both 25 and
587) to see if it supports the Login type, and it won't let me do
anything until I initiate an SSL connection. Specifically says you
must issue a STARTTLS command first. STARTTLS does exactly what it
sounds like, it starts a TLS connection. TLS (Transport Layer
Security) is basically a variant of SSL (Secure Socket Layer).
So it really does look like Gmail still requires SSL for sending at
least.
Attempts to telnet to pop.gmail.com on port 110 (the pop port), go
unanswered. Attempts on port 995 (the SSL pop port) are answered but
drop any manual connection attempts I make. That is the result I
would expect for a socket expecting only SSL connections.
So it looks like gmail probably also still requires it for POP as well.
To sum up, it looks like CE will not work with Gmail directly. If you
want to get it to work, see my other posts about how to fake the
return address on an account so things look like they are coming from
your gmail account when they are really from your ISP account.
Otherwise, skip CE and pick a newer mail client that supports SSL
connections and then you can talk directly to gmail.
-chris
<www.mythtech.net>
___________________________________________________________________________
To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to
<[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
