Jump to content

filips

ESET Staff
  • Posts

    154
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by filips

  1. I updated the answer - there was a problem with encoding of some characters...
  2. Hi Guillaume, [apart from using EDTD] to disable the rule for certain users, you can update the default rule with new condition. You could add "Sender is not one of {list of whitelisted senders}" or "Sender's IP address is not one of {list of whitelisted IPs}" etc. This shouldn't happen, but we need some diagnostic data to examine the issue - you could contact customer care for further assistance.
  3. Hi Richard, EMSX v7 has a "From header - display name" condition in transport rules so you can create a rule like this: Conditions: From header - display name contains one of {My User1, My User2..} Sender's IP address is not {list of my IPs} (or Internal message is false) Actions: log/reject/delete/quarantine
  4. Hi davidenco, The error in logs is caused by an exception while parsing "Received:" headers. We will address the issue in next hotfix of EMSX. Could you PM me a procdump file(s) capturing the exception? It would help us to track it down: procdump -ma -e 1 -f "nullreferenceexception" edgetransport.exe
  5. Hi, it looks like the mail server had limited connectivity to ESET antispam cloud services (already discussed here).
  6. Hi, unfortunately, this is not supported. Quarantine web access rights support only administration of whole quarantine and delegated access to one mailbox. Though you can assign the access rights to user group as well, you would still have to create one access right record for each mailing list. I filed an improvement to add delegation to domain/multiple mailboxes (e.g. wildcard support).
  7. Hi Russ, SPF uses only IP whitelists (or domain to IP). Approved senders list is not used in SPF, it applies only to antispam. The domain to IP lists should work - you could compare resolved IP addresses in GUI with connecting IP (maybe it wasn't resolved?). The rule you created didn't work because if "Automatically reject messages if SPF fails" is enabled, SPF is evaluated right on MAIL FROM command and if it fails, message is rejected right away and no rules/antispam are evaluated. To handle SPF in rules disable setting "Automatically reject messages if SPF fails" and then create a rule. It could look like: Condition 1 - Sender's IP address is not (list of customer's IPs) Condition 2 - SPF result is Failed Action - Reject message (You should test it with "Log to events" action first to see if it works correctly) or a simple version (but this one will not protect against spoofing of their own domain) Condition 1 - Sender's domain is not mydomain.com Condition 2 - SPF result is Failed Action - Reject message
  8. Hi Dean, All available keywords are mentioned in tooltip for "Format of event messages" Attachment name keyword will be available in EMSX v7 (%ATTNAME%, %ATTSIZE%). We improved the mailserver log in v7 as well so you will see all blocked attachments in mailserver log detail.
  9. Users are read from Sharepoint and checked against AD (once every 24 hours), deleted ones should be ignored Please PM me: 1. the output of usercount command 2. some user names that are deleted/disabled and are counted 3. number of active users you have 4. how you deactivate users we will check it thanks
  10. Hi, try running this command to see which user accounts were counted: shpio13 usercount /print /withnames /diag
  11. Hi, i can confirm this is a bug - resolving of domains runs asynchronously and the IP addresses are not always transferred to transport agent. It will be fixed in EMSX v7 Thank you for reporting a problem
  12. Greylisting whitelists use IP address of sender - HELO domain is not used at all. The problem can be caused by EMSX not resolving all of hotmail.com IP addresses. What IP addresses from hotmail.com do you see in greylist log that were rejected (and should be whitelisted)?
  13. Hi Dean, wildcards are ignored - you can combine 2 conditions: Sender's domain is "aol.com" Sender contains "mobile_" or you can use regex: Sender matches regular expression "mobile.*@aol.com"
  14. Hi davidenco, "Add domain to greylisting whitelist" adds the domain to "Domain to IP whitelist". Domains in this list are resolved to IP addresses and these IP addresses are then whitelisted. Resolving may take some time - you can check advanced settings to see if the IP addresses were already resolved (and which IP addresses were found). hotmail.com, outlook.com and hotmail.co.uk share some IP addresses/ranges so if you add one of them to whitelist it may whitelist others as well. If you see an email rejected by greylisting (that should be whitelisted), you can check the IP address against "Domain to IP whitelist".
  15. Hi, this error is shown also when there is no certificate bound to the quarantine address. You should be able to fix it with new binding. Open IIS->Sites->Default web site->Bindings... and add a new https binding with port 4443 and your certificate.
  16. Hi, antispam in EMSX v6 requires different firewall settings than v4, You should check those as well: https://support.eset.com/kb332/#antispam
  17. Hi, This feature has already been discussed with some customers. The problem is that it defeats the purpose of rules - if an admin wants to block certain type of files then why give users an easy way to "smuggle" these files into your company (e.g. just put it in a DOC file)? The problem with *.tmp can be solved easily, but if we find a good use case for "Is in a container" setting we will certainly implement it.
  18. Hi jdashn, You can remove the *.tmp extension from the rule. We already removed it in newer versions because it caused this problem. You can see Office documents blocked because they are archives and some of them may contain *.tmp files (rules are evaluated on each file in archive).
  19. Hi, Blocked body domain list marks an email as spam - spam action is performed. EMSX v7 will have body content filtering rule as well - it will support different actions, logging etc.
  20. Hi, unfortunately, the message "Infected attachment has been deleted by ESET Mail Security" cannot be changed
  21. One more thing i forgot to mention: You can (should ) use rule action "Log to events" for some time to check if the rule works correctly before enabling action like reject/drop/quarantine
  22. Hi davidenco, The SPF check is evaluated using domain from HELO or MAIL FROM. It does not protect You against spoofing of "From" header. This means that if the sending domain (in HELO or MAIL FROM) does not have SPF record or has a valid SPF record, the mail is valid even if it is spoofing your domain in From header (it could be a valid mail forwarder). This problem can be solved by using DMARC: https://blogs.technet.microsoft.com/eopfieldnotes/2015/02/26/using-dmarc-to-prevent-spoofing/ You could also create a transport rule like this: Conditions: Message headers match regular expression \nFrom: .*@OurDomain.co.uk Sender's IP address is not one of (list of your IPs or IPs that are allowed to send mail for your domain) Actions: Quarantine message Or something like this: Conditions: Message headers match regular expression "\nFrom: .*@OurDomain.co.uk" Message headers do not match regular expression "\nReply-To: .*@OurDomain.co.uk" Actions: Quarantine message
  23. Hi davidenco, You are right, if an email fails the SPF check or if there is no SPF record for the sending domain, greylisting will be performed.
  24. Hi, this option is not available. Something similar will be available in EMSX v7 - it will have a customizable SMTP reject response message (apart from default "Invalid content").
×
×
  • Create New...