Closed Bug 16366 Opened 25 years ago Closed 25 years ago

Move/copy menus not updated after creating a new folder

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: huang, Assigned: scottputterman)

References

Details

WinNT / 10-13-09-M11 commercial build / IMAP account:

1) Create folders from the local mail of one IMAP account
2) Selected any msg from Inbox and tried to copy one msg to that specific local
mail folder....
3) But when go to menu bar: "Message" menu -> "Copy Message" menu item -> "Local
Mail" and wanted to find that specific new folders.
4) Actual Results: The new folders not display there, need to exit application
in order to copy msg to local folders.

All other platforms and POP account are working fine
 except specific WinNT / IMAP account.
All platforms
Assignee: phil → putterman
Summary: Shouldn't need to exit application to create IMAP account's local mail folders from the Message ->Copy message menu → Move/copy menus not updated after creating a new folder
Reassign to putterman, cc alecf.
QA Contact: lchiang → huang
Changed QA Contact to me
*** Bug 17424 has been marked as a duplicate of this bug. ***
Target Milestone: M13
M13. This seems to work ok using bookmark folders.
Status: NEW → ASSIGNED
Target Milestone: M13 → M14
I'm sure this is similar to new accounts not showing up (at least it will be
when we start listening to server notifications).
Depends on: 17713
yup... I'll add a dependancy for you, because this isn't even worth looking into
until I add that.
This seems to be working for me.  Karen can you try this again before I mark it
WORKSFORME?
Sure.
Used 03-07-09-M15 WinNT:
It works for me too, you can go ahead to mark as worksforme.
marking WORKSFORME
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Marking as verified.
Oops! Marking as verified.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.