check before: 2020-11-20
Updated December 16, 2020: We have updated the rollout timeline for this release and add additional details for clarity. Thank you for your patience. We're making some changes to how tenant (Anti-spam/Hosted Content Filter policy) and user (Safe sender) allows work when it comes to high confidence phish. A message is marked with the high confidence phish verdict when we detonate it and know that it is malicious. We want to ensure that our customers are protected and therefore block those messages from getting to the inboxes of end-users. This is normally the case, but tenant and user overrides can stop this from happening. We have decided to no longer honor Allowed senders or domains when the messages are considered as high confidence phish. Note: Secure by default will not impact your antispam policy high confidence phish action settings but actually enforce it by ignoring the above stated overrides when we know it is high confidence phish. In other words, high confidence phish will still go to where you configure it to go, whether it is sending it to quarantine (recommended) or to the Junk Email folder.
an advanced plan is required to see all details
A cloudsocut.one plan is required to see all the changed details. If you are already a customer, choose login.
If you are new to cloudscout.one please choose for a plan.