Closed Bug 60344 Opened 24 years ago Closed 23 years ago

Mozilla calls my Inbox `INBOX'

Categories

(MailNews Core :: Backend, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED
mozilla1.2alpha

People

(Reporter: mpt, Assigned: naving)

References

Details

Attachments

(2 files)

Build: 2000111520, Mac OS 9.0 My IMAP Inbox appears to be called `INBOX' on the IMAP server. As a result, it is displayed not as `Inbox' but as `INBOX', and this looks corny. Assuming that IMAP folder names are case-insensitive, I suggest that any folder name which is all capitals on the server should be treated by Mozilla (and recorded in Mozilla's mail database) as if it had only an initial capital.
Keywords: 4xp
If I remember right, only INBOX is case-insensitive.
yes, only INBOX is case-insensitive - your suggestion is not viable for all folders in general. You, as a user, have control over the case of your other folder names. We present the INBOX name as the IMAP server presents it to us.
QA Contact: esther → huang
this should be fairly trivial to fix.
Status: NEW → ASSIGNED
Keywords: mail6
OS: Mac System 8.5 → All
Priority: P3 → P2
marking nsbeta1-
Keywords: nsbeta1-
It might be mozilla calling your Inbox INBOX and your server might be calling it Inbox - Navin has a fix if that's the problem
Assignee: bienvenu → naving
Status: ASSIGNED → NEW
Attached patch proposed fix.Splinter Review
Use the boxname as sent by the server instead of "INBOX". Need review, david
r=bienvenu, though judging by that fix, 4.x would have had the same problem, wouldn't it?
mpt, could you verify this patch or tell us the server where we can verify it ? I don't know what 4x does ? I think it would always create "Inbox", no matter what.
Sorry, I don't currently have the setup to apply patches. Mozilla has this problem (and 4.x does not) with all IMAP accounts I have had; one of these is mailandnews.com, which offers free IMAP accounts so you can get one there and try it out. If the server itself refers to the inbox as INBOX, I still think it would be preferable from an aesthetic point of view to display it as `Inbox' -- provided that it is not possible for an IMAP server to have two folders named `Inbox' and `INBOX' at the same time.
mpt, the mailandnews server sends INBOX. From the log ask for all mailboxes 268[396b340]: mailandnews.com:A:SendData: 3 lsub "" "*"^M The server replies 268[396b340]: mailandnews.com:A:CreateNewLineFromSocket: * LSUB () "." Deleted^M 268[396b340]: mailandnews.com:A:CreateNewLineFromSocket: * LSUB () "." INBOX^M 268[396b340]: mailandnews.com:A:CreateNewLineFromSocket: * LSUB () "." Outbox^M 268[396b340]: mailandnews.com:A:CreateNewLineFromSocket: * LSUB () "." Trash^M 268[396b340]: mailandnews.com:A:CreateNewLineFromSocket: 3 OK Completed^M
I think what mpt is suggesting here is to change INBOX to Inbox, just like in 4x. right ?
Right.
So the patch we want is one which uses the string "Inbox" whether the server sends "inbox", "INBOX" or "Inbox", right? If this is the case, it's a tiny mod to the attached patch. Gerv
Attached patch Patch v.1Splinter Review
Looking for some rubberstamps here, please... This is a one-liner. blake? bienvenu? naving? Gerv
Assignee: naving → gervase.markham
Hardware: Macintosh → All
Target Milestone: --- → mozilla0.9.3
We cannot take this patch because there are several other places where we call Inbox "INBOX". This will need some more work.
I've done an LXR search for all occurrences of the string "INBOX" and have only found the following ones which seemed possibly relevant: mailnews/imap/src/nsImapServerResponseParser.cpp, line 840 -- boxname = PL_strdup("INBOX"); mailnews/imap/src/nsIMAPHostSessionList.cpp, line 704 -- result.AppendWithConversion("INBOX"); mailnews/imap/src/nsImapIncomingServer.cpp, line 1088 -- PRInt32 offset = parentName.Find("INBOX",PR_TRUE,0,1); mailnews/imap/src/nsImapProtocol.cpp, line 5821 -- List("INBOX", PR_TRUE); The first one is the one changed in the current patch. I've checked the others out and, as far as I can see, none of them seem relevant. Note that this change is only meant to affect the displayed string; all internal handling should continue as before. Also, please note that the original fix which you attached to this bug, which uses what the server sends instead of INBOX (whereas my fix uses "Inbox" instead of "INBOX") only changes this file. If you think there are other files that need changing, you are going to have to give me a clue as to what they are ;-) Gerv
Didn't make the 0.9.3 train.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
I think Gerv's patch look reasonable, to separate backend and frontend usage of this constant. I asked him to test it on IRC, and he said it works too. If you get bienvenu's sr, here's r=hwaara.
I thought we already checked in a fix for this, and we had some problem with Cyrus servers because we changed the case of INBOX which messed up sub-folders. Navin, do you have the bug I'm talking about?
Component: Mail Database → Mail Back End
Gervase, I remember telling you that this bug is trivial and may cause more problems than good. Please do not checkin this fix. Inbox is a very sensitive folder and we need to be sure that it works in all cases with different servers. I cannot test it right now but I will get to it in mach V. bienvenu, that is a different bug, I have that bug.
mach V?
Navin: I am happy to hold off if you are going to get to this eventually. Otherwise, I'd like to keep investigating and testing. It either causes problems or it doesn't - if all we change is the displayed string, it can't cause problems. If that string is used for other things internally, it may cause problems and we should find a fix that only changes the displayed string. Gerv
I may try and move the string change closer to the actual point of display, to avoid any suggestion that it will mess with other internal stuff. Gerv
Target Milestone: mozilla0.9.4 → mozilla0.9.5
*** Bug 90683 has been marked as a duplicate of this bug. ***
Ccing Cavin
Cavin, do you think this bug is related to bug 98433 that I logged? Looks like we are still having problem for Inbox & INBOX for interoperability......
Karen, this bug is different from bug 98433
Please note that bug 90683 marked as a duplicate is about cyrus imap server being case _sensitive_ to the name of Inbox when there are subfolders of Inbox. Where as the original report is about Inbox being case insensitive. I'm not sure but it looks like the proposed fix should solve this?
A suggestion would be to have a hardcoded #define somewhere for the case of inbox (that would be "Inbox") and then use it everywhere. That would solve naving's concerns of inconsistency, right?
Target Milestone: mozilla0.9.5 → mozilla0.9.6
I don't have the energy for this any more. It's a trivial cosmetic fix, and I can't be bothered to fight past all the obstacles. Gerv
Assignee: gerv → mscott
QA Contact: huang → esther
QA Contact: esther → huang
moving to 0.9.9
Target Milestone: mozilla0.9.6 → mozilla0.9.9
Keywords: mail6nsbeta1+
Blocks: 122274
Status: NEW → ASSIGNED
Keywords: nsbeta1+nsbeta1-
Target Milestone: mozilla0.9.9 → mozilla1.2
No longer blocks: 122274
this was fixed when I fixed bug 57440
Assignee: mscott → naving
Status: ASSIGNED → NEW
marking fixed
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Matthew, can you confirm this bug's fix? Please mark as verified if the problem is not occurring for your IMAP Server. Thanks.
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: