Trying to test out the outlook integration extension... not working so far.

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • rabii
    replied
    Originally posted by rudepeople
    What it says on the tin. After IMAP has been disabled in o365, my company is kind of scrambling to get something back up and working to capture emails. The solution SEEMS to be the outlook integration, but I cant get it to work.

    We don't want to just buy the integration if it's not going to work so I requested a demo and am trying to get it set up in the dev environment provided my espo. I have followed the instructions (here) Created the app registration and key in azure, updated the integration in espo(dev), and created a new personal email... this is what I get:

    Code:
    Error 500
    Outlook Oauth: Error after requesting GET [URL]https://outlook.office365.com/api/v2.0/me/[/URL]; Reason: Access is denied. Check credentials and try again.. Code: 403.


    Has anyone gotten this working? or is this error just because I'm in the dev/demo environment?

    I should note, when I created the personal email account in espo and saved, it DID give me the outlook box with the connect option. clicking through that enduced the expected popup with login.microsoftonline.com and I was able to successfully log in. THAT'S when I got the error.
    means you are just missing some configuration, i had same problem still have not fixed it all but for IMAP it is working make sure to use SSL not TLS and it should work.

    Leave a comment:


  • rudepeople
    replied
    Emilvb I have put together a little work around but it's not pretty. I built an iredmail mta in our colo (hyperv) and configured it with mail boxes for each of our sales team members. then I set transport rules in exchange to forward all mail to the mta. I had to set up 2 rules per user, one for inbound and one for outbound.

    The biggest gotcha is dovecot has to be configured with insecure connections. NOT wise under any other circumstance, but once again espocrm falls short in that it doesn't support starttls.

    Common espocrm devs, I understand you're dealing with a war and all (and I genuinely hope you're safe), but you've had 2 years (at minimum) to get these things working.

    Something to consider, I have not yet figgured out how to clear the emails from the mail boxes on the MTA. Cant just delete on recv'd because espo needs time to log. Cant seem to find a scheduler to shuttle everything to trash based on age. It's low priority right now so I haven't spent a lot of time on it.
    Last edited by rudepeople; 10-27-2022, 06:21 PM. Reason: noting caveats

    Leave a comment:


  • Emilvb
    replied
    Same issue on my side.
    Running latest version of Espo (7.2.6) and the latest Outlook integration (1.2.9).

    Cant get it running on Personal nor Shared mailbox.

    Leave a comment:


  • Trying to test out the outlook integration extension... not working so far.

    What it says on the tin. After IMAP has been disabled in o365, my company is kind of scrambling to get something back up and working to capture emails. The solution SEEMS to be the outlook integration, but I cant get it to work.

    We don't want to just buy the integration if it's not going to work so I requested a demo and am trying to get it set up in the dev environment provided my espo. I have followed the instructions (here) Created the app registration and key in azure, updated the integration in espo(dev), and created a new personal email... this is what I get:

    Code:
    Error 500
    Outlook Oauth: Error after requesting GET [URL]https://outlook.office365.com/api/v2.0/me/[/URL]; Reason: Access is denied. Check credentials and try again.. Code: 403.


    Has anyone gotten this working? or is this error just because I'm in the dev/demo environment?

    I should note, when I created the personal email account in espo and saved, it DID give me the outlook box with the connect option. clicking through that enduced the expected popup with login.microsoftonline.com and I was able to successfully log in. THAT'S when I got the error.
    Last edited by rudepeople; 10-26-2022, 03:08 PM. Reason: adding details
Working...