As a long-time user of eM Client, I wanted to provide some feedback and suggest an improvement to the way SSL/TLS settings are presented and configured in the application.
Currently, the SSL/TLS configuration options (e.g., “Use SSL if available,” “Force SSL,” “Use SSL on special port”) are somewhat ambiguous and don’t align well with the terminology used in most email service provider guides. This can create confusion for users when trying to match the settings from their provider’s instructions to eM Client.
The current issues:
Ambiguous Terminology: Terms like “Use SSL if available” and “Force SSL” do not clearly reflect standard encryption options like SSL/TLS or STARTTLS, making it difficult for users to understand exactly what encryption method is being used.
Mismatch with Service Provider Instructions: Most email service providers use familiar and consistent terms like SSL/TLS and STARTTLS, and guide users to specific ports (e.g., Port 993 for IMAP, Port 465 for SMTP). However, eM Client’s options don’t directly align with this common language, leading to unnecessary confusion.
Suggested Improvements:
Keep Existing Terminology, Add Standardized Information in Parentheses: Instead of changing the existing labels, I suggest adding standardized details in parentheses to provide clarity. For example:
Use SSL if available (SSL/TLS, Port 993 for IMAP, 465 for SMTP)
Force SSL (SSL/TLS, Port 993 for IMAP, 465 for SMTP)
Use SSL on special port (Custom port, SSL/TLS)
This would allow eM Client to keep its existing terminology while offering users a clearer understanding of the encryption method and the ports involved.
Port Automation: Where possible, eM Client could automatically configure the correct ports based on the encryption choice, reducing the need for manual adjustments and ensuring consistency with provider guidelines.
Consistency with Provider Documentation: Many email service providers (such as Gmail, Outlook, Yahoo, etc.) use consistent labels like SSL/TLS and STARTTLS to describe encryption options. While it’s not necessary to change the terminology in eM Client, adding port and encryption method details in parentheses would make it easier for users to match eM Client settings to provider instructions.
This change would make the setup process more intuitive for both new and experienced users, allowing them to more easily follow standard provider documentation.
Thank you for considering these suggestions. I look forward to seeing how eM Client continues to evolve!