Announcement

Collapse
No announcement yet.

IMAP/SMTP plain auth is deprecated Office 365 / Gmail now requires OAuth 2.0

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • partomas
    replied
    I figured out another unpleasant situation related to SMTP. I'm not able to send any mails form CRM on behalf of my account when I have enabled google extension for calendar, but don't have any personal e-mail account and using default System Outbound Emails settings.

    Looks like google extension also add something to SMTP credentials there as well.
    Attached Files

    Leave a comment:


  • macistda
    commented on 's reply
    Espo: OAuth is working only with Outlook extension.
    Espo: Send E-Mail from Group Mailbox via office365 smtp is working only with a O365 "full mailbox", not a O365 sharedMailbox. IMAP works with both O365 sharedMailbox and "full mailbox".

  • partomas
    commented on 's reply
    There are only one way - Please Use Outlook extension.

  • shootify
    replied
    hi, is there any update or solution for this, my office 365 imap stopped working... please help. thanks

    Leave a comment:


  • partomas
    commented on 's reply
    The same problem was detected in versions Espo v.7.1.3 (our current CRM) and v.7.2.4 (freshly installed CRM for tests). Outlook Integration v.1.2.8.

    1. When Outlook extension is "connected" SMTP use $username = $inboundEmail->get('emailAddress'); instead of "SMTP username" In this case there are no matter what SMTP username parameters are set, the system are looking at the main "Email Address" which is not always are the same as login credentials as you can see in captured video https://youtu.be/1U0bm3pH0JQ of the case.

    2. issue come when in personal/group email account we "connect" to outlook 365 by Outlook extension, then we are not able to send emails by using other setted SMTP settings like "localhost:25 no authentication", because outlook extension add additional authentication parameters on top of current settings because of: $client = $this->getExternalAccountClientManager()->create('Outlook', $id);
    example: {"name":"vmi464757.contaboserver.net","host":"loca lhost","port":25,"connectionConfig":{"authString": "dXNlcj1vbGQtc3VwcG9...UpHN5bUR6NU1nAQE="},"connec tionClass":"\Espo\Modules\Outlook\Core\Outlook\Smt p\Auth\Xoauth"} - instead of simple mail sending SMTP to localhost:25 without any authentication.

    The same behaviour is with Google extension as well.

  • lazovic
    commented on 's reply
    Hi partomas,

    In order to be able to reproduce this issue, please tell me what type of Outlook email account do you use? It is a business account or personal account? Do you use domain outlook.com or some custom one? What SMTP settings are you using (host, port, security)?

    Also, please tell me what version of EspoCRM and Outlook Integration extension are you using?

    I will be glad to help you with this problem as soon as possible.
    Last edited by lazovic; 10-07-2022, 09:31 AM.

  • partomas
    replied
    October 2022 is there and we starting getting errors like 5.7.3 Authentication unsuccessful for O365. Does anyone have ideas what to do as SMTP is not working even with Outlook plugin.

    Leave a comment:


  • bandtank
    commented on 's reply
    I have not had any issues with the Outlook extension. My emails are always sent as HTML.

  • macistda
    commented on 's reply
    I will activate and see if this problem will come back again from users.

  • yuri
    commented on 's reply
    What bugs Outlook Integration has?

    > even not possible to send a html E-Mail looking

    What does this mean? Outlook Integration has nothing to do with how email is looking. It just sends additional authentication data when connecting to SMTP/IMAP.
    Last edited by yuri; 07-07-2022, 10:53 AM.

  • macistda
    replied
    Update:
    I figured out how it works:

    https://docs.espocrm.com/extensions/...gration/email/

    If "old" E-Mail account exists, it should be deleted first, then create a new one. I am not sure if "empty" password is possible to be set.

    Looks like that works for E-Mail sending / recieving, I have to proove if sended E-Mail looks "very well" instead of "not well" on different recieving clients.
    But for "normal" IMAP Feature of Espo in future (for O365 usage) will not work from October 2022 on anymore without purchasing Outlook Plugin, that should be sure (for Business O365 Accounts).

    Earlier:
    Russ , lazovic
    Hi, I think that you are wrong (lazovic). Microsoft will drop Basic Auth at October 2022 for SMTP / IMAP and further, like they call it "unsafe" protocols.
    Your Workarount will not work for Business Accounts, maybe for private accounts, I don't know.
    You can only delay if Microsoft turns off SMTP / IMAP before October 2022. (Happened to us, and some IMAP Accounts where able to login, some where not)

    After October 2022 this features get useless at EspoCRM if you don't want to use the O365 Plugin.

    yuri , shalmaxb
    Sorry, but O365 Plugin has several disadvantages and missing features (We bought but we do not use, Update: only for E-Mail).
    We have programmed our own Scripts (Phython, exchangelib I think, triggered by PHP and via Webhook Queues) nearly completely outside of Espo and use API User for that.

    The script compares all objects (for meetings eg. max. 180 days in the past and all future meetings) with each other and creates, deletes or updates the changed data accordingly.

    The synchronization of contacts (Group Folder and Sub-Folder of every user's account - Sub-Folder of Outlook-Contact-Folder because of Apple iOS Bug) and appointments is one-way. This means that changed data in Outlook will be overwritten. For the tasks, the status will also be changed to Espo if it has changed to Exchange. All other task fields are overwritten. Objects created manually in Outlook (e.g. appointments) are ignored and not changed or deleted.

    We create objects for single Users and a Group Calendar for round about 25 employees. It was impossible to reach the goals with Espo O365 Plugin.
    Furthermore a cuple of other systems fetch this Data and store in their own Databases. (e.g. VOIP)

    For Espo we use much E-Mail automated Imports via IMAP4 for Cases, Meetings, Accounts, Contacts, Offers and on an on.

    All those things won't be functional from October on. Sinking efficiency by Espo round about 40 percent i guess.
    I think much Espo Users / Companies use IMAP instead of O365 Plugin because of Bugs and missing features. (e.g. even not possible to send a html E-Mail looking "normal" - on the opposide but with IMAP looking very well)

    Leave a comment:


  • lazovic
    replied
    Hi Russ,

    I can say with confidence that IMAP and SMTP for Outlook 365 works the same as before.
    For the first time I set up Outlook 365 six months ago (approximately) with the current email for EspoCRM, and now in the latest version of EspoCRM I entered the same login and password that were used earlier, then I used outlook.office365.com for IMAP, and smtp.office365com for SMTP. All test connections were successful and test emails were sent.

    As for IMAP and SMTP for Google, you just need to enable 2-Step-Verification (https://support.google.com/accounts/answer/185839) and create an App Password (https://support.google.com/accounts/answer/185833). This App Password will need to be used in EspoCRM for Outbound Emails, IMAP and SMTP in place of your normal, initially set password.

    Leave a comment:


  • yuri
    replied
    Anybody tried App Passwords for Gmail? Do they work with Espo?

    Leave a comment:


  • yuri
    replied
    Google Integration and Outlook Integration both support OAuth login for emails (for a couple of years already). Not sure about implementing unified solution into Espo open source in the future. It doesn't depend only on me.

    Leave a comment:


  • Russ
    replied
    Thanks for your kind replies,

    >Would this workaround help (Microsoft)?
    https://support.microsoft.com/en-us/...a-a6f2979a7944

    I tried, nope, the will drop non oAuth 2.0 support for IMAP connections


    >It is explained for Googlemail here: https://www.youtube.com/watch?v=WN9l5VWjUTw

    Hope this will work, thanks

    Leave a comment:

Working...
X