In this article, you can find algorithms of Email Listener updating microservice in different deployment methods.

Run the following command
helm upgrade -i #specify parameters the same as during installation.
You can find the installation sample in the deployment instructions.
The current version of the helm package is available in the article:

For Docker:

Delete a running container with an out-of-date version of Exchange Listener.

docker rm - f <container_name>

After that, download new files of the Email Listener microservice to the directory and run the command with installation instructions

docker-compose up -d
The latest version of Exchange Listener can be found in the Docker Hub community here.

Like 2




Thank you for the guide, but could you please link to the latest email listener service ?


In the academy documentation , for Kubernetes or docker, both point to version 0.8.74 whilst the latest versions are on for a couple months already apparently....

Please update your on-premise documentation, these critical service files links are outdated for more than 1/2 year.....


P.S: Shouldn't any posting to the latest academy page reference be in 8-0 and not 7-18 link by now?

Show all comments


Could you elaborate on the basic authentication deprecation mentioned in the 8.0.3 release notes… ? When is it occurring?

Do clients on-premise are currently still on 7.18.5  until 8.1 is released ( waiting code being stabilized with new features and fixes), do we need to update their system in 8.0.3 or does the email listener integration with 7.18.5 work ok ?



Like 1



Hello, Damien!


As for now, the integration works successfully on all versions with Basic Authentication, and it does not depend on where the site is (cloud or on-premise). 
But as we have written in the release notes 8.0.3 Microsoft is deprecating the login and password authentication (Basic Authentication) method since it is obsolete and insecure. We recommend setting up secure OAuth authentication in the near future so that you do not lose access to your mailboxes from Creatio. 
Also, you can change the method of authentication both on version 7.18.5 and on 8.0.1, it will work.


You can use this article for setting up Microsoft Office 365 Email for using it with Creatio via OAuth:…


Best regards,

Kate Karpik,

Thanks for the clarification :)

Regarding shared mailboxes using Oauth - can it be done also in 7.18.5 or do we need to upgrade to 8.0.3 minimum ?



P.S. Noticed the deprecation will be sooner than later (Oct 1st 2022 -

Dear Damien,


Thank you for your feedback.

Unfortunately, in order to add shared mailboxes that use OAuth authentication to Creatio you need a minimum version of 8.0.3


Best regards,

Show all comments