Open
Bug 160643
Opened 21 years ago
Updated 8 months ago
case sensitive issue of the special 'IMAP Server Directory' setting - 'INBOX'
Categories
(MailNews Core :: Networking: IMAP, defect)
MailNews Core
Networking: IMAP
Tracking
(Not tracked)
NEW
People
(Reporter: Henry.Jia, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(3 files, 1 obsolete file)
14.80 KB,
image/jpeg
|
Details | |
8.22 KB,
image/jpeg
|
Details | |
2.17 KB,
patch
|
Details | Diff | Splinter Review |
When you set the 'IMAP Server Directory' of IMAP servers that have the 'INBOX.' namespace to case insensitive 'INBOX', such as 'inbox', 'Inbox', etc, you'll see that the folders are shown both under 'INBOX' folder and parallelly with 'INBOX' folder. See comment in bug 27002 (http://bugzilla.mozilla.org/show_bug.cgi?id=27002#c109) Steps to reproduce: 1. set an account in which the IMAP server has an 'INBOX.' namespace 2. set the 'IMAP Server Directory' advanced setting to 'inbox' 3. refresh the folders showing Expect: the folders originally under 'INBOX' should only show parallelly with 'INBOX' Result: the folders show both under 'INBOX' and parallelly with 'INBOX', so confusing. Add bienvenu & Michael Klose to CC list.
Updated•21 years ago
|
QA Contact: olgam → huang
Taking. :-) Add Seth to the CC list.
Assignee: sspitzer → Henry.Jia
Make the parser nsImapUrl::AllocateCanonicalPath case insensitive for the specific 'INBOX'.
Add cavin & navin to the CC list. Pls r=. Thx.
Status: NEW → ASSIGNED
Comment 6•21 years ago
|
||
If I understand this patch correctly, you're just trying to extend the logic of checking if the currentPath starts with the onlineDir to be case-insensitive if the onlineDir is INBOX. I don't think that should take an extra 30 lines of code. I'll try to come up with a more succinct approach.
A clearer patch for review.
Attachment #94153 -
Attachment is obsolete: true
Comment on attachment 96667 [details] [diff] [review] patch for review 1/3 lines are related to comments & ASSERTION.
Updated•21 years ago
|
QA Contact: huang → gchan
Comment 9•21 years ago
|
||
How about set server directory directly to "INBOX" by ignoring case in nsImapIncomingServer::SetServerDirectory if we really need to fix this bug ?
Updated•19 years ago
|
Product: Browser → Seamonkey
Updated•15 years ago
|
Assignee: Henry.Jia → bienvenu
Status: ASSIGNED → NEW
Component: MailNews: Main Mail Window → Networking: IMAP
Product: Mozilla Application Suite → Core
QA Contact: grylchan → networking.imap
Assignee | ||
Updated•15 years ago
|
Product: Core → MailNews Core
Updated•11 years ago
|
Assignee: dbienvenu → nobody
Comment 11•2 years ago
|
||
We have an issue where TB no longer finds the subscribed folder if capitalization of "INBOX" changes. As far as I understood RFC 3501, INBOX and iNbOx and whatever combination is completely valid since Inbox itself is case-insensitive.
Example:
TB is subscribed to INBOX/schaiss2:
# curl imap://mail01/ -u u0005@company.test: -X 'LIST "" "*"'
* LIST () "/" "INBOX"
* LIST (\Trash) "/" "Deleted Items"
* LIST (\Drafts) "/" "Drafts"
* LIST (\Sent) "/" "Sent Items"
* LIST () "/" "INBOX/schaiss2"
# curl imap://mail01/ -u u0005@company.test: -X 'LSUB "" "*"'
* LSUB () "/" "Drafts"
* LSUB () "/" "Sent Items"
* LSUB () "/" "Deleted Items"
* LSUB () "/" "INBOX"
* LSUB () "/" "INBOX/schaiss2"
Now there is a change:
# curl imap://mail01/ -u u0005@company.test: -X 'LIST "" "*"'
* LIST () "/" "INBOX"
* LIST (\Trash) "/" "Deleted Items"
* LIST (\Drafts) "/" "Drafts"
* LIST (\Sent) "/" "Sent Items"
* LIST () "/" "INBOX/schaiss2"
# curl imap://mail01/ -u u0005@company.test: -X 'LSUB "" "*"'
* LSUB () "/" "Drafts"
* LSUB () "/" "Sent Items"
* LSUB () "/" "Deleted Items"
* LSUB () "/" "INBOX"
* LSUB () "/" "Inbox/schaiss2"
TB nows greys out that folder, whereas it should not.
Comment 12•2 years ago
|
||
Hello this also causes us IMAP synchronisation issues when users rename folders. So we as helpdesk often have to step in which is annoying, just because the RFC is not followed by Thunderbird as it is by mailserver software. Please fix this
Updated•8 months ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•