Evolution and Thunderbird configurations misleading
Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Evolution and Thunderbird configurations misleading
While setting up a new secure mail server, I'm finding that settings for Evolution and Thunderbird to be confusing. Most of this seems to be due to poor, or even wrong, choice of terminology. For example Evolution gives a choice between "TLS" and "SSL" for security. Duh ... those are just the same thing. Turns out "TLS" means to use "STARTTLS" (or "STLS" for POP) and "SSL" means to use "TLS" (formerly known as "SSL").
I think it would help if the developers for Evolution and Thunderbird were to get together and at least use the same wrong terminology. Then I could more easily write instructions to users to set up their mail client.
My exprience is that bug reports don't fix fundamental design flaws. It's even a struggle getting real bugs fixed that way. One bug I reported for Mozilla is still bouncing around, unfixed for years. A "major" bug (a standard function was producing radically wrong answers) in glibc didn't get fixed for 5 years. I'm tired of that process. If the developers can't talk to the public and discuss issues, then we need to move on and make something new.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.