Konstantin Kunshchikov wrote: > > >> > > <snip> > > >> > >> Yes, this is a problem with OE. Netscape Messanger works fine as expected. > >> But this may be also an architecture thing. "Shared Folders" and "Other > >> Users" > >> are in general virtual. > >> Its not possible to view ACL's of this folders with cyradm. > > > >The same can be said for "user" in the standard namespace. "user" is > >the prefix for the other users' namespace, just like "Other Users" and > >"Shared Folders" are prefixes for the respective namespaces. Even if OE > >doesn't support the NAMESPACE extension, a LIST command returns the > >\Noselect flag for the prefixes, which tells the client that these are > >not selectable mailboxes. > > For standard namespace I can create the top-level folder in hierarchy and > this is sufficient for OE. With altnamespace I don't. > > For example: > > cyradm>cm test.first > cyradm>cm test.second > > In that case OE failed, Netscape works fine and displays "test" hierarchy. > > For OE I can do: > > cyradm>cm test > > And now "test" subfolders works fine with OE. The same with user hierarchy. Either you are confused, or you're confusing me. "Toplevel" folders in the two namespace are entirely different. The only toplevel folders in the standard namespace are shared folders (INBOX is special, and doesn't count). The only toplevel folders in the alternate namespace are personal folders. If you look at the output of the NAMESPACE command, you'll see what the necessary prefixes are for mailboxnames. > > > >> Other things may also cause a problem. > >> For example, is it possible to drag mail in to the "Shared Folders"? > > > >It shouldn't be, and the server tells the client so as described above. > > > >> As I undestood, altnamespace has 2 major features: > >> > >> 1. Users subfolders at the same level of that user Inbox. > >> 2. "Shared Folders" and "Other Users" prefixes. > >> > >> I think making 1 and 2 separate with different switches in imapd.conf would > >> be > >> generally good idea, and solve the problem with OE too. > > > >1 and 2 can not be made mutually exclusive, either you get both > >(altnamespace) or neither (standard namespace). > > > >IMHO, the architecture is correct (similar to other commercial variants > >of Cyrus) and the problem lies completely with OE. > > This is completely OE problem. > In case of Standard Namespace we have to modify registry when user wants > to save his Sent mail on a server. > In case of AltNamespace user decides previous problem but have to use ugly > "GO TO" button to look through the Shared Folders. > If you open Shared Folders via "GO TO" button they'll dissapear > after Outlook restart. > Since OE exists one should fix its problems. I think that proper > patch for AltNamespace would be simple to make(may be #ifdef OE?) I don't understand what good an #ifdef would do. I am *very* reluctant to hack what I feel is a good and correct design just to fix the misbehavior of one (albeit popular) IMAP client. Unless someone can prove to me that the server is doing something incorrect, I suggest you do one of three things: 1. Complain to Microshaft about LookOut Express 2. Don't use the alternate namespace. 3. Use a different client. If your users really want Microsoft, then use Outlook. If you decide to do 2 or 3, I would still do 1. Ken -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
