Feedback by UserVoice

Craig Brown

My feedback

  1. 834 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    51 comments  ·  Microsoft 365 Groups  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Craig Brown commented  · 

    This is a much requested feature in my org as well. We used to use Lotus Notes Team Rooms, which had more granular permissions. We like the use of groups for simplicity, however the users want more control over the data as not everything should be editable.

    Craig Brown supported this idea  · 
  2. 265 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Craig Brown supported this idea  · 
    An error occurred while saving the comment
    Craig Brown commented  · 

    I'm not the original poster, but came here to see if someone submitted this request, and vote for it, as I have yet another problem with the spam filter today.

    All of our mailboxes are in the cloud, however we have an on-premise mail gateway that all messages pass through for spam filtering, etc both incoming, and outgoing. Messages from my local public library are being marked as spam by EOP, so I white-listed the domain in the Exchange Online spam filter settings. However, EOP is still marking this message as spam (with a score of 5, and also marking them as bulk, even though I have that turned off as well.

    I placed a call with support, and they advised me to create a transport rule, to set the spam score for this domain to -1. What is the purpose of the domain whitelist, if I need to create a transport rule anyway?

    I would much rather have the option of bypassing the spam filter completely for all messages, as our on-premise spam filter does the job just fine, and 365 is providing us with a lot of false-positives. The link you provide really doesn't explain how to disable EOP completely. I'm using scenario 3 - mail routed to on premises, with MX record pointing on premises. We do not want to have the MX point to Office 365 at all, which is what scenario 3 recommends, even though that's not what we want at all.

    I suppose my only option is to create a transport rule that applies to all messages, and set the spam score to -1?

Feedback and Knowledge Base