Jump to content

filips

ESET Staff
  • Posts

    160
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by filips

  1. Hi,

    you can use Ignored lists to exclude some (irrelevant) information from classification.

    This is useful in more cases, e.g.:

    • False positive - If you receive email from some provider that got to cloud blacklist, all email from this provider will be marked as spam. You can add IP/domain to ignored list to ignore this piece of information but still evaluate antispam.
    • Exclude IP addresses of servers that are part of your infrastructure. IP address of your server may become whitelisted causing all mail coming from this server marked as ham.

    * we will fix the KB article

  2. We don't have any feature to notify users when using quarantine mailbox.

    Each quarantine type has some pros and cons - you must decide which one suits you best, e.g.

    Local quarantine gives us more control so it has some nice features like:
    - users can manage their spam using:
        - mail reports
        - web interface
    - spam emails do not enter Exchange infrastructure

    Disadvantage is that if you have more transport servers then you will have more quarantines to manage

    more info here http://help.eset.com/emsx/6.5/en-US/index.html?idh_config_mailserver_quarantine.htm

  3. Hi,

    unfortunately, we don't support content filtering by message body (yet)

    maybe you could use "Blocked Body Domain list" to mark messages that contain some domains in body as spam? (http://help.eset.com/emsx/6.5/en-US/?idh_config_mailserver_as.htm)

    you can specify a particular domain - e.g. spamdomain.com or a top level domain - e.g. .com

     

  4. Hi,

    there seems to be a problem with SPF macro expansion - should be fixed in next EMSX release.

    When you mentioned other "legitimate" sender, do you mean other domains? Can you give us other domain-IP pairs that are not evaluated correctly?

    We can examine them and check whether they are related to the problem with humblebundle.com or not

  5. Users can manage their spam emails - both release and delete are allowed on spam emails.

    The type column in screenshot you posted says "rule" - it was not quarantined by antispam but by rules. Email can be quarantined by AV protection, AS protection or by rules - the release action depends on this.

    actions.png

    I filed an improvement to give administrator control over this behavior to be able to:
    1. Create a rule that forbids certain content (e.g. file type policy) - user cannot release such emails
    2. Create a rule that defers certain content (e.g. suspected spam) - user can release such emails

     

  6. Hi,

    As i wrote above, this is not supported. Regular user cannot release emails quarantined by a content rule - only admin can.

    If you quarantined some emails with a rule and want to release them, you have 2 options:
    1. log in to the web interface as administrator and release them
    2. go to machine where EMSX is installed and release them using GUI

    If you want to allow regular users to release emails quarantined by content rule please submit a market requirement.

  7. Each user has access to his quarantined emails, but may not be able to do all operations. This is for security reasons.

    e.g. If admin creates a rule that prohibits .exe files it would be too easy for the user to just release emails with .exe files. Now he has to request the files from admin.

    If you have a specific content rule and want to allow users to release emails quarantined by this rule - this is currently not possible.

    Could you give us an example/use case of what you are trying to achieve?

     

    thanks

×
×
  • Create New...