Dave van den Berg

My feedback

  1. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello,

    Thank you for sharing your idea with us, to have a breakdown of the Junk email report. Is the Junk breakdown report what you are looking for?

    Junk Email Breakdown—This report displays the total of all junk email, categorized by type, for the selected Domain during the Date Range specified in the report. Junk email is categorized into six types: Spam, Virus, Spoofing, Abuse, Incomplete, and User. The Incomplete category is for all sessions where a timeout occurs or the client closes the socket or issues a quit command before sending the data. SMTP probes fall under this category. The User category is for Blacklists, Content Filter Rules, Attachment Filtering, and custom Sieve Scripts. The remaining categories refer to their corresponding Security sections. The table below the graph contains columns for each type, and each row corresponds to the Summary time period by which the report is delineated (hours,…

    Dave van den Berg shared this idea  · 
  2. 10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Dave van den Berg supported this idea  · 
  3. 12 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello Charl,

    Thank you for sharing your idea with us to implement per user location screening. There are some challenges to implementing this as it will require that we allow authentication to begin before a connection can be blocked by location screening. Some users will not like this, so we have to find a way to block connections as efficiently as possible.

    There are a couple of options available for by-passing location screening on a per user basis. You can enable options for ActiveSync so that known devices by-pass location screening checks. You can also have the IP address of knwon ActiveSync devices whitelisted, so if you have a laptop on the same wifi network that is not using ActiveSync it will be allowed to connect as well. If you are using Webmail, you can use Two Factor Authentication to bypass Location Screening.

    We will look into per user location…

    Dave van den Berg supported this idea  · 
    An error occurred while saving the comment
    Dave van den Berg commented  · 

    Is it possible to adjust location screening per domain? I think you don't have to authenticate when you see that a domain can't be reached. In this case, when having many users, you can put users in an domain when they travel. The other domains can keep the location screening only for their countries.

  4. 3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    Dave van den Berg shared this idea  · 
  5. 9 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Hello,

    Thank you for your suggestion to include client information. Can you provide additional details about what you would like to see added to the log? Which name would you like to see added to the log? Is this for a specific protocol or all protocols? Which log would you like the information added to?

    Thanks,
    Arron

    Dave van den Berg supported this idea  · 
    Dave van den Berg shared this idea  · 

Feedback and Knowledge Base