http://bugzilla.opensuse.org/show_bug.cgi?id=957417 http://bugzilla.opensuse.org/show_bug.cgi?id=957417#c1 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #1 from Wolfgang Bauer --- 15.08.3 is the latest release at the moment. KMail 5.1 should be part of KDE Applications 15.12, to be released in 2 weeks. See also: https://techbase.kde.org/Schedules/Applications/15.12_Release_Schedule The latest "unstable" version, i.e. a current git snapshot, is always available in KDE:Unstable:Applications though, but use that at your own risk... -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=957417 http://bugzilla.opensuse.org/show_bug.cgi?id=957417#c3 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Wolfgang Bauer --- (In reply to Matthias Schünemann from comment #2)

Okay, thank you for the link. Will the 15.12 version be immediately available from the SUSE repositories or will there be a delay for inhouse testing?

There is no openSUSE "inhouse testing", especially not for those addon repos. 15.12 will be available in KDE:Applications as soon as it is released. Just one note: the KDE bug report you mentioned seems to be about a completely different problem (mail import from Thunderbird and mbox) than you describe here. So I'm not sure *your* problem will be fixed in 15.12.0... There are some other upstream bug reports about synchronization problems with outlook.office365.com though. https://bugs.kde.org/show_bug.cgi?id=351814 (you commmented there anyway) https://bugs.kde.org/show_bug.cgi?id=354807 Maybe the KDE4 version (4.14.x) would work better? It is still included in Leap 42.1. You might have to wipe out the Akonadi database though, I'm not sure that a downgrade is supported. -- You are receiving this mail because: You are on the CC list for the bug.