- Server operating system version
- AlmaLinux 9
- Plesk version and microupdate number
- Plesk Obsidian 18.0.73 Update #4
We have server version:
Which means things like https://support.plesk.com/hc/en-us/...n-type-after-update-to-Plesk-Obsidian-18-0-73 doesn't apply. However, we have two domain accounts which are both on the same server and both successfully connect to emails -- but one connects with encrypted password (CRAM-MD5) and the other connects via PLAINTEXT , but we can't see how to make the Plaintext connection work using Encrpyted password.
We have found these two accounts "encrpyted_domain" and "plaintext_domain" are on different subscriptions with different Service Plans and I assume something in these settings enable/disable email password encrpytion, but digging into the subscription and/or service plan options, we can't see what to tweak so that both subscriptions/service plans enable email password encryption.
All connections are via SSL/TLS
Plesk Obsidian 18.0.73 Update #4
Web Host Edition
Last updated on Nov 19, 2025 03:50 AMWhich means things like https://support.plesk.com/hc/en-us/...n-type-after-update-to-Plesk-Obsidian-18-0-73 doesn't apply. However, we have two domain accounts which are both on the same server and both successfully connect to emails -- but one connects with encrypted password (CRAM-MD5) and the other connects via PLAINTEXT , but we can't see how to make the Plaintext connection work using Encrpyted password.
We have found these two accounts "encrpyted_domain" and "plaintext_domain" are on different subscriptions with different Service Plans and I assume something in these settings enable/disable email password encrpytion, but digging into the subscription and/or service plan options, we can't see what to tweak so that both subscriptions/service plans enable email password encryption.
All connections are via SSL/TLS