Adding an Exclusion for SmarterMail in SentinelOne

When using Sentinel One (S1) antivirus/behavioral monitoring systems you may notice it flag the SmarterMail installer as it includes our move to .NET 10. These new .NET packages are recent enough that S1 will flag the installer for review. If this happens, you can utilize the Incidents page in S1 to add an exclusion for the installer and the components it installs.

Once you’ve located the blocked incident, click on the blocked application itself on the list (SmarterMail installer) to open the threat details view. Here you can click the Actions menu at the top right corner and select Add to Exclusions to exclude the installer from further scanning:

In the above screenshot, we already have the necessary exclusions added and so our SHA signatures are shown in red. New exclusions will not display in red unless you’ve already added tthem and are just awaiting agent synchronization of the new rule.

SmarterTools has reached out to SentinelOne and we are working with them on remedying this situation. However, this may take some time. For now, the exclusions will resolve this issue.

Article ID: 3763, Created: Yesterday at 1:13 PM, Modified: Yesterday at 1:15 PM

Adding an Exclusion for SmarterMail in SentinelOne

Was this article helpful?