Closed
Bug 577506
Opened 15 years ago
Closed 13 years ago
listing content of sub folder named "Inbox xxxx@xxxx.xx " dos not work
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: voggur, Unassigned)
Details
(Whiteboard: [closeme 2012-03-25])
Attachments
(1 file)
25.72 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.99 Safari/533.4
Build Identifier: 3.0.x
normal thunderbird sends "select "INBOX/junk mail""
if the folder name is "Inbox xxx@xxx.xx" it sends
"select "Inbox xxx@xxx.xx/Inbox xxx@xxx.xx"" to the server
Reproducible: Always
Steps to Reproduce:
1.make sub folder in your inbox namd "Inbox xxx@xxxx.xxx"
2.send some content to the folder
3.try to list content of folder
probably bug in version 3.0.x at lest in 3.0.4 and 3.0.5 only trade Linux builds
Comment 1•15 years ago
|
||
Is the bug still present in 3.1.1 ?
Component: Folder and Message Lists → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: folders-message-lists → networking.imap
Yes
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9pre) Gecko/20100805 Lanikai/3.1.3pre
OS: Linux → All
Comment 3•15 years ago
|
||
Is this over imap ?
Comment 5•15 years ago
|
||
Can you get a imap log https://wiki.mozilla.org/MailNews:Logging ?
from the log you can see the folder list correctly and how it sends the wrong select command "Inbox xxx@xxxxx.xx/Inbox xxx@xxxxx.xx"
Updated•15 years ago
|
Attachment #467171 -
Attachment mime type: text/x-log → text/plain
Comment 7•15 years ago
|
||
> 3 select "Inbox hus@hydra.is/Inbox hus@hydra.is"
> 3 NO SELECT Mailbox does not exist
"Inbox hus@hydra.is" is a namespace.
> 3 namespace
> * NAMESPACE (("" "/")) NIL (("Inbox Spjall@hydra.is/" "/")
> ("Inbox thor@catholic.org/" "/") ("Inbox WebMaster@hydra.is/" "/")
> ("Inbox hydra@hydra.is/" "/") ("Inbox admin@hydra.is/" "/")
> ("Inbox hydra@internet.is/" "/") ("Inbox Listar@hydra.is/" "/")
> ("Inbox hus@hydra.is/" "/"))
> 3 OK NAMESPACE Completed
> 4 lsub "" "*"
> * LSUB () "/" "Inbox hus@hydra.is"
> 4 OK LSUB Completed
(In reply to comment #0)
> Steps to Reproduce:
> 1.make sub folder in your inbox namd "Inbox xxx@xxxx.xxx"
> 2.send some content to the folder
> 3.try to list content of folder
How/when did you create 'sub folder in your inbox named "Inbox hus@hydra.is"'?
As "Inbox hus@hydra.is" is a namespace, it should appear at folder as root level folder since initial, and if you created the folder as 'sub folder in your inbox", folder path should be "inbox/Inbox hus@hydra.is".
Did you create root level folder of "Inbox hus@hydra.is" before namespace of "Inbox hus@hydra.is" was defined as namespace at server?
Comment 9•15 years ago
|
||
(In reply to comment #8)
> yes sory it is a root folder.
If you are talking about root level folder named "Inbox hus@hydra.is", when/how did you create root level folder named "Inbox hus@hydra.is"?
Can you provide IMAP log since clean status(no root level "Inbox hus@hydra.is" nor no subfolder named "Inbox hus@hydra.is"), to 'creation of root level "Inbox hus@hydra.is"' or subfolder of "Inbox hus@hydra.is" of inbox?
Comment 10•13 years ago
|
||
can you reproduce this using a current version of thunderbird?
if you are unable to reproduce, please close by setting stats to resolved, and resolution to WORKSFORME or another appropriate setting.
If you are able to reproduce, add new details, and a testcase if one does not already exist in the bug report.
Whiteboard: [closeme 2012-03-25]
Reporter | ||
Comment 11•13 years ago
|
||
Hi yes
i currently have thunderbird 10.0.2 (linux) and Earlybird 12.0a2 (2012-03-09) (linux) installed and this is still current in them.
Comment 12•13 years ago
|
||
'3 select "Inbox hus@hydra.is/Inbox hus@hydra.is"' is executed by following request for root level folder named "Inbox%20hus%40hydra.is"(escaped in request).
> -856688880[7f78ce7d1120]: ccf55000:mail.hydra.is:NA:ProcessCurrentURL:imap://voggur@mail.hydra.is:993/select%3E/Inbox%20hus%40hydra.is: = currentUrl
Tb perhaps applied non-personal-namespace of ("Inbox hus@hydra.is/" "/") which is returned in lsub response of '* LSUB () "/" "Inbox hus@hydra.is"', instead of personal namespace of (("" "/")) which we want used by Tb.
Confirming per log.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 13•13 years ago
|
||
Do you need full utilizing of public namespace/other users namespace?
If no, "disabling of public namespace/other users namespace" is a simple workaround in your case.
Server Settings, Advanced button
Personal namespace: ""
Public(shared) : (nothing is written)
Other Users : (nothing is written)
[ ] Allow server to override these namespaces <= Uncheck
Issues in accessing to other user's Mbox for sharing("Inbox <username>@domain") may arise, but I think it's perhaps "write access error" only when you attempted to copy/move mail to other user's Mbox, even if issue in accessing occurs.
Comment 14•13 years ago
|
||
FYI.
Following is document for "permission" in namespace.
> http://wiki.dovecot.org/SharedMailboxes/Permissions
"permission" is done by IMAP acl and file system level access privilege. So, as far as "permission" is appropriately done at IMAP server and ACL is correctly supported by IMAP server, issue in "disable public namespace/other users namespace" is following only.
(1) Tb doesn't know about that "Inbox <username>@domain" is SharedMailbox.
(2) Tb can't ask user for "where folder is created" when user requests folder creation at IMAP account level. By 'Personal namespace: ""' only, folder creation request at IMAP account level is always interpreted by Tb as "creation of root level folder".
Comment 15•13 years ago
|
||
Vöggur ??
(In reply to WADA from comment #13)
> Do you need full utilizing of public namespace/other users namespace?
Comment 16•13 years ago
|
||
RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error please respond to this bug with your reasons why.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•