176484 - Mail fails to connect to server ("CreateNewLineFromSocket: (null)") w W2K SP3

Status: RESOLVED WORKSFORME

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Cip]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/2002101612

It looks like the mail program can't use the network stack or smth. On a W2K w
SP3 the mail program can not connect to the server (POP3 or IMAP). Dumping
packets from another machine in the same hub, no packets leave to the IMAP
server. On the same machine Outlook connects to the same IMAP server w/o any
problem. True for 1.1 and 1.2b.


Reproducible: Always

Steps to Reproduce:
1.
2.
3.




All the updates from Microsoft were in place.

Comment 1

[Adrian Spermezan]

Happened to me too.
After enabling logging of IMAP component, the log file contained only a line:
264[2046c38]: ravone:NA:CreateNewLineFromSocket: (null)
ravone being the name of host name of the IMAP server.

After many hours of desperation, I discovered that, IF I HAVE NO SOCKS PROXY SET
in Mozilla, it works smoothly. (I had SOCKS v4)
My host, my mail server and the proxy server are all in the same (class C)
network. I have the default settings for "do not use proxy for": localhost,
127.0.0.1
I am using the official Mozilla 1.2.1 Gecko/20021130 on Windows 2000 SP3.

Comment 2

[Mike Cowperthwaite]

Reporter (Cip): Is this bug still an issue for you?  Does comment 1 apply to 
your situation?  If still a problem, have you tried a more recent build of 
Mozilla?

Comment 3

[Adrian Spermezan]

I (author of comment #1) can still reproduce bug with official Mozilla 1.4b for
Windows (Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507)

I use Mozilla as a browser also, so the HTTP/SSL/FTP/GOPHER proxy is set. With
these settings browsing and reading mail using IMAP works ok (the server is a MS
Exchange 2000, if this matters). If I set the SOCKS proxy (leaving also set the
other proxies), is does not work any more. If I remove the SOCKS proxy (leaving
other proxies active), it works again. And so on. It can be reproduced at my
company, at least on Windows 2000 SP3 (my computer) and on Windows .NET Server
(a colleague's computer).

I hope that with this info the bug can be reproduced everywhere and finally
enter its NEW state (and, hopefully even ASSIGNED state) - sorry for not sharing
this in Bugzilla when first happened to me.

Comment 4

[Cip]

Sorry  Mike, I was errr... "convinced" to switch to XP so I can't be of any
help.   Yet I can tell that my issue was not about SOCKS at all (in the W2K
era...). On XP it works ever since.

Comment 5

[Matthias Versen [:Matti]]

wfm on my win2k installation (and comment#3 is a user error)