IMAP: delete message, moves to next message and stalls

RESOLVED EXPIRED

Status

Thunderbird
Mail Window Front End
RESOLVED EXPIRED
14 years ago
13 years ago

People

(Reporter: Ian Lipsky, Assigned: Scott MacGregor)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 0.8 (20041020)

When i click a message in thunderbird, and hit the delete it, it marks the 
message as deleted, and then instantly jumps to the next available message and 
stalls. It just sits there trying to display the message. If i hit stop and 
click another message it displays fine. Only stalls when i hit delete and it 
jumps to the next message (i'd be happy if i could just stop it from jumping 
to the next message on its own).

Reproducible: Always
Steps to Reproduce:
1. click a message
2. press the delete key
3. sit back and watch the busy icon in the upper right corner as it animates 
endlessly 

Actual Results:  
A few brain cells commited suicide from waiting endlessly for thunderbird to 
display the next message.

Expected Results:  
Displayed the next message (or optionally NOT jumped to the next message after 
hitting delete ... thats what i would prefer)

This is using an IMAP server, MEpro 1.5e from mailenable.com

I tried setting the option for cached connections to 1 in thunderbird just in 
case it was trying to open too many connections but it had no effect.

Comment 1

13 years ago
I think the behaivor of Thunderbird not normally work.
1. After click on the message and the hit delete. Thunderbird is stalling.
2. Don't hit the delete key if you click the message body. You will need to
select another message then select back to the message which you want to delete.
Press the delete key. Untouch message body Thunderbird still fine work.
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.