<p>I'm doing exactly what you want. The solution is very simple: create groups with accounting system of the operating system, where the public folders reside (in my case it's a Novell Netware server). Give groups needed rights to those folders. Accounting has to be handled by OS - not the software on that OS.</p><p>bye  Olaf</p><p> </p>

<p>Hi all,</p><p>Pegasus "public folders" are great in 2 aspects </p><p>1) you can have a folder hierarchy</p><p>2) all mails are single files </p><p>..but my problem is the definition of "public"</p><p>We are working in groups A.B,C and I would like to use public folders more flexible.</p><p>GroupA -> sees PublicF A </p><p>GroupB -> sees PublicF B</p><p>GroupC ->  sees PublicF A and PublicF B</p><p>The <b>workaround</b> can be, to run several instances of Pmail </p><p><b>My question is now, can separate instances of PMail be connected to the same public folder ?</b></p><p>(<i>also interesting for laptop-people in their office</i>)   </p><p>The <b>solution</b> would be, Pmail handles the connection to "public folders" on a user basis.</p><p>Every user can deside which "public folder" he wants to be connected to. </p><p>best regard khsti </p><p> </p><p> </p><p> </p>

Have you read the Public Folder help files?

<p>thanks, good answer </p><p>help file(s) ? -> no </p><p>online help -> yes </p>