Hello,

It's actually a segregation issue with Microsoft Exchange.

It is most commonly happening when you have an environment merged, upgraded, or imported.

In basic essence each mailbox needs to have a Default Public folder assigned.

whenever nothing has been assigned to a mailbox it picks a random one (often one from a customer they got no access to which causes the login failure).

SolidCP by default generates a Public folder per organization and sets this as default for each mailbox within that organization.

Anything generated outside of SolidCP, Migrated, Imported, or maybe from an older exchange (such as exchange 2010) or for example created during websitepanel days might have this symptom.

We have created a powershell script to generate missing PF's per organization and set as default within that organization per mailbox: http://installer.solidcp.com/Files/stable/Tools/PFFix.zip

Please make sure you adjust the OU properties following your Active Directory and run it on an Exchange server with domain admin and Org management privs user.

If it errors for some (or even quite a few) that would be normal as it does not verify existing, it is made to error on existing and continue with the next only generating and assigning the missing ones. 

If you need any help we can always do this for you with our premium support.

Regards,

Marco Tiggelaar

Hi Marco, It's been a while since we had contact about this issue.
We dd manage to resolve it with the steps you provided. Thanks again.

However we recently created a new mailbox user in one of our customers sites and that user gets the password required message for that site's public folder.

We did rerun the sript you provided and this site does have a public folder so that's not the problem.

Is it safe to delete the public folder of that customer and let thew script you provided create a new one and let that fix the problem or can we fix this using a different method?

Thanks in advance.