Closed Bug 2730 Opened 26 years ago Closed 23 years ago

Can't expunge folder with open connection: old UW servers

Categories

(MailNews Core :: Backend, defect, P2)

Product:
MailNews Core
Component:
Backend
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME
Milestone:
Future

People

(Reporter: lchiang, Assigned: naving)

Details

<content transferred from bugsplat bug 332020. I edited the description from that bug to delete the test account username and pw info. If you need it, check the bugsplat bug for the info.> Can't expunge folder with open connection: old UW servers Oct 13, 1998 Linux 4.5. I have 2 test messages sitting in the test account at demo.cac.washington.edu that I can't expunge. I just get mozilla IMAP stdout: URL: Loading IMAP://demo.cac.washington.edu?expunge>|INBOX [mkimap4.cpp:10666] imapIOthread IMAP stdout: demo.cac.washington.edu:S-INBOX:NET:WR: 12 expunge [mkimap4.cpp:9975] imapIOthread IMAP stdout: demo.cac.washington.edu:S-INBOX:NET:RD: 12 NO EXPUNGE failed: Can't expunge because mailbox is in use by another process Granted, this is a really old server, but other than connecting with a different client, I can't think of a way to expunge them. I don't have this problem with newer UW servers.
Setting all current Open/Normal to M4.
QA Contact: 4098
qa contact to scurtis
This has a current target milestone of M4. Would you consider this an M4 stopper? If not, please change the milestone accordingly.
Target Milestone: M4 → M7
We don't have IMAP in 5.0 yet so we can't fix any bugs for it...Pushing to M7.
Summary: Can't expunge folder with open connection: old UW servers → [PP]Can't expunge folder with open connection: old UW servers
Hardware: Other → All
Summary: [PP]Can't expunge folder with open connection: old UW servers → Can't expunge folder with open connection: old UW servers
Removing [PP] from summary. This was never a platform parity bug. I suggest we make this a really late milestone, anyway, since a) They've upgraded the server at demo.cac.washington.edu ...I'm not sure we'll even be able to find an older UW server at this point, and b) older UW servers aren't on the supported server list anyway. Will update when/if I'm able to reproduce.
Status: NEW → ASSIGNED
Target Milestone: M7 → M10
I'm not at the stage where I'm fixing bugs that were in 4.5x yet. triaging to m10.
OS: Linux → All
Correcting OS to ALL.
I don't think this bug needs to be fixed for PR1
Target Milestone: M10 → M14
post beta 1.
QA Contact: scurtis → huang
change QA Contact to me since it's my feature now
Target Milestone: M14 → M15
load balancing to jefft. Looks like this is an old 4.x bug so maybe we don't need to fix it in the 5.0 timeframe....
Assignee: mscott → jefft
Status: ASSIGNED → NEW
Target Milestone: M15 → M16
Status: NEW → ASSIGNED
Not M16 stopper, marking M17. Please add beta2 keyword if you think this is a beta2 stopper.
Target Milestone: M16 → M17
moving to future milestone.
Target Milestone: M17 → Future
reassigning jefft's bugs to naving
Assignee: jefft → naving
Status: ASSIGNED → NEW
The bug was entered in 1999 about old IMAP servers, I think the issue should be closed now two years later as even the reporter has no access to such an old server anymore and IMAP code changed a lot during that time. I propose to close this oldie bug ASAP.
I tried this sometime back and it worksforme.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Based on above comments, marking as verified since we don't have such old server anymore. Please log new bug for current UW Server if you see this problem again.
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.