M.K.

IP addresses found on "Ignored IP List" will be skipped during classification, the rest of the email will be still checked. When IP is whitelisted, the whole email is automatically considered as ham.

Hi, ESET Mail Security for Exchange uses '451 4.7.1 Please try again later' response for greylisted messages, but Greylisting is turned off by default. Have you checked in-product logs or transaction logs to verify whether messages were rejected by Mail Security?

Hi, just Windows Server 2008 (NT 6.0). MK

Hi, try using Get-TransportPipeline command, that will give you better information about the order in which the agents are actually called. Get-TransportAgent shows an overall priority, it is applied separately for every event that Exchange processes during email transport.

Hi, your customer can use additional rules with conditions: SMTP Sender's domain, Sender's IP address, From header - address, to check if emails with From: "supplier-mail-address" have also corresponding IP address range or SMTP Sender. Note: we plan to add the Sender Spoofing Protection feature to the upcoming vNext version of EMSX, to help to automate tasks like these.

You need to use one of the IP & Domain-to-IP whitelists, for example Greylisting and SPF -> IP whitelist Greylisting and SPF -> Domain to IP whitelist

Hi, have you tried using custom rules with the combinations of conditions From header - address From header - display name? You can also have all macro-enabled office documents quarantined, using the Attachment type condition.

Hi, also please note that ESET Mail Security for Exchange can also be used to scan Exchange Online mailboxes with on-demand scan in case of hybrid deployments (on-premise + cloud). Mail transport in hybrid deployments is scanned only if emails are routed first to on-premise server and then to cloud. Matej

Hi Brent, currently this is not possible to do, other than to have the archives password protected and thus bypassing the attachment filtering rules. Matej

Hi Joe, yes, Exchange can move spam to recipients' Junk folder based on the SCL score, so setting up a rule to insert the SCL header should be enough. Best regards, Matej

Hi, yes, by default Mail Transport protection adds X-Eset... headers to all scanned emails, unless it's turned off in settings. So if headers are missing, it's better to check why (settings, logs, topology, ...). Best regards, Matej

Hi, RBL servers are queried with IP addresses extracted from message headers, DNSBL server are queried with domains and IP addresses extracted from the message body. So the answer depends on the type of the BL, i.e. Spamhaus could be in both, Spamcop collects only IP's so it's probably sufficient to put it only in Additional RBL servers list, etc.. Best regards, Matej

Hi, the way you can test this is to create another rule with condition that always hit on the email above, and add Action of type "Log to events" and use a variable %Recipients% in the text. That way you can verify all the addresses Mail Security sees when evaluating the rule. Best regards, Matej

Hi, just to clarify, when evaluating Recipient condition, Mail Security currently uses values of "To" and "Cc" MIME headers and all addresses passed in RCPT commands in SMTP envelope - that includes all Bcc recipients too. Note: for incoming messages the "Bcc" MIME header shouldn't be present at all - at least according to RFC (5322). But for outgoing messages it could be useful to add it to the condition evaluation - if that's the case. We can track it as a feature request. Best regards, Matej

Hi, a quick update to this older thread. With the upcoming update of the Archive support module (v1303, currently on pre-release servers) it should be now possible to remove macros from office documents in incoming emails, even in previously released Mail security products. If you define a custom rule with Attachment type condition, select "Office files/Generic OLE2 Compound Document", and choose Quarantine attachment (or Delete attachment) as an action, Office documents will be delivered without any macros. Note: you can of course combine additional conditions in the rule to target it to specific groups or types of emails. Matej

Hi Joe, typically the tool should produce the same results. Have you tried running it with parameters (/names, /details) to see which mailboxes make the difference? M.K.

Hi, I meant sender's IP address in this context - this is usually the topmost Received header. M.K.

Hi, Our GeoIP DB correctly identifies this IP as Chinese. But only the sender's address (last hop) is verified against Blocked countries list, not all intermediate servers from Received headers.

Hi Tom, in Mail Security there is an option to define a custom rule to move all emails containing macro-enabled office documents to quarantine. You need to define an Attachment type condition and mark "Microsoft Office Macro-Enabled Document (97-2003)", "Microsoft Word Macro-Enabled (2007+) (*docm, *dotm)", etc... Matej

Hi, from your description it seems that the email has been marked as a spam because of it's content ("Rule system classified mail as SPAM"), despite the fact that it came from a trusted source ("IP (209.85.208.175) isn't found on cloud black list"). Ad. "Any ideas why this software is blocking trusted email?": In order to answer this, please open a ticket with our support and provide them with sample(s) of mis-classified email(s). Ad. "Does this software not send a quarantine report to end users?": Yes it can, please refer here (https://help.eset.com/emsx/7.1/en-US/idh_scheduler_task_qreports.html). Matej

Hi Tom, in general multiple transport agents can act on an email independently, in order based on their priority (see cmdlet Get-TransportAgent, or https://help.eset.com/emsx/7.1/en-US/idh_agent_priority2.html). Ad "Is it possible to setup that spam mails will be delivered in the Junk Mail folder again": Yes, for example set the action to take on spam to "No action" and configure a rule to set the SCL header (https://help.eset.com/emsx/7.1/en-US/idh_wizard_rule_action.html). By default Exchange will then move all emails with SCL above threshold to Junk folder (https://docs.microsoft.com/en-us/exchange/antispam-and-antimalware/antispam-protection/configure-antispam-settings?view=exchserver-2019). Matej

Hi Tom, "we see an 'X-ESET-Antispam: OK' tag, which menas to me, that ESET didn't apply any anti spam action": you are right, based on this ESET Mail Security is not responsible for placing the email to the Junk folder. It could be Oulook's state-of-art antispam, or one of the Exchange server's default antispam agents. Check the X-MS-Exchange-Organization-SCL header. The format of X-ESET-AS header is not public, it's used for diagnostic purposes. Matej