Closed Bug 26735 Opened 25 years ago Closed 23 years ago

IMAP mailbox state ignored

Categories

(MailNews Core :: Backend, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED
Future

People

(Reporter: rzach, Assigned: Bienvenu)

Details

(Whiteboard: [nsbeta1+ 1/25] need help for verify)

Attachments

(2 files)

Trying to compact an IMAP folder, I got an alert saying:

Read-only Mailbox! Your browser is not RFC compliant since it ignores the
mailbox state

The weird thing is that I can move messages in and out of folders, and can mark
them deleted, so it's not really read-only.  So this may well be a server
problem.  I'm attaching the IMAP log just in case there is something here.

Linux build 2000.02.05.08
Attached file IMAP log
Status: NEW → ASSIGNED
Target Milestone: M15
QA Contact: lchiang → huang
Summary: IMAP mailbiox state ignored → IMAP mailbox state ignored
Yup, it's a read only mailbox shouldn't allow compact to that folder.
Mass moving to M16 to get these off the M15 radar.  Please let me know if this
is really an M15 stopper.
Target Milestone: M15 → M16
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17
Moving to M18 and nominating for beta3.
Keywords: nsbeta3
Target Milestone: M17 → M18
- per mail triage
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future
Attached patch a fixSplinter Review
Can I get a r= & sr=?
OK, sr=bienvenu, but we shouldn't close the bug, just reassign it to me - there
are many other operations that we should pay attention to the read only state
for besides expunge.
Assignee: jefft → bienvenu
Status: ASSIGNED → NEW
As you wish. I'll let you check in the fix too. Thanks,
adding mail3 keyword
Keywords: mail3
changing priorities
Priority: P3 → P2
any ideas on which operations or are there so many of them it's not worth listing?
this just needs to be done in a centralized place, probably
ProcessSelectedStateUrl, before getting to the individualized handlers for imap
commands. I believe 4.x handled this correctly. It's not hard.
Status: NEW → ASSIGNED
I know it's probably easy, but what are some of the more important operations
that are affected if we don't fix this?
deleting messages, marking messages read, compacting the folder, copying
messages into the folder - all of these will cause an alert
marking nsbeta1+ and moving to mozilla0.8
Keywords: nsbeta1
Priority: P2 → P3
Whiteboard: [nsbeta3-] → [nsbeta3-][nsbeta1+]
Target Milestone: Future → mozilla0.8
moving to mozilla0.9
Target Milestone: mozilla0.8 → mozilla0.9
marking nsbeta1-
Keywords: nsbeta1, nsbeta3nsbeta1-
Whiteboard: [nsbeta3-][nsbeta1+] → [nsbeta1+ 1/25]
Target Milestone: mozilla0.9 → Future
fix checked in - we pay attention to the read-only state now and don't issue the
protocol that causes the alert. Richard, if you're still around, it would be
great if you could verify this since I doubt our QA has access to any read-only
mailboxes. Thanks!
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Richard, can you help for verifying this bug since we don't have access to any
read-only mailboxes. Please mark as verified if problem has be fixed.
Reopen if problem still exists. Thanks!
Adding "need help for verify" on the status whiteboard.
Whiteboard: [nsbeta1+ 1/25] → [nsbeta1+ 1/25] need help for verify
Again....
Richard, can you help for verifying this bug ? Please mark as verified if
problem has be fixed. Thanks!
As far as I can tell, this is 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.

Attachment

General

Creator:
Created:
Updated:
Size: