• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk 8.1 SMTP Error

P

PE-Steve

Guest
Hello,

We're having a bit of an email problem since the upgrade from 8.0.1 to 8.1. Our email relaying is set to use SMTP authentication, although the SMTP server rejects passwords in Plain Text but works when using CRAM-MD5 password encryption.

Any ideas to temporarily fix this, as well as [hopefully] information from SWSoft on whether this will be fixed or not.

Regards,
Steve
 
what distro are you running plesk on?
anyone else is having this issue?
that is surelly a no-go for me, i guess most of my users are using plain auth... if that stops working my helpdesk will become a mess!
 
Running CentOS4.2. We, along with our datacenter, looked at it for hours and the only fix we could find for it was CRAM-MD5.

-Steve
 
Originally posted by davegarbs
Sure, but where is that option in Plesk?

Encrypted password can be created using creation utilities only. Refer to /usr/local/psa/bin directory.
 
Back
Top