87444 - Message send error does not generate an alert box.

Status: VERIFIED WORKSFORME

(MailNews Core :: Composition, defect)

Description

[Dwayne]

Build 2001-06-21-04, Win2k sp2

Recently I haven't been able to send messages at all through Mozilla, because
when I attempt to do so, there's no network activity whatsoever (with throbber
window "Sending..." open).

This also halts all other network activity throughout Mozilla.  In other words,
not a single bit of traffic is sent from my computer through Mozilla.  If I load
up Netscape (before or afterwards), I can still get access.

I've tried closing Mozilla, dropping and re-establishing my connection with
Mozilla still running... nothing seems to help.

At the same time, I've tested this same build on a Win98 machine running off a
LAN and there were no issues.  Strange...

Steps to reproduce:
1. Open MailNews and browser
2. Create a new message, send it out.
3. Try to access any web page through the browser.

Results:
No network activity.  Not a single packet.

Expected results:
Message sends, network activity unaffected.  If there is a connection problem, a
dialog box should appear.

Reproduceability:
100.00%, at least on my machine.

Comment 1

[Dwayne]

Adding keywords 4xp and hang.

(4xp has got to be one of the most useless keywords, honest.  I mean, about 80%
of everything qualifies as 4xp!)

Comment 2

[Dwayne]

Ok, this is weird.  I wrote myself a note to file this bug since I had
reproduced it many times in the past.  So I neglected to test it again today, as
I saw no reason for it.  But now it's sending just fine.

So maybe the orignal problem needs to be narrowed down to some type of error
message that needs to appear and is not.

Changing summary to reflect.  Sorry guys.  And good luck trying to find out what
that network error is!  :)

Comment 3

[Jean-Francois Ducarroz]

Try to turn off SMTP SSL, that should help...

Comment 4

[Dwayne]

Well, I did have this set to "If available" so I'll report back later if I see
it anymore (with it set to "never").

Thanks for the suggestion.

Comment 5

[Sheela Ravindran]

Based on reporters comments marking this bug as worksforme.  Reporter, reopen 
the bug if you encounter this problem again.
I have been able to send messages with 2001062107 build on win98, 
2001062108 linux, and mac trunk builds when SMTP SSL is set to 'Never'

Comment 6

[Sheela Ravindran]

verified as worksforme

Comment 7

[Dwayne]

But if it's truly the case that only setting SSL to 'Never' solves the problem,
then this bug is not solved.  Setting to 'If Available' should not cause this
problem.  And setting it to 'Always' should generate an error.

I will live with the WORKSFORME for now as I can't reproduce again, but be
wary... :)