Facebook
Twitter-
We value your experience with Plesk during 2024
Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
Please take this short survey:
https://pt-research.typeform.com/to/AmZvSXkx -
The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
-
We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.
Encrypted password auth does not work after update to plesk 10.4.4
- Thread starter Mshaker
- Start date
More detailed report.
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
plesk 10.4.4 CentOS 5 1013111102.18 , CentOS release 5.7 (Final), x64
PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
After upgrading from plesk 10.3 to plesk 10.4.4 mail users cannot authenticate using "encrypted password" auth in their mail clients (changing it to plaintext will work).
When setting up an email account in most major email clients (thunderbird, mac mail etc) it will automatically test to see what auth the server supports and choose the best one (previous plesk versions supported encrypted password auth so all the mail clients are using this).
ACTUAL RESULT
After the plesk upgrade all mail users get a password popup box telling them that they have entered the wrong password. The only fix is to switch the authentication method in their mail client to "plaintext".
EXPECTED RESULT
The mail server should support encrypted password auth like previous plesk versions
ANY ADDITIONAL INFORMATION
Just a note that our MTA is set to use qmail.
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
plesk 10.4.4 CentOS 5 1013111102.18 , CentOS release 5.7 (Final), x64
PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
After upgrading from plesk 10.3 to plesk 10.4.4 mail users cannot authenticate using "encrypted password" auth in their mail clients (changing it to plaintext will work).
When setting up an email account in most major email clients (thunderbird, mac mail etc) it will automatically test to see what auth the server supports and choose the best one (previous plesk versions supported encrypted password auth so all the mail clients are using this).
ACTUAL RESULT
After the plesk upgrade all mail users get a password popup box telling them that they have entered the wrong password. The only fix is to switch the authentication method in their mail client to "plaintext".
EXPECTED RESULT
The mail server should support encrypted password auth like previous plesk versions
ANY ADDITIONAL INFORMATION
Just a note that our MTA is set to use qmail.
S
Sanderv
Guest
Just to be sure, this fix will make it possible to use encrypted passwords for mail-users? Currently planning migrations of servers from plesk 9.5.4 to 10.4.4, with a lot of encrypted passwords. Is there any ETA for when this fix will be available?
J
jan_s
Guest
waiting for updates...
hey! anyone have updates for this problem? all ios-devices can't connect to the mailserver... that's very bad!
maybe a workaround will be help me (and other)....
hey! anyone have updates for this problem? all ios-devices can't connect to the mailserver... that's very bad!
maybe a workaround will be help me (and other)....
Please install MU#5 http://kb.parallels.com/en/112937 where this issue was fixed.
H
hostfan
Guest
Does not work with MU#15
How it can be reproduced?
Just try to login with ATMail (IMAP) or same with telnet localhost 143, but for some users work and for some no.
I did not checked yet, but I think work with users with encrypted pass (new accounts) and not work with PLAIN passwords saved in the past. I am not quite sure, but as I remember it was like this.
Now we solved temporarelly to login with Horde and modified Horde to login with POP3.
I did not checked yet, but I think work with users with encrypted pass (new accounts) and not work with PLAIN passwords saved in the past. I am not quite sure, but as I remember it was like this.
Now we solved temporarelly to login with Horde and modified Horde to login with POP3.
H
hostfan
Guest
Hello,
I created a new mail account with encrypted password on our testsystem, but can't login yet.
So I can't confirm this behaviour with plain/encrypted passwords.
@IgorG:
I don't understand... reprodcue in which way?
plain password over IMAP -> not work (thats ok)
plain password over SSL/TLS -> work
crypt password CRAM-MD5 over IMAP/S -> both not work
crypt password SHA1 over IMAP/S -> both works
plain password over IMAP -> work
iphone/ipad -> can't test this at the moment,but expected probadly not work
I created a new mail account with encrypted password on our testsystem, but can't login yet.
So I can't confirm this behaviour with plain/encrypted passwords.
@IgorG:
I don't understand... reprodcue in which way?
plain password over IMAP -> not work (thats ok)
plain password over SSL/TLS -> work
crypt password CRAM-MD5 over IMAP/S -> both not work
crypt password SHA1 over IMAP/S -> both works
plain password over IMAP -> work
iphone/ipad -> can't test this at the moment,but expected probadly not work
Please fill template http://forum.parallels.com/showthread.php?t=106113 with all necessary details, logs. I will forward this report to developers.
H
hostfan
Guest
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
plesk, 10.4.4 MU#15, Debian Squeeze 6.0.4, x64
PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
No Login with CRAM-MD5 against POP3, IMAP, SMTP after upgrade.
Starting situation was Debian Lenny 5.0.9 64-bit with Plesk 10.3.1
We updated in the following order:
1.) Upgrade Plesk to 10.4.4 MU#15 lenny-build
2.) Upgrade OS to Debian Squeeze 6.0.4 with autp-get dist-upgrade
3.) Upgrade Plesk to 10.4.4 MU#15 squeeze-build
ACTUAL RESULT
After upgrade, no login for mail-clients with CRAM-MD5 ist possible (bad username/password).
At this moment, we have tested the following ways:
plain password over IMAP -> not work (thats ok)
plain password over SSL/TLS -> work
crypt password CRAM-MD5 over IMAP/S -> both not work
crypt password SHA1 over IMAP/S -> both works
plain password over IMAP -> work
iphone/ipad -> can't test this at the moment,but expected probadly not work, because client requeires CRAM-MD5
EXPECTED RESULT
The mail server should support encrypted password auth like previous plesk versions, in this case CRAM-MD5 works well.
ANY ADDITIONAL INFORMATION
We use standard-setup -> courier-imap and qmail
plesk, 10.4.4 MU#15, Debian Squeeze 6.0.4, x64
PROBLEM DESCRIPTION AND STEPS TO REPRODUCE
No Login with CRAM-MD5 against POP3, IMAP, SMTP after upgrade.
Starting situation was Debian Lenny 5.0.9 64-bit with Plesk 10.3.1
We updated in the following order:
1.) Upgrade Plesk to 10.4.4 MU#15 lenny-build
2.) Upgrade OS to Debian Squeeze 6.0.4 with autp-get dist-upgrade
3.) Upgrade Plesk to 10.4.4 MU#15 squeeze-build
ACTUAL RESULT
After upgrade, no login for mail-clients with CRAM-MD5 ist possible (bad username/password).
At this moment, we have tested the following ways:
plain password over IMAP -> not work (thats ok)
plain password over SSL/TLS -> work
crypt password CRAM-MD5 over IMAP/S -> both not work
crypt password SHA1 over IMAP/S -> both works
plain password over IMAP -> work
iphone/ipad -> can't test this at the moment,but expected probadly not work, because client requeires CRAM-MD5
EXPECTED RESULT
The mail server should support encrypted password auth like previous plesk versions, in this case CRAM-MD5 works well.
ANY ADDITIONAL INFORMATION
We use standard-setup -> courier-imap and qmail
Last edited by a moderator:
H
hostfan
Guest
H
hostfan
Guest
Hi,
the capability AUTH=CRAM-MD5 exists, that was not the problem.
But I have good news, we applied MU#16 via autoinstaller from command prompt, since them CRAM-MD5 is working well, like before.
Don't know what happened, because CRAM-MD5 is not listed as Bugfix in MU#16.
I saw, while applying MU#16, autoinstaller applied all MU's again. Maybe something went wrong in MU#5-Install in our first upgrade.
the capability AUTH=CRAM-MD5 exists, that was not the problem.
But I have good news, we applied MU#16 via autoinstaller from command prompt, since them CRAM-MD5 is working well, like before.
Don't know what happened, because CRAM-MD5 is not listed as Bugfix in MU#16.
I saw, while applying MU#16, autoinstaller applied all MU's again. Maybe something went wrong in MU#5-Install in our first upgrade.
F
Fermina
Guest
hostfan,
tried doing a micro update for MU#16 using Parallels Panel GUI but my "Update Components" is greyed out. So does this mean I have to do it from the command prompt as you did?
tried doing a micro update for MU#16 using Parallels Panel GUI but my "Update Components" is greyed out. So does this mean I have to do it from the command prompt as you did?
H
hostfan
Guest
Hello,
I executed: /usr/local/psa/admin/sbin/autoinstaller --select-release-latest --upgrade-installed-components
