1813367 - `Move to <folder> again` doesn't work

Status: VERIFIED FIXED

(Thunderbird :: Folder and Message Lists, defect)

Description

[raal]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/109.0

Steps to reproduce:

TB 111.0a1 (2023-01-28) (64-bit), Linux
Gmail account
This works: select message, right click a message, select Move to>gmail account>Inbox

Bug steps:
go to spam folder
right click a message
select "Move to Inbox again"

Actual results:

Actual result: nothing happens

Expected results:

move message to Inbox

Comment 1

[Thomas D. (:thomas8)]

Thanks raal. Confirming for TB 111.0a1 (2023-01-31) (64-bit), Win10. Please note that filing bugs against TB 111 is discouraged before 14-Feb as we're still working on it.

Comment 2

[Geoff Lankow (:darktrojan)]

Attachment: Bug 1813367 - Fix "Move to <folder> again" context menu item. r=#thunderbird-reviewers

Comment 3

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/a0df2fc649a0
Fix "Move to <folder> again" context menu item. r=mkmelin

Comment 4

[Wayne Mery (:wsmwk)]

Comment on attachment 9318658 [details]
Bug 1813367 - Fix "Move to <folder> again" context menu item. r=#thunderbird-reviewers

[Triage Comment]
Approved for beta

Comment 6

[Daniel Darnell [:dandarnell]]

Thunderbird 111.0b1:
https://hg.mozilla.org/releases/comm-beta/rev/84787dee37c7

Comment 7

[Wayne Mery (:wsmwk)]

Confirm this works on daily.

Comment 8

[raal]

happened yesterday with TB 112.0a1 (2023-03-04) (64-bit)
E-mail is in the Spam folder
TB re-downloading all message in Inbox
In the spam folder click Move to inbox again
Message is lost - it's not in spam folder or inbox folder

It's IMAP account. Please can you check it?

Comment 9

[raal]

Attachment: Snímek obrazovky z 2023-03-06 18-22-52.png

Please reopen the bug - you're moving an e-mail to inbox of different account!

Comment 10

[Geoff Lankow (:darktrojan)]

The option moves mail to the most recently moved-to folder. If that's not what you thought it was, that's not our fault.

This bug is closed. If you think there is a further problem here, open another bug.