Closed Bug 2734 Opened 26 years ago Closed 24 years ago

"~/imapdirectory/" problem with UW server

Categories

(MailNews Core :: Backend, defect, P2)

Product:
MailNews Core
Component:
Backend
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: scurtis, Assigned: jefft)

References

Details

Attachments

(2 files)

Attached IMAP log file for "~/imapmail/"
36.59 KB, text/plain
Details
UW IMAP log with the "~/imapmail_uwtest2/" advanced setup
77.46 KB, text/plain
Details 
(This bug imported from BugSplat, Netscape's internal bugsystem.  It
was known there as bug #334199
http://scopus.netscape.com/bugsplat/show_bug.cgi?id=334199
Imported into Bugzilla on 01/27/99 18:46)

I got this one from a user using WinNT, and I was able to reproduce it with
Win95 and Linux.

He had a UW-looking server (he said it was called FreeIMAP).

He set up his Advanced IMAP preferences as follows, apparently led to do so by
what worked for him in 4.0x.

*IMAP mail directory  "~/imapmail/"
Show only subscribed folders checked
Server allows folders containing messages and subfolders checked

*Namespaces: [defaults, let server override]

(* Necessary for reproduction)


His claim was that he could create and file to folders other than his inbox, but
could not open them to see what was inside.

As it turned out, we were creating the folders in the right places, and the file
URL worked fine, but we weren't doing a SELECT on the folders when they were
clicked on, although we were displaying them in the folder pane and the
Subscribe pane.

The real bummer here is that even after I had him change his IMAP mail directory
to just "imapmail", it still didn't work. I'm not sure if this much is our bug
or a UW server bug, but it seems that the reason it didn't work is because of
the way the UW writes out its .mailboxlist file in the user's home directory.
Entries in this file are supposed to reflect the folders present, and I don't
know how much this file affects Communicator, but our folder-creating actions
had apparently created the lines
~/imapmail/[foldername1]
etc., in the file.

The only way I was able to get Communicator to be able to select the folders
again with my Unix build was to delete the ~/imapmail/[*] lines from the
.mailboxlist file. They were then regenerated as more normal-looking
imapmail/[*] lines.

On Windows, there was an interesting interim display period after the directory
name had been specified correctly and before the .mailboxlist file had been
modified. The folders were then selectable, but there appeared also a shared
folder hierarchy that contained the identical foldernames, and they were all not
selectable. On Unix, I got the shared, non-selectable folders, but no usable
folders back.

This seems to be an unhappy meeting of some of our users' 4.0x conventions, the
~ symbol as an understandable indicator of HOME, and the ~ symbol as the default
representation of other users' namespace by the UW server, and I haven't been
able to find a workaround that doesn't involve tinkering with server files.

Tested on both carbuncle and wensleydale UW servers.
Batch reassigning chrisf's empty-TFV bugs to mscott and marking TFV 5.0
<sorry for the bug notification intrusion> I (or someone else) will be moving
enhancements, etc, bugs targeted for 5.0 to bugzilla in the near future.

