Jump to content

M.K.

ESET Staff
  • Posts

    26
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by M.K.

  1. You can add a condition "Sender's IP address ... is not" to the rule and list the addresses for which you want to skip the rule. Currently it is not possible to reference directly the existing IP lists defined in Advanced settings/Antispam protection/Filtering and verification. But we do track this market requirement in our backlog already and plan to add it in the future.
  2. Hi, the problematic domain you reported has been already removed from the cloud blacklist. The quickest way to solve such cases is to send the email sample to nospam_ecos@eset.com (https://support.eset.com/en/kb141-submit-a-virus-website-or-potential-false-positive-sample-to-the-eset-lab#spam) as those are handled almost immediately. Also based on the sample we have identified a problem in the algorithm that selects the sender's address from email headers in some cases (Return-path: header), and it will be also addressed by an automatic update. Regards, Matej
  3. EMSX tries to resolve as many IP addresses associated with that domain as possible - using A, MX, and SPF records. All resolved IP's could be checked in the Edit dialog in Advanced settings. If the IP is on the list (approved domain to IP list) and the email is still being marked as spam, please submit a support ticket so we can have a look at it.
  4. First question - yes, exactly. Regarding the blacklist check - if the IP is on Ignored list, then no checks are performed with the IP, including neither cloud nor local blacklists. But the email could be, for example, marked as spam due to the blacklisted domain in the message body.
  5. 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.
  6. 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?
  7. 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.
  8. 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.
  9. 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
  10. 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.
  11. 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
  12. 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
  13. 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
  14. 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
  15. 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
  16. 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
  17. 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
  18. 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
  19. 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.
  20. Hi, I meant sender's IP address in this context - this is usually the topmost Received header. M.K.
  21. 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.
  22. 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
  23. 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
  24. 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
×
×
  • Create New...