On October 19, 2021, we have enabled single-sign-on for our Plesk Support Center to provide a seamless login/account experience. This implies that you’ll be able to use a single account across any of our web-facing properties.
If you had already registered your account at MyPlesk.com/Plesk360/Platform360 please use one for login. Otherwise please re-register it using the same email address as your existing Zendesk login (support account). It’s essential that you use the same email address on our support center to ensure that your tickets stay attached to the same account.

Cannot set up Plesk mail IMAP account in Outlook: SASL DIGEST-MD5 authentication failed: authentication failure

Follow

Comments

13 comments

  • Avatar
    King555

    This work-around is not only required for Outlook users, but also for users of the Android app "Samsung Email".

    4
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    @King555

    Thank you for sharing this information.
    The article was updated.

    0
    Comment actions Permalink
  • Avatar
    Andreas Hendrickx

    Just some extra info for somebody who might encounter this. I am using the Outlook version coming with the Office 365 package. I was unable to setup IMAP. It simply failed without any additional information. A POP3 connection worked. I do use Samsung Mail  on my Android phone and there it worked fine.

    This solution fixed my Outlook setup problems. And as a bonus made retrieving mails via Samsung mail three times as fast

    0
    Comment actions Permalink
  • Avatar
    Alisa Kasyanova

    @Andreas Hendrickx
    Thank you for the information! I am sure other Plesk users will find it useful.

    0
    Comment actions Permalink
  • Avatar
    Andreas Hendrickx

    The issue returns after a while. The same steps fix it. I assume the configuration file get changed by an update. It is kind of annoying to ind out that suddenly all my customers have outlook problems and to go to the same steps again. Is there a way to fix the change ? Or any sight on a permanent solution.

    I understand that in its core this is an Outlook problem. But it is one of the most used application by my customers.

    1
    Comment actions Permalink
  • Avatar
    Alexander Tsmokalyuk

    @Andreas I have fixed the article. The custom configuration file should not be rewritten by the updates. Thank you for the reporting the issue.

    1
    Comment actions Permalink
  • Avatar
    Andreas Hendrickx

    Alexander Tsmokalyuk Thanks !! I give it a go :)

    1
    Comment actions Permalink
  • Avatar
    Jay Ambrose (Edited )

    Thanks for sharing this. This works perfectly!

    0
    Comment actions Permalink
  • Avatar
    Madhavi Chandrasekaran

    Hi , I am not a techie. How can i get it to work again in my Outlook? It used to very well until recently. THanks!

     

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Madhavi Chandrasekaran

    In that case, the suggestion is to submit a request for support, depending on where Plesk license was purchased https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-

    0
    Comment actions Permalink
  • Avatar
    Brandon Yap

    Putting the setting in 00-auth_mechs.conf doesn't seem to take effect. When Plesk updated to 18.0.33, the authentication failures started happening again which caused fail2ban to block my clients. It looks like the settings in dovecot.conf takes precedence over anything in conf.d thus overwriting the settings after an update.

    0
    Comment actions Permalink
  • Avatar
    Peter Debik

    Brandon Yap I was concerned regarding your post and tested this on our machines. In the default Dovecot configuration file I see digest-md5 included in the auth mechanism list after the update again (we did remove that previously), but that is expected (see the introductory lines of that file that warns users that this file will be overwritten on updates). I also have the 00-auth_mechs.conf in conf.d where the auth methods are re-defined. After verifying the setting I restarted Dovecot to make sure that it uses the current settings.

    Then tested the capabilities with a Telnet connection:
    > telnet <host name> 143
    returns
    * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLED IDLE LITERAL+STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=CRAM-MD5] Dovecot ready.

    0
    Comment actions Permalink
  • Avatar
    Brandon Yap

    Hi Peter, you're right, I was able to replicate what you did with telnet and digest-md5 did not show up in the list. It must be something else then because after every update I have a spate of clients getting fail2banned via the plesk-dovecot filter. Thanks for taking the time to post your findings.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request