New Install of CP and everything on the mailbox front is working wonderfully. Started to try and get the Public Folder part going and hitting some roadblocks. Basically, I create a company and a few mailboxes, then go to the ‘Public Folders’ section. Under username, I enter ‘publicfolders’ and leave the domain as the default for the authoritative domain for the customer. I only have one Public Folder plan so I leave that selected. Click ‘Submit’ and I get the error:
The specified mailbox “publicfolders@domain.com” doesn’t exist.
I’m not sure if I missed a prerequisite step or what. The only public folder mailbox on the entire Exchange server is one called ‘Default Public Folders’ which I created via the ECP.
Am I missing a step or does this error indicate something else?
Just to follow up on this, I tried on another company…exact same process and it worked. However, of 3 companies that I have created, it only worked on 1 of them and failed (with the error above) on the other 2.
I’m working on trying to resolve this.
Basically this is what CloudPanel should do:
* Create new public folder mailbox for company ABC
* Create new parent public folder in that new mailbox
* Remove Default and Anonymous permissions
* Add permissions for that company
* Put email on public folder mailbox with company ABC primary domain
* Assign all users in that company to that public folder mailbox
Does all of this sound about right?
Which part is causing issues?
Jacob – On the 1 company that didn’t give me an error, it appears to have worked exactly as you described above. However, for the other 2 companies it never even creates the public folder mailbox. It just generates an error that reads
“The specified mailbox ?publicfolders@domain.com? doesn?t exist.”
<Where domain.com is the authoritative domain for the company>
So I’m basically stuck right out of the gate. I tried to figure out what was different about the companies but I can’t see a correlation.
There should be at least something in the logs. Please email me the logs after you generate the error again so I can look.
I am having a problem. Cloudpanel seems to create the public folders just fine and creates the necessary groups. The problem I get is that tenants can see each other folders. When I check permissions, it is all correct and only the people inside that organization should see the folder but this is not the case. it seems that all customers can see each other public folders. Any suggestions?
Sounds to me like the permissions are not correct and Default or Anonymous has access. Personally I would recommended holding off on Public Folders if you can until the new version is released because many people are having issues.
Hi Jacob,
thanks for adding public folders. Question – how can i add existing public folders to CP (just one PF for us)
Unfortunately, I cant because the tenants require public folders. At looking at my permissions as you suggested, I do notice that cloud panel creates the public folders on the root itself and not under Non_IPM_Subtree as Microsoft suggests. Any thoughts on that?
My permissions are right. on each folder, anonymous and default has no access and the author is set to the group that cloud panel created.
I’ve since tried to remove the public folder options from the control panel and now I cannot do so. Getting the error
You don’t have sufficient permissions. This operation can only be performed by a manager of the group.
Please refer me to the article about putting them under NON_IPM_SUBTREE because i’ve never seen that. Now if you are talking about NON_IPM_SUBTREE for the staging area then I have seen that but the public folders shouldn’t remain there.
In CloudPanel there is a table called PublicFolderMailboxes. It has a MailboxID column which is auto generated, CompanyID which matches the CompanyID on the companies table, PlanID which matches the public folder plan from the table Plans_ExchangePublicFolders and an Identity key which matches the email address used when creating the public folder mailbox.
You can manually add the public folder to that but CloudPanel doesn’t do anything with public folders. You can’t manage permissions or anything like that yet… that is what i’m currently working on.
The fix to my original problem was because “Default” user account was the owner to the root of public folders. Cloud panel creates a directory for your tenant on the root itself. I had to remove the rights from the “Default” user to none and allow only the two groups that Cloud panel created to have access. Doing this allowed each tenant to only see their respective folders. Jacob was correct. It was a permissions problem.
Jacob, I guess what could be nice is in the next version, if you could change the script to automatically remove the “default” user of its ownership rights as any new folder currently created inherits the “default” ownership permissions from the root. Problem is, we cannot remove the “Default” from the root itself because if you do, no one will be able to see any folders beneath it.
