Will result in false display of Exchange plugin status in the hub. Also will result in disableing the plugin on the Exchange, although activated in the policy…
Update: I can confirm, that the issue still exists in the form that the plugin is disabled on per device view within the hub. This also seems to reflect on the GUI directly on the client.
Yet I also can confirm that detections from the plugin where made…
Resolved an issue with settings in the Exchange Shield component. Previously, settings for Exchange Shield were not being properly reflected on the client.
Wildcards are now accepted for the Exchange Shield file name mask for attachment blocking. Previously, wildcards were rejected.
This problem still occurs!
Maybe it got fixed for some time but we see mails getting to the mail shield of clients… mails that would have been intercepted normaly by Exchange plugin…
I did some testing with 2 customer exchange installations: Just activated the plug-in manually from the Avast GUI… On the first server it was disabled a few minutes later… after the second try it stays active.
On the second server after activating it it still is active…
get-transportagent on management shell will show, that the plug-in is running… Which is wierd since I only have one customers out of 12 that has proved Exchange plugin detections of malicous mails…
Is the plugin still active for you at this time? As far as I am aware, we haven’t had any recent reports to the support team of new issues with the Exchange plugin. Thank you
please refer to the case 16002482. I just resent my mail that I sent on november 6th. But the mail was smime signed… There is some issue when I sent mails signed for certain customers/partners… so my mail from november the 6th was probably not seen by the support team…
I have put all the relevant information in the mail.