On Monday 06 February 2023, Simon Lees wrote:
On 2/6/23 13:23, Michael Hamilton wrote:
On Monday 06 February 2023, Michael Hamilton wrote:
Something changed in TW 2023020[123]+, KDE3:kmail3 can no longer send via SMTP details of the SMTP server ...
The following was logged, seems to point to protocol issues, but /etc/crypto-policies/back-ends/opensslcnf.config is the same on both new and old TW systems. I tried disabling apparmour, but that didn't seem to help (but maybe I did that wrong - used yast-services and a reboot). ...
I've edited out the log entries to only show the relevant entries, which are...
Feb 06 13:48:46 ksmserver[13902]: 40CF65DC027F0000:error:0A000102:SSL routines:ssl_choose_client_version:unsupported protocol:ssl/statem/statem_lib.c:1952: Feb 06 13:48:49 ksmserver[13902]: 40CF65DC027F0000:error:0A000102:SSL routines:ssl_choose_client_version:unsupported protocol:ssl/statem/statem_lib.c:1952: Feb 06 13:48:58 ksmserver[13923]: kioslave: ####### CRASH ###### protocol = smtps pid = 13923 signal = 11 Feb 06 13:49:00 ksmserver[13927]: kioslave: ####### CRASH ###### protocol = smtps pid = 13927 signal = 11 Feb 06 13:49:27 ksmserver[13902]: 40CF65DC027F0000:error:0A000102:SSL routines:ssl_choose_client_version:unsupported protocol:ssl/statem/statem_lib.c:1952: Feb 06 13:49:37 ksmserver[13902]: 40CF65DC027F0000:error:0A000102:SSL routines:ssl_choose_client_version:unsupported protocol:ssl/statem/statem_lib.c:1952: Feb 06 13:49:49 ksmserver[13946]: kioslave: ####### CRASH ###### protocol = smtps pid = 13946 signal = 11 ...
The cause is something in kdelibs3 3.5.10-241.19, possibly in combination with kdepim3 3.5.10-290.18. I used /var/cache/zypp with rpm --upgrade --force to revert to kdepim3-3.5.10-290.18.x86_64.rpm, which had no effect, but also reverting to kdelibs3-3.5.10-241.16.x86_64.rpm got everything working again.
Who would be the right contact for Tumbleweed_KDE3?
https://build.opensuse.org/project/users/KDE:KDE3 will give you a list, kde3 doesn't seem to be officially supported on tumbleweed.
Thanks. I've forwarded this to the person listed as "bugowner" for that project.