Open Bug 452394 Opened 16 years ago Updated 2 years ago

imap mark-as-deleted model: should close msg and advance after deleting (in standalone msg window) (like pop)

Categories

(Thunderbird :: Mail Window Front End, defect)

defect

Tracking

(Not tracked)

People

(Reporter: checco, Unassigned)

References

(Depends on 1 open bug)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.1) Gecko/2008070208 Firefox/3.0.1
Build Identifier: version 2.0.0.16 (20080708)

When deleting a message in an IMAP folder, it is marked as deleted.  If the message was open, there is no indication that it was deleted.

When deleting a message in a POP3 account, the mail is closed (if open), moved to trash and the next message is loaded.  

I would like IMAP accounts to act consistently in this was as well

Reproducible: Always

Steps to Reproduce:
1. open email from imap account
2. select delete

Actual Results:  
1. nothing visible happens if message is open
2. message on imap folder is marked as deleted

Expected Results:  
1. message should be closed (if open)
2. folder should mark mail as deleted, move it to trash (perhaps an option?)
3. next message should be opened (if original message was open)
What's your IMAP delete model:

Account settings -> [ IMAP server -> Server Settings:
"When I delete a message"

Mine is set to "Move it to the trash folder," and everything WFM.
Thanks for the suggestion, but I like the "mark as deleted" option for my IMAP servers... 
a) if a message window is open and the "delete" button is pressed, the message window should be closed
a) the auto message advancement should work even if I do not move it to Trash. 
Confirming.
Status: UNCONFIRMED → NEW
Component: General → Mail Window Front End
Ever confirmed: true
OS: Windows XP → All
QA Contact: general → front-end
Hardware: PC → All
Summary: imap folder processing should be similar to pop3 → imap mark-as-deleted model: should close msg and advance after deleting (in standalone msg window) (like pop)
Depends on: 65823
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.