30363 - Cyrus IMAP:Should display error message when users trying to create "." fodler name or folder name ends with "." from the Cyrus IMAP server

Status: VERIFIED INVALID

(MailNews Core :: Backend, defect, P3)

Description

[Karen Huang]

Used 03-02-08/09-M15 commercial build:

This bug is tracking specifically for Cyrus IMAP server.

We should have a way to solve folders' names with "." problem specific for Cyrus 
IMAP server

Test results for "." & "g.h": 
".": 
Actual results: Did not display any error message.
Expected Results:  Since this is ends with a hierarchy separator for Cyrus IMAP,
so it should display error message to warn users that this is invalid mailbox 
name.
Additional Info: There was a bug#20599 logged is regarding to "." folder should 
display successfully on 5.0 client UI since that bug is for others' IMAP servers
(NMS,UW,MSexchange,SIMS

"g.h": 
Actual results: will create "g" for the first level folder & create "h" for the 
2nd level since there was no way to aviod this problem in seamonkey for Cyrus 
IMAP server yet!!

Expected Results: Should allow user to create g.h scuuessfully in Cyrus IMAP 
server

Comment 1

[Phil Peterson]

Reassign to jefft, cc bienvenu

Comment 2

[Karen Huang]

Oops! Additional Info should be bug#29599...(not 20599). 

Comment 3

[selmer (gone)]

Mass moving to M16 to get these off the M15 radar.  Please let me know if this
is really an M15 stopper.

Comment 4

[selmer (gone)]

Not beta2 stopper, marking M18.  Please add beta2 keyword if you disagree.

Comment 5

[kmurray1115]

Need more info. How prevalent are Cyrus IMAP servers? 

Comment 6

[lchiang]

I believe Cyrus IMAP servers are fairly popular/standard.  jgmyers can answer 
for sure.

Comment 7

[kmurray1115]

jgmeyers: does this impact the use of NSCP6 with Cyrus IMAP servers, or is this 
just an isolated case?

Comment 8

[John G. Myers]

I'm sorry, I don't understand the description of the bug.

Comment 9

[Karen Huang]

I think that I didn't describe very well in the description.
The problem here is:

1) For "." -- If tried to create "." folder name from the Cyrus IMAP server:
* Actual Results is: nothing happened, didn't display any error message.
* The expected results should be: Should display an error message: "The current 
command did not succeed. The mail server responded Invalid Mailbox name" 
(Since "." is hierarchy separator for Cyrus IMAP, so users shouldn't allow to 
create "." folder name from the Cyrus IMAP server)

2) For "g.h" -- ignore this problem for this bug since create "g" for the first 
level folder & create "h" for the 2nd level which work correct for this part.

Updating the summary to make more clear which is: "Should display error message 
when users trying to create "." folder name from the Cyrus IMAP server".

Adding interop for the keywords.

Comment 10

[Karen Huang]

The error should also display when users tried to create folder name ends with 
"." (e.g. "Jeff.", "Kevin."....etc). Adding "folder name ends with ." in summary 
too.

Comment 11

[kmurray1115]

The question for jgmeyers is: " Are Cyrus IMAP servers fairly 
popular/standard?" This will impact whether or not we prioritize this as a beta3 
bug or future it.

Comment 12

[John G. Myers]

I don't have market share information for Cyrus servers.  They do have some 

amount of popularity, but not as much as UWash servers.



I doubt this is a bug with the client.  If the server doesn't issue an error 

message for "CREATE ." then there is little reason for the client to issue an 

error.



Unless the client special-cases folder names like "Jeff/" or "Kevin/" when 

talking to "/"-delimited servers, it should not special-case folder names like 

"Jeff." or "Kevin." when talking to "."-delimited ones.

Comment 13

[Karen Huang]

So, do you mean that because of the error not be creted from the Cyrus 
IMAP server, so that's why client won't handle it at all?

Comment 14

[Karen Huang]

I know bug 29926 already address the "/" & "Jeff/" problem.
If based on John's comments, I will suggest bug 29926 should be in nsbeta3 
instead of this one......

Comment 15

[John G. Myers]

Someone would have to look at an IMAP telemetry log to determine whether or not 
the Cyrus server is generating an error.  I suspect that it is not.

Comment 16

[Karen Huang]

I didn't see the error from the log yesterday. I will try again.

Comment 17

[Karen Huang]

Attachment: Attached the Cyrus IMAP log when creating "." & "Kevin." folders

Comment 18

[Karen Huang]

--------------------------------------------------------------------------------
13 create "INBOX.Kevin."-3660225[3c6bec0]: 
buggy.mcom.com:S-INBOX:CreateNewLineFromSocket: 13 OK 
Completed-3660225[3c6bec0]: buggy.mcom.com:S-INBOX:SendData: 14 subscribe 
"INBOX.Kevin."-3660225[3c6bec0]: buggy.mcom.com:S-INBOX:CreateNewLineFromSocket: 
14 NO Subscribe-3660225[3c6bec0]: buggy.mcom.com:S-INBOX:SendData: 15 list "" 
"INBOX.Kevin."-3660225[3c6bec0]: buggy.mcom.com:S-INBOX:CreateNewLineFromSocket: 
15 OK Completed-3660225[3c6bec0]: buggy.mcom.com:S-INBOX:SendData: 16 create 
"INBOX.."-3660225[3c6bec0]: buggy.mcom.com:S-INBOX:CreateNewLineFromSocket: 16 
OK Completed-3660225[3c6bec0]: buggy.mcom.com:S-INBOX:SendData: 17 subscribe 
"INBOX.."-3660225[3c6bec0]: buggy.mcom.com:S-INBOX:CreateNewLineFromSocket: 
17 NO Subscribe-3660225[3c6bec0]: buggy.mcom.com:S-INBOX:SendData: 
18 list "" "INBOX.."-3660225[3c6bec0]: 
buggy.mcom.com:S-INBOX:CreateNewLineFromSocket: 18 OK Completed
----------------------------------------------------------------------------
Yes. No error display on the IMAP telemetry log.
So, is this Cyrus IMAP bug?

Comment 19

[John G. Myers]

Yup, a bug in the server.  Could you report this to [e-mail] ?
Then I'd close this bug as INVALID.

Comment 20

[Karen Huang]

Looks like that we found the Cyrus IMAP server problem!!
I already email to them -- Done for this bug.
Jeff is in sabbatical, either David or John can mark this bug "invalid", then I 
can verify to close this bug.

Comment 21

[John G. Myers]

Closing INVALID

Comment 22

[Karen Huang]

Verified. -- Thanks John.