217840 - Mail delivey aborts with a failed assertion

Status: RESOLVED EXPIRED

(MailNews Core :: Networking, defect)

Description

[Stas Sergeev]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030712
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b) Gecko/20030712

When I press a "Get Msgs" button, I see the following in the status bar:
Resolving host xxx (where xxx is the host name, that's OK)
Connecting to xxx (that's OK either)
But then I hear a beep and delivery aborts.
The message "Connecting to xxx" stays on the status bar.
On the console I see this message:
---
###!!! ASSERTION: unknown error, but don't alert user.: 'errorID !=
UNKNOWN_ERROR', file nsMsgProtocol.cpp, line 399
Break: at file nsMsgProtocol.cpp, line 399
Abort mail message delivery.
---

It used to work perfectly for years, but since the last "cvs update" this
week the mail delivery works not any more. So this bug is very recent
(I think, unless it was caused by something else I did, but I don't think
I've done some changes that could affect mozilla when this started to happen).

Reproducible: Always

Steps to Reproduce:
1.do "cvs update" and build the newest mozilla
2.press "get msgs" button


Actual Results:  
Beep and the error message mentioned above.

Expected Results:  
Receive the e-mail, as it used to do for years.

What additional information can I provide?
I can do some gdb debugging if you like, just give me a hints what is to debug
out.

Comment 1

[Stas Sergeev]

I've figured out what causes this.
This happens only if the socks proxy is
defined in the Preferences but is not
accepting connections.
Now the bug may be closed as invalid, but
I think there can be some better notification
about a nonfunctional socks proxy than the
assertion failure.
Also it doesn't seem to be affected by any
settings in a "Mail & News account settings"
including the "Use secure connection", "Use
secure authentification" etc. Does it really
use the socks proxy for pop3 in all that cases?
Anyway I think a better user notification is
necessary, so I am leaving this opened.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.