Then you need to be careful to include enough polyfills because even what you assume would be there probably isn't, there's no Promises, no Array.prototype.includes, no arrow functions.
How about a consistent, reliable implementation of modern web standards? If you had to write a mail client in Java, would you rather target Java 1.5 or the most recent version?
Many small (and large) features together make a huge difference when it all adds up to providing an implementation of modern web standards that is consistent with other browsers and with modern standards. It's a huge burden to always be checking "is this supported in IE11 or is there a polyfill we can use" when wanting to use a native function or object (not to mention features that can't be polyfilled or transpiled, like ES6 proxies).
But honestly i'm not a fan of requiring the latest version of something just for developer convenience. It might have to do with growing up using outdated computers for years and seeing most programs not work or work slowly/badly, often without a good technical reason (outside programmer preference).
So, what is the use case here really, what sort of features IE11 does not provide that you'd need to implement a web-based mail client?
(note that i'm not trying to promote IE11 here, i just do not understand why IE11 would block implementing any feature to the point of dropping it entirely)