WG-Goe 0 Posted May 28, 2023 Posted May 28, 2023 I run Exchange Server 2019 internally and have been using eset Mail Security for 2 weeks. we have shared mailboxes and distributed group mailboxes that are flooded with spam and esmx doesn't seem to check these mailboxes. I've created transport rules in esmx to filter specific characters, but it seems to only work with real person mailboxes
Administrators Marcos 5,455 Posted May 29, 2023 Administrators Posted May 29, 2023 Please check if you have this setting enabled: https://help.eset.com/emsx/10.0/en-US/idh_config_av_agent2.html Of note is: Internal messages from Outlook inside the organization are sent in TNEF format (Transport Neutral Encapsulation Format). Antispam does not support TNEF. Therefore, internal TNEF formatted emails will not be scanned for spam regardless of Scan also messages received from authenticated or internal connections by setting. Also refer to the Antispam section of the KB https://support.eset.com/en/kb332 and make sure that ESET can communicate with the listed ESET servers and: Make sure to open TCP/UDP port 53535 for the addresses in the table below. Otherwise, the performance and catch rate of antispam will be limited. I'd recommend raising a support ticket should the problem persist. We'll need you to enable diagnostic logging when receiving a test message and logs collected with ESET Log Collector as well as the test message itself.
WG-Goe 0 Posted May 30, 2023 Author Posted May 30, 2023 Thanks for your fast reply. The shown setting is enabled and Ports are open. I will open a support ticket containing the logs.
Recommended Posts