Go configure, accounts, sending. Set up an SMTP account and try to "automatically determine protocol". Gives: failure and wrong indications on all accounts, wrong port, wrong transport (no encryption instead of TLS 587). Such failure will be nefast for the less proficient user and may induce usafe settings without any transport security. Proven with: freenet, web.de, proximus (skynet.be). If set up by hand will work flawlessly. Reproducible: Always Steps to Reproduce: 1. create smtp 2. ask for automatic determination of available transport 3. Gives "no method available, check transport" or an unsafe method without encryption will be proposed). Actual Results: transport smtp relevation in configuration - advanced is broken - unsafe Expected Results: should work out of the box (did in the past) opensuse 13.2 from rpm protocol hit was smtp with TLS on port 587 (failure is complete whatever provider). This is AFAIK a very common setting. Workaround: RTFM of the provider that however is often difficult to reach and to find. Many less proficient user will be dumped here.
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.