Closed
Bug 104557
Opened 24 years ago
Closed 24 years ago
Copy/Move of a message to another folder problem
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
People
(Reporter: boro, Assigned: mscott)
Details
I've been using Mozilla mail-client for some time now, and after around 0.9.4
there has been this small problem which I didn't found by quick look in
bugzilla, problem when moving mail from folder to another via right-click on
message(s).
This doesn't happen every time, usually after starting the mail-client...
Normally I would do&see:
1. select message(s) from imap folder to be moved to another imap-folder
2. right-click on them
3. Move mouse pointer on "Copy To" or "Move To"
4. Choose any of accounts in the list (I have 3)
5. try taking mouse pointer over subfolder of account (subfolder should be listed)
---
6. folder-icon changes to "open folder", but subfolder doesn't open or list
folders under it even trying again.
What SHOULD: list subfolder's folders.
Work-around is to to do this before trying move/copy messages: open the wanted
subfolder in left-panel where's the accounts and folders listed and then try to
move/copy the message(s). This has usually helped.
| Reporter | ||
Comment 1•24 years ago
|
||
Okay, updated to 0.9.5 (didn't see it came today) and could reproduce this with
it. Earliar browser was nightly build just before final 0.9.5 (200110115 if I
recall correctly).
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 2•24 years ago
|
||
I mean, COULDN'T reproduce. Sorry for mistake.
0.9.5 doesn't have it, but trunk builds do - so you saw right, and this is a
duplicate of reopened bug 67736 by way of bug 104419.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
*** This bug has been marked as a duplicate of 67736 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•