Greetings!

 

Have noticed that field BlindCopyRecipient in Activity is not being populated when receving an email, that was send using bcc field and specifying an email address that is configured for synchronization.  However email is synchronized and showing correctly in communication panel. Is it a bug or feature?

 

Like 1

Like

1 comments
Best reply

Hello, 

Such behavior is indeed reproduced when the recipients of the email are in the BCC field. If the "To" and "CC" fields are empty, and the recipients are in BCC, this behavior is expected. 

Logic behind how the BCC field works:
The BCC field in the letter is seen only by the sender, and only in the sent email folder. This behavior is based on the message data transfer logic at the email server level; the recipient in the blind copy does not have access to view the list in the BCC field. None of the recipients will see the blind copy (even if you send it to yourself). Therefore, the BCC field in Creatio will be filled in only in two cases: - the letter was sent from our system, and while sending, you need to specify the recipients in this field. - the letter was synchronized from the sent letters folder. In other cases, the BCC field in Creatio will be empty. Since for these emails, recipients were not specified in the "To" and "CC" fields, only in BCC, which according to the logic of the field's operation, we do not see, there is a situation where the email is synchronized, but there are no recipients. Please note that Creatio cannot influence this behavior in any way, as we only synchronize the email from the mail server with the same parameters as the parameters of this email. Since the "To", "CC", "BCC" fields are empty in Outlook itself, they will also be empty in Creatio. 

Best regards,
Ivan

Hello, 

Such behavior is indeed reproduced when the recipients of the email are in the BCC field. If the "To" and "CC" fields are empty, and the recipients are in BCC, this behavior is expected. 

Logic behind how the BCC field works:
The BCC field in the letter is seen only by the sender, and only in the sent email folder. This behavior is based on the message data transfer logic at the email server level; the recipient in the blind copy does not have access to view the list in the BCC field. None of the recipients will see the blind copy (even if you send it to yourself). Therefore, the BCC field in Creatio will be filled in only in two cases: - the letter was sent from our system, and while sending, you need to specify the recipients in this field. - the letter was synchronized from the sent letters folder. In other cases, the BCC field in Creatio will be empty. Since for these emails, recipients were not specified in the "To" and "CC" fields, only in BCC, which according to the logic of the field's operation, we do not see, there is a situation where the email is synchronized, but there are no recipients. Please note that Creatio cannot influence this behavior in any way, as we only synchronize the email from the mail server with the same parameters as the parameters of this email. Since the "To", "CC", "BCC" fields are empty in Outlook itself, they will also be empty in Creatio. 

Best regards,
Ivan

Show all comments

We have active directory which locks user account after 5 login attempts.

After user change password and his exchange account was added in crm, email listener try to consume mails and 5 times fail it because password in crm is not changed yet (user need to remove his account from crm before changing password).

Our listener is deployed in docker. How we can configure attempts to consume emails < 5 times?

Like 2

Like

2 comments
Best reply

Hi,

 

The values for 'attempts to consume emails' are in the SyncErrorHandler table under the RetryCount column. For example, you can reduce it to 3 times. This would be the most optimal value.

Also, please note that a RetryCount value that is too large or too small can lead to undesirable consequences regarding interaction with your mail server (for example, the mailbox will be disabled upon any negative response from the server). Therefore, we recommend changing this cautiously.

Hi,

 

The values for 'attempts to consume emails' are in the SyncErrorHandler table under the RetryCount column. For example, you can reduce it to 3 times. This would be the most optimal value.

Also, please note that a RetryCount value that is too large or too small can lead to undesirable consequences regarding interaction with your mail server (for example, the mailbox will be disabled upon any negative response from the server). Therefore, we recommend changing this cautiously.

Sergii Zhmurko,

mb you know concrete row what is responsible for my question in this table? We use exchange basic auth

Show all comments

I have locally installed the creatio environment + downloaded the zip archive and setup the email service

 

