http://catb.org/jargon/html/Z/Zawinskis-Law.html
Gmail is an email client. Facebook is now, too. So are the default 'mail' applications for Android and iOS. And let's not leave out Emacs :)
The challenge of email (which comes with its advantage of being ubiquitous today) is its plethora of standards documents one must read and respect if one wants to make a serious go of developing software that will work well with most of its corner cases.
But if you disagree, please write one - I'd be a very willing beta tester and would even be keen to help in a limited way.
Also, I think it's implicit that you trust your server. It's other people's servers you've got to worry about.
Email did this badly from the start, because it started in a much more trusting world of people who did not spam one another. Authentication features were added later, but there was no requirement to use them, which limits their effectiveness.
Perhaps for a project starting fresh now, this can be handled better?
This is a very cool and exciting idea but my feeling is that email clients are hard to code because they're full desktop applications. Even standard email clients are hard to get right - building a social network version (with encryption) would be quite a challenge.
The rewards could be nice though - such as being able to use mailinator or mixmaster for anonymity.