lou kamenov ([EMAIL PROTECTED]) wrote: > > Actually I don't fully agree with you Mike.. yes there is control ( Depends > what control you want? Isn't it the same with the Exchange Public Folders?) > Exchange Public folders (Guess why its called 'public') is for sharing > calendar/notes/any shits to anybody in your _user group_. If you want more > privacy then use Net folders which infact is working nicely for small > workgroups.
If I chmod 755 /home/jacksonm and chmod 644 all the files inside, then I am sharing them with you but you can not add or delete them. Shared folders are designed to work exactly the same way, based on the permissions that are set by the user. In a virtual users environment, the user has no permission to even enter the directories in, for example, /var/qmail/maildirs, and probably does not even have a shell account on the mailserver. The concept of shared folders in this situation is either all or nothing. As soon as you introduce it to the users, somebody in management will demand that they want to be able to share a folder but that nobody else can add or delete to it. This is not possible in this scenario. It is not an acceptable level of control for nearly any environment that I can think of. If you want shared folders to work properly, you can not use a virtual users environment. And yes, qmail-ldap can work just fine in a normal user environment. Were this discussion taking place on the Courier IMAP list, Sam would probably give you some good advice or tell you that he will implement some changes. He is very reasonable, and has implemented a few of my requests in the past. -- Mike
