Skip to main content
Jamf Nation, hosted by Jamf, is the largest Apple IT management community in the world. Dialog with your fellow IT professionals, gain insight about Apple device deployments, share best practices and bounce ideas off each other. Join the conversation.

Apple Mail keeps trying to run on Sierra?

As we've got new Macs coming in this summer and they can't accept anything lower than Sierra, I'm now working on setting up a Sierra software configuration.

One of the things we have set up on our JSS is that the Apple is blocked using Restricted Software (because we want people using Outlook instead). On Sierra what I am seeing is that the restriction message is popping up on a regular basis even when isn't loaded / isn't being used.

Does anyone know what causes this behaviour and how to stop it? Would simply deleting have any significant bad effects? We don't see this happening on 10.11 or 10.10.

Dan Jackson (Lead ITServices Technician)
Long Road Sixth Form College
Cambridge, UK.

Like Comment
Order by:
SOLVED Posted: 7/14/17 at 6:34 AM by davidacland

We had a similar issue recently. There were a few extra binaries that are in the /Applications/ bundle that were triggered occasionally, causing the "this software is restricted" message to appear, even when Mail wasn't running.

We switched to blocking the /Applications/ binary directly and it quietened down.

We are using a restriction in a configuration profile rather than the standard Jamf restricted software though.

SOLVED Posted: 7/14/17 at 10:18 AM by mvijay

change default email to Microsoft Outlook and try. It might help you.

SOLVED Posted: 7/14/17 at 12:00 PM by jimw

I wouldn't recommend deleting the Mail app. We had a similar issue in our environment. This thread helped solved our issue:

In the process name, you should drop the ".app" if you tick the "Restrict exact process name box".

SOLVED Posted: 7/17/17 at 5:35 AM by DanJ_LRSFC

@jimw thanks, that seems like it will work, I'll try that.

@mvijay I'm currently looking into ways we can do that with a script, but it seems fairly involved so to sort out the immediate issue I'm just going to correct our Restricted Software entry in the first instance.