Bug 333647 - after upgrade to 4.13: one of two IMAP resources is reported "not functional"
Summary: after upgrade to 4.13: one of two IMAP resources is reported "not functional"
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.13
Platform: Kubuntu Linux
: NOR major
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-20 11:20 UTC by m.eik michalke
Modified: 2017-01-07 22:45 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m.eik michalke 2014-04-20 11:20:48 UTC
after i upgraded to KDE SC 4.13 (kubuntu 14.04), one of two formerly working IMAP resources is suddenly unavailable. on another machine which is still running KDE SC 4.12, both servers still respond like a charm, as they did on both machines for the past months.

directly after the upgrade, akonadi didn't work *at all* due to a dorked mySQL database upgrade. i  was able to fix it by applying the workaround described here: https://bugs.kde.org/show_bug.cgi?id=331867#c16

after that, kmail seemed to be working again, but i'm still stuck with one IMAP account not working. i tried to add a new resource for the same server, it still won't fetch mails: akonadictl says "akonadi_imap_resource_1(7031)/kdepimlibs (kimap) KIMAP::LoginJob::connectionLost: Connection to server lost  0", kmail shows the folder in red and appends the attribute "(offline)".


Reproducible: Always

Steps to Reproduce:
1. start kmail
Actual Results:  
kmail complains the resouce was not functional and is now "online" (wich sounds like a contradiction in itself).

Expected Results:  
kmail should fetch mails like it used to.

in the akonadictl messages, i noticed this one repeatingly (i replaced the search term with $SEARCHTERM):

<akonadictl log>
Executing search "searchUpdate-1397992226" 
json_parser - syntax error found,  forcing abort, Line 1 Column 0 
akonadiserver(6968) SearchPlugin::search: invalid query  "select distinct ?r ?reqProp1 where { { ?r <http://akonadi-project.org/ontologies/aneo#akonadiItemId> ?reqProp1 . ?r <http://www.semanticdesktop.org/ontologies/2007/01/19/nie#isPartOf> <nepomuk:/res/c61280ec-7c17-498d-93cb-8cf3102a78d5> . { ?r <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#bcc> ?v1 . ?v1 <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#cc> ?v2 . ?v2 <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#to> ?v3 . ?v3 <http://www.semanticdesktop.org/ontologies/2007/03/22/nco#hasEmailAddress> ?v4 . ?v4 <http://www.semanticdesktop.org/ontologies/2007/03/22/nco#emailAddress> ?v5 . FILTER(bif:contains(?v5, "'$SEARCHTERM*'")) . } UNION { ?r <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#messageSubject> ?v6 . FILTER(bif:contains(?v6, "'$SEARCHTERM*'")) . } UNION { ?r <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#plainTextMessageContent> ?v7 . FILTER(bif:contains(?v7, "'$SEARCHTERM*'")) . } UNION { ?r <http://www.semanticdesktop.org/ontologies/2007/01/19/nie#isPartOf> ?v8 . ?v8 <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#plainTextMessageContent> ?v9 . FILTER(bif:contains(?v9, "'$SEARCHTERM*'")) . } . ?r a <http://www.semanticdesktop.org/ontologies/2007/03/22/nmo#Email> . } . FILTER(REGEX(STR(?r), '^nepomuk:/res')) . }" 
searchUpdateResultsAvailable 340 0 results 
Got 0 results, out of which 0 are already in the collection 
Added 0 
Search done "searchUpdate-1397992226" (without remote search) 
Search update finished 
All results: 0 
Removed results: 0
</akonadictl log>

no idea if this is related.
Comment 1 m.eik michalke 2014-04-23 18:28:57 UTC
please give me a hint how i can help to debug this. i am totally unable to work on the "upgraded" machine. removing the resouce and re-adding it didn't help but only also remove the offline folder from kmail and invalidate all filters set for it. this is pretty grave.

how can i make akonadi tell my *why* it closes the connection to the IMAP server, when it obviously still manages to fetch mails from it with 4.12?
Comment 2 Christian Mollekopf 2014-04-24 09:52:16 UTC
(In reply to comment #1)
> please give me a hint how i can help to debug this. i am totally unable to
> work on the "upgraded" machine. removing the resouce and re-adding it didn't
> help but only also remove the offline folder from kmail and invalidate all
> filters set for it. this is pretty grave.
> 
> how can i make akonadi tell my *why* it closes the connection to the IMAP
> server, when it obviously still manages to fetch mails from it with 4.12?

Is it perhaps related to https://bugs.kde.org/show_bug.cgi?id=328625?
Comment 3 m.eik michalke 2014-04-24 11:36:51 UTC
> Is it perhaps related to https://bugs.kde.org/show_bug.cgi?id=328625?

the mailserver in question is mail.rz.uni-duesseldorf.de -- as far as i can 
tell, it hat SSLv2 disabled.

can i somehow (i.e., wrapper or config file) instruct kmail/akonadi/openssl to 
only try TLS?

thanks!
Comment 4 m.eik michalke 2014-04-28 17:37:36 UTC
today this hit one of my colleagues, at work: no more mails, the same error message, same mailserver. so for the time being, fetching mails with kmail 4.13 is impossible for at least all users at the university of düsseldorf.
Comment 5 kosar88 2014-04-29 11:33:32 UTC
The issue also affects me. I am, too, using the mail.rz.uni-duesseldorf.de mail server in KMail.
Comment 6 m.eik michalke 2014-05-03 10:40:16 UTC
here's some news:

KDE SC 4.13 on kubuntu 14.04: connection to mail.rz.uni-duesseldorf.de fails
KDE SC 4.13 on kubuntu 13.10: *no* problem fetching mails from mail.rz.uni-
duesseldorf.de

on 13.10, KDE SC 4.13 was installed by using the kubuntu PPA packages. i also 
tried to connect from a freshly created user account on 14.04, to ensure that 
it's not caused by leftovers from previous configuration -- still the same 
problem.

i therefore also reported the problem here: 
https://bugs.launchpad.net/bugs/1315637
Comment 7 Denis Kurz 2016-09-24 20:44:40 UTC
This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 8 Denis Kurz 2017-01-07 22:45:46 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.