Gmail IMAP Problem

[Pete Holsberg]

I manually set up a gmail IMAP account for a friend using TB 2.0.0.24
and did the same thing on my computer as a test.

THE SETTINGS ARE IDENTICAL. REALLY!

Server Type: IMAP Mail Server
Server Name: imap.gmail.com Port: 143
Usename: name

Security Settings
Use secure connections -- NEVER
DO NOT use secure authentication.

I connect to his machine (in NC) via LogMeIn and try to get email. TB
says, "imap.gmail.com is not an IMAP4 server"

No probs on my computer (in NJ).

Could LogMeIn be somehow causing the problem? Or ????

Thanks.

--
Pete Holsberg
Columbus, NJ

Whether you think you can or think you can't, either way you are right.
- Henry Ford

[Mike Rocket J Squirrel]

Pete Holsberg wrote:
> I manually set up a gmail IMAP account for a friend using TB 2.0.0.24
> and did the same thing on my computer as a test.
>
> THE SETTINGS ARE IDENTICAL. REALLY!
>
> Server Type: IMAP Mail Server
> Server Name: imap.gmail.com Port: 143
> Usename: name
>
> Security Settings
> Use secure connections -- NEVER
> DO NOT use secure authentication.
>
> I connect to his machine (in NC) via LogMeIn and try to get email. TB
> says, "imap.gmail.com is not an IMAP4 server"
>
> No probs on my computer (in NJ).
>
> Could LogMeIn be somehow causing the problem? Or ????
>
> Thanks.
>
>

Hi Pete, on my XP machine I run logmein and TB with a gmail IMAP account
and have not had that problem -- TB+gmail IMAP is very dependable.

But I am not unfamiliar with the error you're seeing. Here, if the
computer has not connected with the access point or network before TB
tries to connect to the IMAP server, I'll see that message. It's not
helpful here, because something like "Could not connect to
imap.gmail.com" would be more to the point than saying the problem is
that imap.gmail.com is not an IMAP server.

So maybe TB is not actually able to connect to gmail for some reason?
Firewall or something, maybe. Someone here might be able to provide some
advice on how to narrow down the problem.

--
Mike "Rocket J Squirrel"
Bend, Oregon

[John H Meyers]

On 4/17/2010 8:39 PM, Pete Holsberg wrote:

> I manually set up a gmail IMAP account for a friend using TB 2.0.0.24
> and did the same thing on my computer as a test.
>
> THE SETTINGS ARE IDENTICAL. REALLY!
>
> Server Type: IMAP Mail Server
> Server Name: imap.gmail.com Port: 143
> Usename: name
>
> Security Settings
> Use secure connections -- NEVER
> DO NOT use secure authentication.

> No probs on my computer (in NJ).

I doubt that you got imap.gmail.com (74.125.95.109)
to respond on port 143.

Visit: http://mail.google.com/support/bin/answer.py?answer=78774
where you will see:

> Have you enabled IMAP in Gmail?
> Did you enable SSL for the IMAP server?
> Make sure SSL is active for IMAP in your mail client.

Visit: http://mail.google.com/support/bin/answer.py?answer=78799
where you will see:
> settings: imap.gmail.com, SSL:yes, Port: 993

Visit: http://mail.google.com/support/bin/answer.py?answer=77662
(instructions for TB2, agreeing with the above)

--

[Wilf]

Pete Holsberg wrote:
> I manually set up a gmail IMAP account for a friend using TB 2.0.0.24
> and did the same thing on my computer as a test.
>
> THE SETTINGS ARE IDENTICAL. REALLY!
>
> Server Type: IMAP Mail Server
> Server Name: imap.gmail.com Port: 143
> Usename: name
>
> Security Settings
> Use secure connections -- NEVER
> DO NOT use secure authentication.
>
> I connect to his machine (in NC) via LogMeIn and try to get email. TB
> says, "imap.gmail.com is not an IMAP4 server"
>
> No probs on my computer (in NJ).
>
> Could LogMeIn be somehow causing the problem? Or ????
>
> Thanks.
>
>

Gmail IMAP works for me using imap.gmail.com and port 993 SSL. I didn't
think gmail allowed ordinary connections via port 143.

--
Wilf

[Pete Holsberg]

Wilf has written on 4/18/2010 4:45 AM:

It had been, but changing my friend's computer to 993/SSL worked.

Thanks.

--
Pete Holsberg
Columbus, NJ

Senility Prayer
God grant me the senility to forget the people I never liked anyway,
the good fortune to run into the ones that I do,
and the eyesight to tell the difference.

[John H Meyers]

On 4/18/2010 4:45 AM:

> [Gmail] had been [working for me using imap.gmail.com on port 143]

In that case, you can somehow do from New Jersey
what can not be done from Iowa -- perhaps we should file
a discrimination suit against Google, for violating "net neutrality" :)

> but changing my friend's computer to 993/SSL worked.

As following the specific instructions of a server owner often does :)

http://mail.google.com/support/bin/answer.py?answer=77662

--