-=-=-=-=-=-=-=-=-= Netscape Messenger Strange Bug =-=-=-=-=-=-=-=-=-=

Program Name: Netscape Messenger
Version: Netscape Communicator 4.74
Company: Netscape Communications Corp.

Bug description:

	While writing IntHook2 ( a proggie which hooks gethostbyname,
send and recv ), I was trying to hook send after successfully hooking
gethostbyname... 

	For testing purposes, I tried to send an e-mail using Netscape
Messenger OFFLINE... ( the winsock hooker is running ) Of course, the
mail goes to no where, because we know very well that after Messenger
( or any mail program ) will call gethostbyname("smtp.whatever.com"),
and fails. So, logically, the mail program should never call send,
since it will fail anyway.

	Well, the reality is: my winsock hooker recorded the following:
.
.
.
smtp.abcdef.com			<---- The SMTP server
Sent: QUIT			<---- The ugly sent data
.
.
.

	If you are familiar with SMTP (Simple Mail Transfer Protocol),
the "QUIT" is the last command to be sent to the SMTP server. It means
that the send mail operation is completed.

	Now, the problem is: the stupid "QUIT" can't be sent to anywhere!
It is like a letter with no postage and no address - the post office kicks
it back to you... Why does Netscape Messenger call send? Obviously, it is
a bug that will never crash your system... It is an 'unintentional
feature' instead, if we want to be nice when using words... :)

	Is there an explanation for this? Or am I wrong? Let's hope that
Netscape corrects this, or if I am wrong (very unlikely), please tell me
the reason behind the notorious 'send'. :)

Author: OCY
e-mail: chuonyuen_ooi@yahoo.com
home: http://www.geocities.com/chuonyuen_ooi/


