The imap version of my account using imap.kabelmail.de crahes as soon as any synchronization is initiated. The folder structure is shown, but no e-mails. The account works for other e-mail clients (thunderbird, evolution). The current kdepim installation (opensuse tumbleweed using kdepim 16.04) works properly for other e-mail accounts, e.g. those imap resources for business. Here some details. Crash report after 'akonadictl restart' http://pastebin.com/eZBAA29u Developer information copied from the crahs report dialog http://pastebin.com/qY8yjn25 I also installed all sources for debugging with gdb. Here is the output. http://pastebin.com/BzkVVsjM The debugger stops at line 84 in file syscall-template.S which is located in /usr/src/debug/glibc-2.23/sysdeps/unix in case of current openSUSE Tumbleweed. Here is the corresponding backtrace http://pastebin.com/xpA29dPP Reproducible: Always Steps to Reproduce: 1. Add account using imap.kabelmail.de to kmail. 2. Synchronize 3. Observe that akonadi_imap_resource crashes Actual Results: The crash report dialog opens. The folder structure of the account is visible. But no synchronization of the e-mails. Expected Results: Show all e-mails I tried to synchronize with imap.kabelmail.de for several months using different version of kdepim (15.08, 15.12, 16.04) on either opensuse Leap 42.1 or Tumbleweed. Furthermore, different users have been used. I like to exclude any configuration issues because only this account shows this behavior and all other imap resource work properly. I suppose that the specific pair of akonadi_imap_resource and server software at imap.kabelmail.de causes this trouble. I have no specific information on the server software.
Git commit 8933e1dcfe7686683c5d804b968dfc4a3af40f34 by Daniel Vrátil. Committed on 11/06/2016 at 09:17. Pushed by dvratil into branch 'Applications/16.04'. Fix crash when server returns non-standard EXPUNGE response Apparently some servers don't mention "EXPUNGE" in untagged EXPUNGE response. This wasn't handled correctly due to a typo in response length check. The code no longer crashes in such case, but will now print "Unhandled response" warning, which is OK, since we don't handle results of the EXPUNGE command anyway. FIXED-IN: 16.04.3 M +1 -0 autotests/CMakeLists.txt A +89 -0 autotests/expungejobtest.cpp [License: GPL (v2+)] M +1 -1 src/expungejob.cpp http://commits.kde.org/kimap/8933e1dcfe7686683c5d804b968dfc4a3af40f34
Dear Daniel Vratil, I am a long term KDE user with some serious problems to set up a special IMAP account properly with KMail, see your solution to https://bugs.kde.org/show_bug.cgi?id=364045 and the next problem behind the first bug, see https://bugs.kde.org/show_bug.cgi?id=366238 Searching for answers on the web, I got in contact with your blog. Especially with http://www.dvratil.cz/2016/01/kde-pim-still-alive-and-rocking/. There, you close the article with "so if you like KDE (PIM) and would like to help us, let’s talk!" Ok, here I am. I think that KDE needs a native PIM solution, i.e. KDEPIM. And I am willing to contribute beyond my personal interest. Being a professor at a German university, see also http://www.bauwesen.tu-dortmund.de/nmi/en/chair/index.html, I am involved in software development (Fortran, Matlab for Finite Element Method), I know the problems of software development very well. Especially in small or even very small groups. Thus, being overloaded myself, I could not contribute to your daily development tasks. Nevertheless, I may contribute at some other place. What is needed? Today, I could only mention some observations. If someting is not working with KDEPIM, there are actually only few hints about the nature of the problem, i.e. - wrong local configuration of KDEPIM, - problems with the e-mail server of the provider - really a bug in KDEPIM. It is hardly possible to choose the correct category. Is it possible to set up a white and black list naming providers or server software which are known to work or fail to work? Is it possible to ask the community in some kind of review reporting positive and negative experience? Would it be helpful to set up a list of test accounts (different providers and different server software) where some scenarios are frequently tested? Ok. Who should do it? But first of all, what are the best means to optimize the developement (and bug tracking) process. So, I am willing to talk. Best regards Franz-Joseph Barthold Am Sonntag, 12. Juni 2016, 09:46:35 CEST schrieben Sie: > https://bugs.kde.org/show_bug.cgi?id=364045 > > Daniel Vrátil <dvratil@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Version Fixed In| |16.04.3 > Status|UNCONFIRMED |RESOLVED > Latest Commit| |http://commits.kde.org/kima > | |p/8933e1dcfe7686683c5d804b9 > | |68dfc4a3af40f34 > > Resolution|--- |FIXED > > --- Comment #1 from Daniel Vrátil <dvratil@kde.org> --- > Git commit 8933e1dcfe7686683c5d804b968dfc4a3af40f34 by Daniel Vrátil. > Committed on 11/06/2016 at 09:17. > Pushed by dvratil into branch 'Applications/16.04'. > > Fix crash when server returns non-standard EXPUNGE response > > Apparently some servers don't mention "EXPUNGE" in untagged EXPUNGE > response. This wasn't handled correctly due to a typo in response > length check. The code no longer crashes in such case, but will now > print "Unhandled response" warning, which is OK, since we don't > handle results of the EXPUNGE command anyway. > FIXED-IN: 16.04.3 > > M +1 -0 autotests/CMakeLists.txt > A +89 -0 autotests/expungejobtest.cpp [License: GPL (v2+)] > M +1 -1 src/expungejob.cpp > > http://commits.kde.org/kimap/8933e1dcfe7686683c5d804b968dfc4a3af40f34
*** Bug 354982 has been marked as a duplicate of this bug. ***