Closed Bug 27396 Opened 25 years ago Closed 25 years ago

Shouldn't display error when selecting UW IMAP "folder-only" folders

Categories

(MailNews Core :: Backend, defect, P2)

Product:
MailNews Core
Component:
Backend
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: huang, Assigned: jefft)

References

Details

(Whiteboard: w/b minus on 03/07)

Attachments

(1 file)

A fix - reviewed by bienvenu
43.63 KB, patch
Details | Diff | Splinter Review
Used WinNT 2000-02-09-09-M14 commercial build: Shouldn't display error when selecting UW IMAP "folder-only" folders. This bug is related to bug#20879 Setup Info: 1)Used 4.7 profile with the following Server's Preference setup: - Leave blank for IMAP server directory - Uncheck dual-use-folder 2) Created "folder only" & "message only" folders from this profile 3) Migrated this 4.7 profile to 5.0 Steps: 1) Login to 5.0 for this UW IMAP account. 2) Select all the "folder only" & "message only" folders. 3) Actual Results: - If select "folder only" folder displayed an error as following: "The current command did not succeed. The mail server responded: SELECT failed: Can't open "foldername": not a selectable mailbox" - If select the "message only" folder without an error and the message within that folder displayed successfully. Expected Results: Should allow to select that "folder only" folder without any error. P.S. Jeff, I just assign to you directly, you can assign to other developer if you want to....
Change QA Contact to me.
QA Contact: lchiang → huang
Summary: Shouldn't display error when selecting UW IMAP folders → Shouldn't display error when selecting UW IMAP "folder-only" folders
Problem occurred on Linux & Mac, too. Change platform/OS to All.
OS: Windows NT → All
Hardware: PC → All
What we need to do is to check with the no select flag. When displaying we might want to simply gray out the folder name just like 4.7 does. When user select to it we don't send select command to the server but highlight the selection.
Status: NEW → ASSIGNED
Target Milestone: M15
Adding beta1 on the keyword. Raising Priority to P2, this is not really a blocker--but it's not good for the users keep seeing the errors display all the time for just selecting folders....
Keywords: beta1
Priority: P3 → P2
I have fix for this. It's part of fixing bug 28301.
Depends on: 28301
Putting on PDT+ radar for beta1. Will move to minux tomorrow not if not fixed soon however!
Whiteboard: [PDT+] w/b minus on 03/07
Moving to PDT- because (1) this problem just is not that severe and (2) the fixes are non-trivial and I'd like them to have more bake time.
Whiteboard: [PDT+] w/b minus on 03/07 → [PDT-] w/b minus on 03/07
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fix checked in.
So, fix will be in the branch build (beta1)? or in the trank build?
Since the bug is listed as PDT- I think it's safe to assume it's in the trunk and not in the beta1 branch.
Yes, trunk (tip) only not branch.
OK. Thanks. Then I will verify on the trank build after completing verification for beta build.
Yes, there're no errors displayed anymore after a click an a folder-only folder, *if it is not listed in the .mailboxlist file of the server*. Thanks! However, if the folder is listed in the file (with or without ending slash), the folder is still displayed as a normal folder and gives an error after clicking on it. REOPENing. IIRC, 4.x for Windows creates such entries (with ending slash), when a new folder-only folder is created (the unix version doesn't support creating them at all :-( ). Note, that 4.x shows the same bug. Maybe this is a server restriction and there's no way for us to find out, but I don't know.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Keywords: relnote
Target Milestone: M15 → M16
Mass moving to M16 to get these off the M15 radar. Please let me know if this is really an M15 stopper.
Updating the keywords -- remove beta1 PDT- and add beta2 on the keywords.
Keywords: beta1, relnote → beta2
Whiteboard: [PDT-] w/b minus on 03/07 → w/b minus on 03/07
Not beta2 stopper, marking M18. Please add beta2 keyword if you disagree.
Target Milestone: M16 → M18
By using 04-16-10-M16 commercial build: Jeff, I did check on this bug....the error is not displaying anymore.....but why when I create the "jeff/david" folder, it should grey out right away, but it didn't -- it will display as normal at first until I select & expand the "jeff" folder in order to see "david"...then it will turn to grey....so does this bug fix completely or will be another bug?
Since this bug logged for "error display" initially. I think that I will log another bug for above described problem.... Jeff, you may mark resolved for this bug now....then I can verify this bug.
If select "jefft" folder doesn't cause error message then that's the rdf updating problem not part of this bug.
Please see my comment above. Should we log a new bug for this as well?
Marking it as fixed again. There already is a generic rdf upating bug assigned to putterman. I believe.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
ScottP, would you please find the bug#? so we can track that problem as well? Thanks.
I don't know of any bug for this.
bug#36248 logged for the problem I described from my above comments. Mark this bug as verified....please still put the rdf bug here if anybody knows. Thanks.
Status: RESOLVED → VERIFIED
I think the rdf bug is the one about the folder/thread pane not refreshing? Is that it? If so, I can try to find it.
Yes, that sounds like it.
I can't find it. I think we should open a new bug for this display/update problem. Will leave up to Karen to do so.
I will try on today's M16 build, if problem is still occurring, then I will log a bug then.
bug#36397 logged for the first launch for new profile's folders refresh problem.
Keywords: nsbeta2
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: