• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Horde password change bug in 8.1

B

Bogdan

Guest
I'm not sure if anyone noticed this, but changing the password for a mailbox through horde doesn't work in Plesk 8.1.

I found this on 2 new servers that I set up with Plesk 8.1 and later on, on several Virtual Machines I used to test the Plesk upgrade process.

Whenever I try to change the passowrd from Horde, I get "Failure in changing password on poppassd server: Incorrect Password" although I entered the correct username and password.

According to KB articles on this:
http://kb.swsoft.com/article_155_1378_en.html
http://kb.swsoft.com/article_155_1373_en.html
I'm suppose to check if the PopPassD service is running (and it is). Furthermore, I can use the telnet command to connect to the poppassd service on port 106 and I'm able to successfully change the password (following the instructions on http://kb.swsoft.com/article_155_1378_en.html)

I sent a ticket to SWsoft about this and it's been over 4 days and still no solution (they've been moving my ticket from the support and development departments back and forward a couple of times though).

Can anyone else confirm this issue?
 
Your support coordinator was very helpful (although it took more than 4 days to get to him) and shed some light on this.

Changing the password from horde works ONLY if you connect to webmail using the domain's webmail FQDN (for example webmail.domain.com) and I was using the IP to connect (http://IP:8425). Since using the FQDN works, there shouldn't be many problems with this, but you may still want to fix this bug in a future version.
 
Back
Top