Phil, The reassignment part didn't work on the bugs you've processed.
Assignee: chrisf → mscott
QA Contact: 4098
Setting all current Open/Normal to M4.
This has a current target milestone of M4.  Would you consider this an M4
stopper?  If not, please change the milestone accordingly.
Target Milestone: M4 → M7
push to M7...we don't have imap in mozilla.
Status: NEW → ASSIGNED
Target Milestone: M7 → M10
I didn't quite push this one far enough. I'm still not at the point where I'm
fixing bugs that were in 4.5x yet....=(
OS: Linux → All
correcting OS to ALL
Not sure I completely understand this bug. This would be nice to have for PR1,
but I would not consider it a blocker since it deals with advanced IMAP settings
Target Milestone: M10 → M14
Post beta 1.
I have problems with IMAP-rootfolders, too.

I'm using something like "root/" (no "~") for "IMAP server dir." in 4.6 Linux
and imported prefs to moz.

Mozilla seems to completely ignore the IMAP root setting. It accesses INBOX and
creates a "Trash" in the home dir on the server, but doesn't even show up any
folders in ~/root, althought they're correctly listed in .mailboxlist.

BTW: "Subscribe..." fails on existing folders.
QA Contact: scurtis → huang
Is the subscribe problem limited to IMAP-uw or my setup? If not, I'd create a
new bug.
Blocks: 17446
No longer blocks: 17446
Blocks: 17445
Summary: "~/imapdirectory/" problem with UW server → [DOGFOOD] "~/imapdirectory/" problem with UW server
Marking dogfood, since this makes Messenger nearly unusable for me.
Whiteboard: [PDT-]
Dogfood is for internal Netscape development.  PDT-.
Whiteboard: [PDT-]
The commercial build.  And yes, mozilla of course.  But we do not need this for
dogfood.  Beta yes.
leger,
I'm confused. Could you please define "we" for dogfood?
We for commercial dogfood is internal Netscape folks.
Whiteboard: [PDT-]
We value the UW server, and would appreciate any work external developers can
work on to assist with this.  This WILL be fixed for BETA.  But is not needed
for dogfood at this time.
My problem is not your valuation of the UW server, but that you make a
distinction between "internal" and "external". If you say, I don't qualify as
Mozilla developer, because I didn't contribute enough code yet, that's
completely OK with me.

But if you say, that only Netscape employees can participate in the dogfood
program, I would regret, that you're not as open as I thought you would be. Of
course, that's your right, but I don't think, you should mention the program on
Mozilla resources, then.

And I ask myself, why you released the source, if you're not willing to go the
road down and stop at in comparision unimportant points.
4.x has a user_pref("news.imap_sentmail_path", "IMAP://user@myserver/Sent"),
which seems to be converted to a user_pref("mail.identity.id1.fcc_folder",
"imap://user@myserver/Sent"); (and some others) for Mozilla. After changing it
to "imap://user@myserver/root/Sent", fcc works.

I still can't see my folders (not even the Sent folder). Subscribe now
coredumps. Obviously,
user_pref("mail.imap.server.myserver.server_sub_directory", "root/"); seems to
unused.
Depends on: 20878
Found the two problems in my case. Filed bugs #20878 and #20879
No longer blocks: 17445
Summary: [DOGFOOD] "~/imapdirectory/" problem with UW server → "~/imapdirectory/" problem with UW server
Removing DOGFOOD as my problem is covered better by the two bugs above now.
cc'ing bienvenu. David, do you think this is a beta stopper? As far as I can
tell, Ben's comments boiled down into two new bugs, so this bug is only about
the stuff imported from Bugsplat.
I'm not sure if it's a beta stopper or not. I think Ben's basic problem is
covered in a few other bugs. If we can get users of the UW server basically
working on mozilla (as well as 4.5 works), I think that's OK for beta. The
biggest problem people are seeing is 7511, which I'd like to fix ASAP.
Whiteboard: [PDT-]
Yes, my "problems" are described in the 2 other bugs now. However, I have a
solution workable for "DOGFOOD" for them (it involves logging into the server
and some errors in 4.x, but OK for now). Clearing Status Whiteboard.

I don't think, I see the original problem (from BugSplat) of this bug, but as
this bug really depends on 20878, of course I can't tell it for sure now.
So, what's the real remaining bug here? Karen, can you review the steps and
clarify what's left? I'm wondering if we shouldn't just close this and use the
other bugs mentioned.
Target Milestone: M14 → M15
What remains is the original problem (from BugSplat), but this really depends on
20878.
I need to take a look for this bug & bug#20878 to know what's the real 
remaining...
Yes. I am able to recreate this problem from 4.7, too.

UW IMAP server profile A:
1) with the following Preferences setup:
 Advanced IMAP preferences:  "~/imapmail/" 
 "Checked" Show only subscribed folders checked
 "Checked" Server support folders containing subfolders and messages
 "Checked" Allowed server to override these namespaces.
2) Steps:
   - open this mail account , only see inbox & trash initially
   - allow to create new folders: (test_f1 & test_f2), 
     but after copy message to these two folders, no messages displayed
from          this two folders

2) Actual Results: 
 - will only display the summary file with the Inbox, Trash & new
created           folders and ignore the other existing folders
 - Select the new created folders and tried to see the copied msg from inbox
to     this folder, not found.
drwxr-xr-x   2 khuang   khuang       1024 Jan 31 14:36 .
drwxr-xr-x   3 khuang   khuang       1024 Jan 31 14:26 ..
-rw-r--r--   1 khuang   khuang      34952 Jan 31 14:36 .Inbox.summary
-rw-r--r--   1 khuang   khuang      16384 Jan 31 14:35 .Trash.summary
-rw-r--r--   1 khuang   khuang      16384 Jan 31 14:36 .test_f1.summary
-rw-r--r--   1 khuang   khuang      16384 Jan 31 14:36 .test_f2.summary   
3) IMAP log file: please see following attached IMAP log file.   




