Debugging a TCPSocket.open timeout

I’m trying to do an IMAP connection. My first target is gmail:

Net::IMAP.new(“imap.gmail.com”, 143)

goes walkabout on line 886:

TCPSocket.open(“imap.gmail.com”, 143)

AT&T swears they are not port blocking. My system logs are clean.

The code for TCPSocket is compiled in, so inserting printfs is going to
be really painful. Moreover, the actual error is probably a ways down
the stack.

Ideas?

Student Jr wrote:

The code for TCPSocket is compiled in, so inserting printfs is going to
be really painful. Moreover, the actual error is probably a ways down
the stack.

Ideas?

What about trying netcat? Not sure that will give more info than tcp
open, but if you have to convince someone, it’s better than saying “my
ruby program doesn’t work”.

Joel VanderWerf wrote:

Student Jr wrote:

The code for TCPSocket is compiled in, so inserting printfs is going to
be really painful. Moreover, the actual error is probably a ways down
the stack.

Ideas?

What about trying netcat? Not sure that will give more info than tcp
open, but if you have to convince someone, it’s better than saying “my
ruby program doesn’t work”.

sudo nc -v -v imap.gmail.com 143
DNS fwd/rev mismatch: gmail-imap.l.google.com != py-in-f109.google.com
DNS fwd/rev mismatch: gmail-imap.l.google.com != py-in-f111.google.com

I don’t know what to expect, so I don’t know if this really means
anything or not…

Phillip G. wrote:

Student Jr wrote:
| I’m trying to do an IMAP connection. My first target is gmail:
|
| Net::IMAP.new(“imap.gmail.com”, 143)
|
| goes walkabout on line 886:
|
| TCPSocket.open(“imap.gmail.com”, 143)
|
| AT&T swears they are not port blocking. My system logs are clean.
|
| The code for TCPSocket is compiled in, so inserting printfs is going to
| be really painful. Moreover, the actual error is probably a ways down
| the stack.
|
| Ideas?

Have you followed (well, as much as possible :P) the instructions GMail
provides for configuring email clients for IMAP?

When I used Thunderbird on Ubuntu 8.04 to connect to Google’s IMAP, I
had no problems.

Write clearly - don’t be too clever.

Funny what the infamous “one more look” can do. They are using a
different port. This nicely deals with the immediate example
problem–the long timeout on a bad connection is going to have to be
handled via shelling out anyway, I guess.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Student Jr wrote:
| I’m trying to do an IMAP connection. My first target is gmail:
|
| Net::IMAP.new(“imap.gmail.com”, 143)
|
| goes walkabout on line 886:
|
| TCPSocket.open(“imap.gmail.com”, 143)
|
| AT&T swears they are not port blocking. My system logs are clean.
|
| The code for TCPSocket is compiled in, so inserting printfs is going to
| be really painful. Moreover, the actual error is probably a ways down
| the stack.
|
| Ideas?

Have you followed (well, as much as possible :P) the instructions GMail
provides for configuring email clients for IMAP?

When I used Thunderbird on Ubuntu 8.04 to connect to Google’s IMAP, I
had no problems.


Phillip G.
Twitter: twitter.com/cynicalryan
Blog: http://justarubyist.blogspot.com

Write clearly - don’t be too clever.
~ - The Elements of Programming Style (Kernighan & Plaugher)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkgzIUcACgkQbtAgaoJTgL+99ACdHi40kwAUQkpeD2Vh9qknX737
vbkAoIANsiX0JMD0qlB+Nc7pR9xdZmqr
=5ecP
-----END PGP SIGNATURE-----

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs