638024 - Undeleting a mail soon after deleting it (ctrl-z) results in brief re-appearance and immediate deletion without the option to subsequently undeletees in unavailable to then be undeleted

Status: RESOLVED WORKSFORME

(Thunderbird :: Folder and Message Lists, defect)

Description

[andrew.boulle]

User-Agent:       Opera/9.80 (Windows NT 6.1; U; en) Presto/2.7.62 Version/11.01
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.14) Gecko/20110221 Thunderbird/3.1.8

Undeleting a mail soon after deleting it (ctrl-z) results in brief re-appearance and immediate deletion without the option to subsequently undelete. Noticed in IMAP inbox on multiple difference installation. Seems to happen consistently if more than one email is deleted in succession prior to undeleting more than one in succession.

Reproducible: Always

Steps to Reproduce:
1.delete three email in the imap inbox in quick succession
2.immediately undelete all three with ctrl-z
3.
Actual Results:  
undeleted emails were again moved to trash and could not be undeleted again

Expected Results:  
undeleted emails remain in the inbox

Comment 1

[Ludovic Hirlimann [:Usul]]

What is your imap delete model ?

Comment 2

[Wayne Mery (:wsmwk)]

and, when did this start happening?  (for example did you use version 3.0?)

Comment 3

[andrew.boulle]

Where do I check the imap delete model?
It has been happening since switching to version 3 from version 2.

Comment 4

[Wayne Mery (:wsmwk)]

If you see deleted messages in your inbox then you are using imap delete model. If they show up in your trash, then you are not - which is the default

Comment 5

[andrew.boulle]

In that case am not using the IMAP delete model as messages go to trash when deleting.

Comment 6

[Wayne Mery (:wsmwk)]

(In reply to andrew.boulle from comment #5)
> In that case am not using the IMAP delete model as messages go to trash when
> deleting.

Andrew, do you still see this problem when using version 17 or newer?

Comment 7

[andrew.boulle]

Not currently able to reproduce, on new imap server now so setup is not identical to before. I think fine to close since others have not reported it.