I recently failed to install gpg2 on freebsd (for some reason it barks at me and fails and I don't care enough to waste my time on it) and decided to give S/MIME a chance with a signed cert from comodo. (which was free, just to try)
I have to say though the experience is beyond reasonable, it's very easy to get to grips with. If you're using S/MIME, I see a little verified badge in my client, not only that, if I've receieved signed mail from you, I can reply with an encrypted document that only you can decrypt.
This works with CC's and everything. The CA cargo-cult crap definitely has a benefit when it comes to web-of-trust.
(YMMV, I was using Thunderbird)
No more public key exchange. I checked and Thunderbird often checks the CRL for the certificate I have. I also checked revocation of that certificate and thunderbird shows a big warning about it being invalid. (although it doesn't specify expired or revoked).
I use it (in El Capitan), it works really well, it's the first time I've been regularly signing my messages with PGP.
So it turns out that the "standard" email encryption is actually S/MIME, and it works pretty much everywhere (non-webmail) out of the box, with fairly decent UI. It even works on iPhones.
Wait, what? Apple Mail supports S/MIME, not GPG. Competing standards strike again.
If the other person has S/MIME, Apple Mail does have a very easy experience. I can't speak for the merits of either security-wise.
Also, I think this is the sort of thing Keybase is good for. There's a level of indirection pasting into Keybase, but it's pretty easy to set up and (for non-Snowden levels of paranoia) makes it very easy to start sending encrypted mail to somebody else. The new Keybase chat is also an option.