Earlier quoted context omitted.
S/MIME is the closest to dead simple solution, but it requires trusting certificate authorities. It's a much better user experience, and honestly I'm surprised that no enterprise orgs have adopted it, because it would probably be cheaper than all this phishing training.
Enterprises, at least in the form of the U.S. federal government, have but there are two key drawbacks: 1. At least until recent, Microsoft implemented it as blocking code in the UI thread – open a message and Outlook won't paint until it can verify the cert, access your local key store (hope your token is in a USB port which is 100% reliable), etc. If you thought “Does that mean that revocation checks block the UI u…
Preventing forgery of @example.com is nice, but sadly doesn't matter that much, because a message fro "Your Boss" is just going to show up as Your Boss in the UI with most clients these days, amd Enterprise oriented clients are worse than the norm. The fastest way to see the actual addresses is to just press reply, which is irritating.