I attached the IMAP log files as following, hope it will help for debugging this
problem:
> (This bug imported from BugSplat
[...]
> Server allows folders containing messages and subfolders checked

For the record: This setting is wrong for the UW server.
So, do you mean that it should be "Unchecked" Server support folders containing
subfolders and messages? Can you explain why this setting is wrong for the UW
server?
Karin,
Yes, you have to uncheck it for the UW-IMAP server.
Why? It doesn't support these hybrid folders due to its mailbox format.
Yes. Maybe the initial record is wrong.
I got an error if I tried to create subfolders, the error is as following:
"The current command did not succeed. The mail server responded: CREATE failed:
cannot create mailbox node /home/uwtest/uw_f10/: File exists."
It seems that the UW does not support folders containing subfolders and
messages...Scott, have you tried this yet?
Yes. Thanks for correcting this bug. 
The initially record's setup is not correct.
I am going to try again with the correct setup.
OK. I tried again with the UW correct setup on 4.7 and the results are as
following:

**Setup:
I set up three profile as following:
A) Profile name: imapmail_uwtest
 Advanced IMAP preferences:  Blank 
 "Checked" Show only subscribed folders
 "Unchecked" Server support folders containing subfolders and messages
 "Checked" Allowed server to override these namespaces.
Actual Results: Can view existing folders,can create folders, can copy & view
msgs from the new created folders. (It displayed all the summary files)

B) Profile name: imapmail_uwtest2
 Advanced IMAP preferences:  ~/imapmail_uwtest2/
 "Checked" Show only subscribed folders
 "Unchecked" Server support folders containing subfolders and messages
 "Checked" Allowed server to override these namespaces.
Actual Results: CANNOT view existing folders,can create folders, CAN copy but
CANNOT view msgs from the new created folders. (It ONLY displayed the new
created summary files)

C) Profile name: imapmail_uwtest3
 Advanced IMAP preferences:  imapmail_uwtest3
 "Checked" Show only subscribed folders
 "Unchecked" Server support folders containing subfolders and messages
 "Checked" Allowed server to override these namespaces.
Actual Results: CANNOT view existing folders,can create folders, CAN copy & view
msgs from the new created folders. (It ONLY displayed the new created summary
files)

IMAP logs are all available, but I just attach for this bug's original problem
which is "profile B) imapmail_uwtest2" log file as following:



mozilla@bucksch.org, David or Scott,
My question is: Should the existing folders disappear after set up the Advanced
IMAP preferences to  ~/imapmail/ or imapmail ? 

Karin, did you delete the .mailboxlist file in th ehome dir on the server every
time you changed the IMAP server dir in the advanced settings?
/Ben Bucksch
Yes. After I delete the ~/imapmail/[*] lines from the .mailboxlist file. 
They were then regenerated for imapmail/[*] lines.
And the results are described as above...

Cc: Phil & answer Phil's 2000-1-27 10:28 comments' questions:
Based on above investigation, it seems that what the real remaining/left will 
be as following:
1) " ~/ " problem: for some reason, either server or client ignore the "~/".
2) Because of the previous problem, after created the new folder, it just cannot 
implement to view the msgs from the created folders.
3) "dual_use_folder" problem.

It seems that if fix the bug#20878 & bug#20879, this bug's problem will be 
solved.
** I will suggest to leave this bug open since this bug included more detail 
description and this way will also keep track for the original problem got 
fixed!!
Assignee: mscott → jefft
Status: ASSIGNED → NEW
Load balancing to jefft whose done a lot of work already for us with UW servers.
Target Milestone: M15 → M16
Status: NEW → ASSIGNED
Not M16 stopper, marking M17.  Please add beta2 keyword if you think this is a 
beta2 stopper.
Target Milestone: M16 → M17
I believe this is fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
> It seems that if fix the bug#20878 & bug#20879, this bug's problem will be 
solved.

Yes. This is fixed along with the fix of bug 20878 & bug 20879.

I did verified again on today's 08-02-05-M17 commercial build for all the 
platforms (Linux, WinNT & Mac platforms) for both "~/imapdirectory/" & 
"imapdirectory" IMAP server directory and they all have be fixed.
After created the new folder, it can implement to view the msgs from the created 
message-only folders now. Marking as verified!!
Status: RESOLVED → VERIFIED
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: