3 ms·
I disagree. There is next to no code sharing between the server and client side of email--implementing the server side of the protocol is vastly different than
by jcranmer 7y ago
I disagree. There is next to no code sharing between the server and client side of email--implementing the server side of the protocol is vastly different than the client side, and even the server-server versus server-client sides of SMTP and NNTP are practically different protocols. Furthermore, Thunderbird already struggles to get enough developers to avoid compounding on its technical debt; such a large undertaking is simply not possible with the current manpower.
I'll also point out:
> - Email encryption standards for key acquisitions
This is basically a standardization problem. I've been involved in at least one failed attempt at standardization here.
> - folders/labels stored as imap keywords
The difficulty here is knowing when you can opt-in to this functionality, which is again basically a standardization process.
> - large file sending protocol using third party services
Thunderbird already supports this, and has for... 7 years or so?
> - msg retrieval when email severs experience outages
If I understand this right, this is basically having your MUA duplicate emails locally... which is what most MUAs do these days (at least on desktop).
> - development in mail list servers.
What development are you talking about? Mailman is pretty actively developed, they even had a GSoC project a few years back to add encrypted mailing list support.