Install and run Email Listener:

  1. Open the directory to deploy Email Listener on the server dedicated for the service.
  2. Download and unpack the archive that contains the setup files to the directory. Download the archive.
  3. Open the / Creatio Email Listener component directory and run the following command:

docker-compose up -d

 

Executed the above command. I was able to add the email account + other configuration but when I run the diagnostics,  I do face the error as attached, how to resolve it?

 

I tried checking the Email Listener log 

 

2023-12-14 19:18:46,098 [105] WARN NT AUTHORITY\SYSTEM Warn - mailbox account@gmail.com synchronization settings not valid

 

I also do not see any email listed in the notification icon -> Mail.

 

Creatio is able to successfully send Creatio test message email from the diagnostic page.

 

 

2023-12-14 19:13:46,080 [106] DEBUG NT AUTHORITY\SYSTEM DebugFormat - ListenerServiceFailHandler started

2023-12-14 19:13:46,080 [106] DEBUG NT AUTHORITY\SYSTEM DebugFormat - ExchangeListenerManager created

2023-12-14 19:13:46,097 [106] WARN NT AUTHORITY\SYSTEM Warn - mailbox account@gmail.com synchronization settings not valid

2023-12-14 19:13:46,097 [106] DEBUG NT AUTHORITY\SYSTEM DebugFormat - Events subscription for 882c1561-***-****-****-******** mailbox created

2023-12-14 19:13:46,097 [106] DEBUG NT AUTHORITY\SYSTEM DebugFormat - Failover synchronization of account@gmail.com started

2023-12-14 19:13:46,097 [106] WARN NT AUTHORITY\SYSTEM Warn - mailbox account@gmail.com synchronization settings not valid

2023-12-14 19:13:46,097 [106] DEBUG NT AUTHORITY\SYSTEM DebugFormat - Failover synchronization of account@gmail.com initialization ended

2023-12-14 19:13:46,097 [106] DEBUG NT AUTHORITY\SYSTEM DebugFormat - Email synchronization process for 882c1561-***-****-****-******** mailbox created

2023-12-14 19:13:46,097 [106] DEBUG NT AUTHORITY\SYSTEM DebugFormat - ListenerServiceFailHandler ended

File attachments
Like 0

Like

1 comments

Hello,

 

I kindly request your attention to a post where a similar issue was discussed.



https://community.creatio.com/questions/exchange-listeners-806



 It is also crucial to ensure that the release version of the microservice is being used (Please note that to deploy a new version of the microservice, you need to contact Creatio technical support to grant you access to the repository).

 

Regarding the warning "mailbox account@gmail.com synchronization settings not valid," please check that the needed folders are chosen during folder synchronization. (in case you are syncing mails from the folders)



Try stopping the mailbox synchronization in the mailbox settings and restart it by reconfiguring the synchronization parameters.

 

Such issues may arise due to the specifics of deploying the local environment and may depend on other factors.

 

The best way to ensure that everything is configured correctly is to send an email from the system.

If emails are sent and synchronized successfully, you can ignore the error as it is not related to the email sending functionality.

 

Best regards,

Pavlo!

Show all comments

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



For KUBERNETES:

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:

https://academy.creatio.com/docs/7-18/user/on_site_deployment/containerized_components/exchange_listener/email_listener_synchronization_service



For Docker:



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



docker rm - f



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

Like

Share

1 comments

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 1.xxx 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

Hi,



Could you elaborate on the basic authentication deprecation mentioned in the 8.0.3 release notes https://academy.creatio.com/docs/release/release-notes/803-atlas-releas… ? 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 ?



Thanks,



Damien

 

Like 1

Like

3 comments

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:

https://customerfx.com/article/setting-up-microsoft-office-365-email-fo…

 

Best regards,

Kate 

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 ?



Regards,



Damien



P.S. Noticed the deprecation will be sooner than later (Oct 1st 2022 - https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online)

 

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,

Kate 

Show all comments