• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Horde webmail won't let users past prompt

H

hostofthewest

Guest
Hi all,

Our users, and myself for that matter, are unable to get past a login prompt to webmail. The user goes to http://webmail.domainname.com and inputs [email protected] with the appropriate password. The login prompt is displayed again and again.

The account was migrated (backup and restore) from another Windows Plesk server. I'm not finding any relevant error logs and I have run defpackagemng.exe to correct the webmail virtual directory. As far as I can see everything looks correct.

Does anyone know of the solution to this problem?

Thank you,
-Bill
 
I have since realized that I shouldn't be seeing a login prompt from IIS but should see the login prompt from Horde instead.

Unchecked Integrated authentication and now of course I just get a 401 not authorized page.
 
To solve this issue try to do the following command:
"%plesk_bin%\defpackagemng.exe" --fix --type=webmail

Hope that helps a bit.
 
Yep, I've done that command a few times now also. No dice.

Thank you,
-Bill
 
Here's a few more details and the solution that worked for me to get this working again.

Basically the IIS anonymous user account wasn't able to authenticate with IIS to display the Horde webmail page. I was getting a 401.1 error on any webmail site.

The webmail virtual directory was setup correctly.

Running "%plesk_bin%\defpackagemng.exe" --fix --type=webmail didn't fix anything this time as it was a permissions issue and this executable doesn't appear to do anything with permissions.

What fixed the problem was to modify the default application pool to run under the local system in the identity tab under the properties of the pool. No, it's not the most secure thing to do but until I figure out a better solution it's going to be this way.

I hope this helps others who have run into this problem.

Thank you,
-Bill
 
Back
Top