It's under the "I don't give a shit as long as some dude in china doesn't slap another name on it and sell it licence". I am not sure what the official name for that is tho :-)
Unfortunately, there's not really a good, widely used license that does what you want, mostly because you run into problems pretty quickly based on derivative works with what you want. Let's say somebody merges your email client with a browser - can they call that by a different name? Can they sell that?
Anyhow, I'd suggest looking at looking at the Apache or BSD licenses (if you want the broadest use) or the GPL (if you want to ensure that modifications to the code must be distributed with any binaries made from the code). Licenses are a bit of a pain, but you can just pick one of the common ones and it'll really help adoption.
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.See https://www.gnu.org/licenses/gpl-faq.html#ReleaseUnderGPLAnd...
http://www.perlfoundation.org/artistic_license_2_0
It's an interesting balance between freedom and giving back - may be more suited to what you want or may not.
Just say its "public domain" or MIT or Apache in a file called license.txt in the project and forget about it.