In article <>, Sidney Lambe <(E-Mail Removed)> wrote:
> One more time: You just plug the gmail password and username
> into an ordinary mail client.
>
> The telnet session didn't work because it is an encrypted
> connection. That's what those non-standard ports are about.
> That's what "tls on", "tls_starttls on", and "ssl" in the
> configuration files I posted are about.
>
OK, it's coming back to me: how I had to hack my client
when my ISP added TxAuthorisation, and the ID?passwd
was AFAICR base64 encoded - how dumb.
What I need to confirm is that my existing gmail by http,
will still continue to work, if/when I've had pop access.
So that would mean they access my stuff via http & pop/smtp
servers.
A previous contributor's ref. to:
http://mail.google.com/support/bin/answer.py
?hl=en-GB&ctx=mail&answer=12103
shows:
]Once you've enabled POP in Gmail, you can configure your mail
]client or wireless device to download Gmail messages. To see our
] recommended settings or troubleshoot POP issues, click the name of
] your mail client or wireless device below.
This implies that POP is not automatically enabled;
and probably that enabling it, disables the http-default.
BTW, the:
"I don't know how it works,
but every *normal* guy is doing it,
so it must be OK",
is what got y'all into the economic crisis poop ?
== TIA.