Outlook 2016’s “Unsafe Rules”

Microsoft Outlook has a robust system of rules that you can use to move, copy, delete (or alert you) when you receive an email based on a number of conditions.

One option I use quite a bit is “when I receive an email with x in the subject line, run a script”. Here’s why: I have an app that downloads files to a specific folder that cannot be changed. When the downloads are complete, I want to move those file(s) to a shared network folder. So I have Outlook set up to where if I send an email to myself with a certain string of letters and numbers, a script runs that moves the file(s) from one folder to the other (I often want to do this while away from the computer, hence the need for the Outlook rule and script).

However, it would appear that December’s updates for Office 365 removed the “run a script” option from the rules, along with a couple other “unsafe rules”. Thankfully, it appears that Microsoft didn’t remove the options, it just hid them. If, like me, you use the “run a script” option, here’s how you can re-enable it:

  1. Close Outlook, if running.
  2. Open Regedit.
  3. Navigate to HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\Security 
  4. Right-click on an empty space in the right pane and choose New > DWORD Value. Name the new value EnableUnsafeClientMailRules and set its value to 1.
  5. Close Regedit; open Outlook.

At this point, go to the “Rules & Alerts” applet. You should see that the “(error)” message next to any existing “run a script” rules is gone, although you might have to check the box to actually enable the rule again.

One thought on “Outlook 2016’s “Unsafe Rules””

  1. This trick is clever. Ever thought about why this rules are called “unsafe client rules” and Microsoft decided to disable them?

Leave a Reply!