Group imap account not receiving emails with Outlook Integration

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Lukas Klepper
    Junior Member
    • Oct 2022
    • 7

    #1

    Group imap account not receiving emails with Outlook Integration

    Hi, Our group imap account stopped receiving emails spontanusley in mid of july. Before everything worked just fine.

    If I check the IMAP connection it fails saying Error 500: cannot login, user or password wrong, even though I can guarantee its correct. The same credentials are put into SMTP, sending the test email here works.

    When I try to connect (reconnect) the outlook extension, login with the required user and accept the app permissions I get Error 500 - Could not get access token for Outlook.

    Nothing was changed on the app permissions side or the email account. Only thing which was changed since three running years is the rotation of the client secret.

    We are on the latest espocrm version with the latest outlook extension.

    I already tried restarting, made sure the permissions are set, removed the email setup and readded it again.

    Has anyone else encountered this issue, or does anyone have suggestions on what else I can check or try?
  • heint
    Junior Member
    • Jun 2025
    • 21

    #2
    Greetings, Lukas Klepper,

    To investigate this issue further, please follow these steps:

    - Enable Debug mode: https://docs.espocrm.com/administrat...ng/#debug-mode.
    - Reproduce the error.
    - Provide the EspoCRM error log. EspoCRM log files are located in {ESPO_ROOT}/data/logs/ directory. Most errors are logged there.

    The log file can be zipped and attached in reply.

    Comment

    • Lukas Klepper
      Junior Member
      • Oct 2022
      • 7

      #3
      Hi, heint,

      thanks for the hint with the debug mode. I was able to see that the getAccessTokenFromAuthorizationCode method is throwing an invalid client error because there was a mismatch in the redirect uri config.

      Even though the redirect uri was correct the system seemed to expect a wrong one because there was a tailing slash in the site url config. I dont know why it worked beforehand (maybe because it was an older version of espocrm?`) but removing the slash fixed it.

      Also I think this message should be logged as an error, not as debug as it indicates as a error.

      Comment

      Working...