IMAP mailbox state ignored

VERIFIED FIXED in Future

Status

P3
normal
VERIFIED FIXED
19 years ago
11 years ago

People

(Reporter: rzach, Assigned: Bienvenu)

Tracking

Trunk
Future
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

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

Attachments

(2 attachments)

(Reporter)

Description

19 years ago
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
(Reporter)

Comment 1

19 years ago
Created attachment 5001 [details]
IMAP log

Updated

19 years ago
Status: NEW → ASSIGNED
Target Milestone: M15

Updated

19 years ago
QA Contact: lchiang → huang
Summary: IMAP mailbiox state ignored → IMAP mailbox state ignored

Comment 2

19 years ago
Yup, it's a read only mailbox shouldn't allow compact to that folder.

Comment 3

19 years ago
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

Comment 4

19 years ago
Mass moving M16 to M17 - look for nsbeta2 before anything else.
Target Milestone: M16 → M17

Comment 5

19 years ago
Moving to M18 and nominating for beta3.
Keywords: nsbeta3
Target Milestone: M17 → M18

Comment 6

19 years ago
- per mail triage
Whiteboard: [nsbeta3-]
Target Milestone: M18 → Future

Comment 7

18 years ago
Created attachment 19278 [details] [diff] [review]
a fix

Comment 8

18 years ago
Can I get a r= & sr=?
(Assignee)

Comment 9

18 years ago
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.

Updated

18 years ago
Assignee: jefft → bienvenu
Status: ASSIGNED → NEW

Comment 10

18 years ago
As you wish. I'll let you check in the fix too. Thanks,
(Assignee)

Comment 11

18 years ago
adding mail3 keyword
Keywords: mail3
(Assignee)

Comment 12

18 years ago
changing priorities
Priority: P3 → P2

Comment 13

18 years ago
any ideas on which operations or are there so many of them it's not worth listing?
(Assignee)

Comment 14

18 years ago
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

Comment 15

18 years ago
I know it's probably easy, but what are some of the more important operations
that are affected if we don't fix this?
(Assignee)

Comment 16

18 years ago
deleting messages, marking messages read, compacting the folder, copying
messages into the folder - all of these will cause an alert

Comment 17

18 years ago
marking nsbeta1+ and moving to mozilla0.8
Keywords: nsbeta1
Priority: P2 → P3
Whiteboard: [nsbeta3-] → [nsbeta3-][nsbeta1+]
Target Milestone: Future → mozilla0.8

Comment 18

18 years ago
moving to mozilla0.9
Target Milestone: mozilla0.8 → mozilla0.9

Comment 19

18 years ago
marking nsbeta1-
Keywords: nsbeta1, nsbeta3 → nsbeta1-
Whiteboard: [nsbeta3-][nsbeta1+] → [nsbeta1+ 1/25]
Target Milestone: mozilla0.9 → Future
(Assignee)

Comment 20

18 years ago
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
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 21

18 years ago
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!

Comment 22

18 years ago
Adding "need help for verify" on the status whiteboard.
Whiteboard: [nsbeta1+ 1/25] → [nsbeta1+ 1/25] need help for verify

Comment 23

18 years ago
Again....
Richard, can you help for verifying this bug ? Please mark as verified if
problem has be fixed. Thanks!
(Reporter)

Comment 24

18 years ago
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.