• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Question Problem setting crypted e-mail password via XML API

messju

New Pleskian
Hi,

after upgrading from Onyx to Obsidian I have a problem with the XML API.

If I update a plesk users password via the XML API, the user can not access mail via IMAP anymore.
The API responsds with OK and the new password works for logging in to the PLESK web-frontend, but not for IMAP. So it seems, my request is correct.
Everything works if I use password type <plain>, but not for type <crypt> (which I need).

I this a known bug or caused by some mail-server setting?
The same requests worked fine on Onyx, but don't work anymore.

kind regards
messju
 
Are you able to login to webmail?

If you run the command cat /etc/postfix/sasl/smtpd.conf on your server, whats the output?

Also have a look in in your mail log and see what authentication method is used when you try to login with IMAP. In the example log entry below CRAM-MD5 is used.

Code:
Jul 19 23:03:30 cp dovecot: imap-login: Login: user=<[email protected]>, method=CRAM-MD5, rip=::1, lip=::1, mpid=19663, TLS, session=<ZDr5RIDHpK4AAAAAAAAAAAAAAAAAAAAB>
 
Thanks for the fast reply and sorry for my late one.
You got me on the track: I tested webmail and the login worked. My first assumption that the IMAP password is not set correctly was wrong since I was pretty sure webmail does authenticate against dovecot. I double checked and found some misconfiguration on my test-client side and now everything works.

thanks and greetings
messju
 
Back
Top