219645 - imap #mh namespace broken

Status: RESOLVED FIXED

(MailNews Core :: Networking: IMAP, defect)

Description

[Peter Whaite]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827

imap #mh namespace (and by the looks of it all namespaces) are not correctly
sent in the 1.5b imap lsub command.  The problem is the imap directory is
prefixed to the namespace.  Compare 1.5a (which worked) with 1.5b as obtained
from the imap log:

   1.5a     lsub "" "#mh/"
   1.5b     lsub "" "~/.mail/#mh/"  

The imap directory should not be prefixed to namespaces.  Probably related to
same changes that incorrectly require "/" to be appended to imap directory name
as noted in another bug report.

Same for other namespaces like #news.

Reproducible: Always

Steps to Reproduce:
1. Enable imap logging
2. Connect to imap server.
3. Look at the lsub commands in the log.
4. Repeat for 1.5a and note differences.

Actual Results:  
   1.5a     lsub "" "#mh/"
   1.5b     lsub "" "~/.mail/#mh/"  


Expected Results:  
   1.5a     lsub "" "#mh/"
   1.5b     lsub "" "#mh/"  


Will have to stick with 1.5a until this is fixed.

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

I don't have an IMAP account to test with, but have you tried with a nightly
build?  There have been changes within the past week or 2 that might've fixed this.

Comment 2

[Peter Whaite]

Tried todays nightly (Build 2003091704) and it is still broken in exactly the
same way.

Comment 3

[David :Bienvenu]

Stephen made that suggestion because the bug about the trailing slash being
required for the online directory has been fixed - however, this bug is different.

Comment 4

[David :Bienvenu]

Attachment: proposed fix

check if mailbox name starts with namespace prefix.

Comment 5

[David :Bienvenu]

checked in, r/sr=mscott - please try tomorrow's 1.6 trunk build

Comment 6

[Jay Smith]

There was last discussion on this almost a month ago, but no indicationin the
discussion that anybody said "now it works".  However, the resolution is "fixed".

A post from David Bienvenu on Bug 227766 stated "I believe this has been fixed
in 1.6a/b" however, I can't find anybody else saying this.

It costs me a lot to hire somebody to do the installation (test) [and I am
concerned about "damaging" our 1.4 installation that is mission critical] so I
am hoping that I can get some additional confirmation on this bug.

Thanks.

Jay

Comment 7

[David :Bienvenu]

please don't install 1.5 if this bug concerns you. This is fixed in 1.6a/b and
will be in 1.6 final. 1.5 does not have this fix, and there has not been a point
release for 1.5, and thus, no point release with a fix.

Comment 8

[Peter Whaite]

I can confirm that this bug has been fixed in 1.6a (Build 2003110115).

On a related note I see that Thunderbird is now releasing nightly builds based
on the 1.6b code, so presumably this bug is fixed in those builds as well.