Closed Bug 10834 Opened 26 years ago Closed 25 years ago

[FEATURE] Delete Folder/Move Folder to Trash - POP

Categories

(MailNews Core :: Backend, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: scottputterman, Assigned: jefft)

References

Details

(Whiteboard: [PDT-] ETA 03/24/00)

bug tracking feature in Summary.
Blocks: 10791
Target Milestone: M11
bug tracking feature in Summary.
Status: NEW → ASSIGNED
Whiteboard: [PR1]
This needs to be fixed for PR1, so I added a note to the Status Whiteboard.
Target Milestone: M11 → M15
Triage to M15
Blocks: 27731
*** Bug 16751 has been marked as a duplicate of this bug. ***
changing [PR1] into beta1
Keywords: beta1
Whiteboard: [PR1]
reassigning to jefft. I'm pretty sure this got fixed already.
Assignee: putterman → jefft
Status: ASSIGNED → NEW
Putting on PDT- for beta. But moving to Fixed. lchiang, can you verify?
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Whiteboard: [PDT-]
fenella - pls verify - thanks!
QA Contact: lchiang → fenella
How do you test this if the UI isn't set up for deleting folders? See bug 27731.
Perhaps we can't verify yet - the backend is there, but no UI. I wonder if there is a backend way we can verify this - if yes, I can ask ppandit to do so.
Sorry to comment on this so late... I don't think that I have done anything for POP3 delete folder/move folder to trash. For Imap, I did implement the feature but there is no UI to test it at the moment.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I am pretty close to have a fix for this.
Status: REOPENED → ASSIGNED
Priority: P3 → P1
Whiteboard: [PDT-] → [PDT-] ETA 03/24/00
Fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Keywords: beta1
Resolution: --- → FIXED
I cannot verify this until Bug 27731 is fixed
Linux, Mac (2000-05-19-08 M16) Win32 (2000-05-19-09 M16) Bug 27731 is fixed and verified. And verified that this bug is also fixed.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.