[Akonadi] [Bug 423672] org.kde.pim.imapresource: Failed to create folder on server: "Create failed, server replied: ... NO Mailbox already exists ... [ ALREADYEXISTS ]"
https://bugs.kde.org/show_bug.cgi?id=423672 Christian Mollekopf changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |kimap/commit/ee2900e3539483 |kimap2/commit/ce0e9873d3a89 |b6f3d5eadfcf8cfc9c6ed42abe |7fee7fd9f8f7649ef4abd3c4627 --- Comment #6 from Christian Mollekopf --- Git commit ce0e9873d3a897fee7fd9f8f7649ef4abd3c4627 by Christian Mollekopf, on behalf of Dennis Schridde. Committed on 06/08/2020 at 12:59. Pushed by cmollekopf into branch 'master'. Idempotent CREATE and DELETE If CREATE fails with an ALREADYEXISTS response code, that is not an error since the intended result (the object existing at the target location) has been achieved. Likewise, if DELETE fails with an NONEXISTENT response code, that is not an error since the intended result (the object being gone from the target location) has been achieved. Please note that for RENAME response code ALREADYEXISTS *is* an error since the content of the source folder was not moved as intended. cf. https://tools.ietf.org/html/rfc5530#section-3 M +27 -0src/createjob.cpp M +2-1src/createjob.h M +27 -0src/deletejob.cpp M +2-1src/deletejob.h https://invent.kde.org/pim/kimap2/commit/ce0e9873d3a897fee7fd9f8f7649ef4abd3c4627 -- You are receiving this mail because: You are the assignee for the bug.
[Akonadi] [Bug 267884] akonadi imap doesn't work with gssapi authentication
https://bugs.kde.org/show_bug.cgi?id=267884 --- Comment #26 from Christian Mollekopf <mollek...@kolabsys.com> --- The patch looks indeed harmless. If you can give it a try (to see wether non GSSAPI usage breaks somehow) we could indeed merge it if it solves the issue. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 236600] KMimeType Crash
https://bugs.kde.org/show_bug.cgi?id=236600 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|REOPENED|RESOLVED CC||mollek...@kolabsys.com Resolution|--- |WORKSFORME -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 341192] Moving messages does not synchronize to disk
https://bugs.kde.org/show_bug.cgi?id=341192 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com Component|IMAP resource |Maildir Resource Assignee|chrig...@fastmail.fm|kdepim-bugs@kde.org -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 340614] assertion failure in KIMAP::ImapInterval::setBegin
https://bugs.kde.org/show_bug.cgi?id=340614 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com --- Comment #8 from Christian Mollekopf mollek...@kolabsys.com --- As pointed out by christophe, fixed in af03ba2b. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 340622] New: IMAP Requests should be split if they get too large
https://bugs.kde.org/show_bug.cgi?id=340622 Bug ID: 340622 Summary: IMAP Requests should be split if they get too large Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: mollek...@kolabsys.com CC: kdepim-bugs@kde.org, vkra...@kde.org Useful information by Jan Kundrat: A client should limit the length of the command lines it generates to approximately 1000 octets (including all quoted strings but not including literals). If the client is unable to group things into ranges so that the command line is within that length, it should split the request into multiple commands. -- http://tools.ietf.org/html/rfc2683#section-3.2.1.5 This got recently upgraded on QRESYNC-compliant servers to read: a client should limit the length of the command lines it generates to approximately 8192 octets (including all quoted strings but not including literals) https://tools.ietf.org/html/rfc7162#section-4 As a random data point, Trojita doesn't attempt to do these bits. At the same time, we do use the UID ranges pretty heavily, so that the numbers often go out as e.g. 100:200. As a first step we could ensure that intervals are always compressed. This doesn't always happen as we can i.e. see in BUG 332323 for UID STORE \Deleted (mass message removal). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 340622] IMAP Requests should be split if they get too large
https://bugs.kde.org/show_bug.cgi?id=340622 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332323] Error in IMAP command UID: Too long argument
https://bugs.kde.org/show_bug.cgi?id=332323 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- Thanks for the report, I'll track this in a separate ticket. *** This bug has been marked as a duplicate of bug 340622 *** -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 340622] IMAP Requests should be split if they get too large
https://bugs.kde.org/show_bug.cgi?id=340622 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||m...@apache.org --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- *** Bug 332323 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 339393] Akonadi fail to fetch IMAP folder content with over 100MiB of messages (akonadi try to fetch too many UIDs at once)
https://bugs.kde.org/show_bug.cgi?id=339393 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 333762] Certificate dialog loops
https://bugs.kde.org/show_bug.cgi?id=333762 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 340622] IMAP Requests should be split if they get too large
https://bugs.kde.org/show_bug.cgi?id=340622 --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- In theory, UID ranges work nicely but in practice, they only work if you don't delete emails. You can still use them as the server is required to ignore any UIDs not present at the server. I.e. you delete five adjacent e-mails with UID 123, 160, 177, 190 and 205, you can do that via 123:205. Yes, doing this requires extra intelligence at a wrong layer, so there are not that many benefits in doing it. = We can probably compress the ranges even more if we know that certain uid's are not available on the server. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 340614] assertion failure in KIMAP::ImapInterval::setBegin
https://bugs.kde.org/show_bug.cgi?id=340614 --- Comment #11 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to RJVB from comment #10) PS: wouldn't it be of interest to know why this issue was triggered on a GMail imap account, which AFAIK no longer provides Exchange features? The codepath is not exchange specific, it's just that the chunking is not actually used if it's not exchange (one large chunk). It would still hit the error after the first chunk though. The only thing that is a bit strange is that the error should be hit every time, meaning it should have shown up during testing? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335776] IMAP agent crashes frequently
https://bugs.kde.org/show_bug.cgi?id=335776 --- Comment #6 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Daniel Vrátil from comment #5) I discovered one of the possible causes of the crash: In ItemSync, when the ItemCreateJob fails, the TransactionSequence is rolled back and ItemSync emits finished() - to which ResourceBase reacts by marking the task as done and scheduling another task. However the BatchFetcher in IMAP resource is not aware of this and keeps feeding more items through ResourceBase::itemsRetrieved() - which eventually hits the assert in ResourceBase, because ResourceBase has already moved on to another non-sync task. Interesting, I actually checked this codepath and though it's fine. ItemSync::slotResult is supposed to handle this case by silently ignoring errors and continuing anyways. I take that somehow doesn't work then? Not sure how to solve this - ItemSync is internal to ResourceBase, so there's no way how to tell resource implementation that ItemSync has failed and so that they should stop sending more items. Just as we can ask for more items, we should also be able to signal that the task was aborted. But it's in any case a mess to pass this through the current API, so I'd prefer to postpone that for a new API. Good-enough fix would probably be to make TransactionSequence in ItemSync to ignore ItemCreateJob failures and handle the error manually (somehow) and continue, or just abort, but let the caller to feed ItemSync all its items (just do nothing with them) and then terminate - i.e. prevent ItemSync for ever aborting prematurely. Proper fix would be to make Sync a cancellable operation, so that we can tell resource to stop feeding ResourceBase with items because there was an error. I'm for simply continuing with the sync. Regarding the reasons for ItemCreateJob failure: in my case this was happening because somehow I had two items with the same RID in one Collection (probably the RID wasn't reset during MOVE or something), so MERGE handler will abort with Multiple merge candidates error and so the ItemCreateJob fails. Something to investigate. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kdep ||im-runtime/ff02785839e9b41b ||587fac5ca9bc2768a2729eec Resolution|--- |FIXED --- Comment #69 from Christian Mollekopf chrig...@fastmail.fm --- Git commit ff02785839e9b41b587fac5ca9bc2768a2729eec by Christian Mollekopf. Committed on 10/09/2014 at 08:21. Pushed by cmollekopf into branch 'KDE/4.14'. IMAP-Resource: Detect invalid UIDNEXT values and fall-back to sequence number based fetches. We run into this codepath with courier imap. M +7-0resources/imap/batchfetcher.cpp M +35 -11 resources/imap/retrieveitemstask.cpp M +36 -1resources/imap/tests/testretrieveitemstask.cpp http://commits.kde.org/kdepim-runtime/ff02785839e9b41b587fac5ca9bc2768a2729eec -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #70 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Marcel Naziri from comment #67) (In reply to Christian Mollekopf from comment #65) A proper fix would be to implement the STATUS command. I won't do that but you're welcome to supply patches. After reading in RFC 3501 about the STATUS command I doubt that it would be the right way. :( It says that STATUS should not be used on the currently selected mailbox. This could be worked around by deselecting first. Also this command can be quite slow. Yeah, I guess it depends on the definition on slow. If you want something fast you better use another IMAP server. On the other hand I found by chatting with a Courier IMAP server via netcat that the STATUS result values like MESSAGES, RECENT, UIDNEXT, UIDVALIDITY and UNSEEN are only updated if prior to this a SELECT or EXAMINE command was executed. So Courier seems not to be conform to the RFC. Indeed, but in that case we could run STATUS after a SELECT that didn't return UIDNEXT. Anways, I'm not going to work on this any further. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335776] IMAP agent crashes frequently
https://bugs.kde.org/show_bug.cgi?id=335776 --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- dfaure reported a disconnect just before a similar crash, so let's assume that's the cause. This happens due to the CollectionFetchJob that is not aborted on disconnect, so we need to fix that. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #72 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Rigo Wenning from comment #71) (In reply to Christian Mollekopf from comment #70) Christian, if I change to another imap-server than Courier, the performance improvements would still work, right? You haven't just reverted to the 4.13.3 state, I hope. No, I simply added an additional codepath that is only used if UIDNEXT is not delivered on SELECT. So other imap servers should not be affected at all by this change. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335776] IMAP agent crashes frequently
https://bugs.kde.org/show_bug.cgi?id=335776 --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- Created attachment 88644 -- https://bugs.kde.org/attachment.cgi?id=88644action=edit debug info by dfaure I suppose this version of the crash could be explained if for some reason the the task was killed (although we don't see a disconnect), and the batchfetcher continued afterwards. I.e. the abortActivity codepath disconnects the sessions which in turns triggers cancelTask in ResourceTask (thus ending the task). However, the internal BatchFetcher job continues to run as it only get's deleted once the session is deleted. Further both the session and the task are deleted via deleteLater, meaning the BatchFetcher still gets a chance to issues a signal through the ResourceTask that then triggers itemsRetrieved (resulting in a crash since cancelTask has already been called). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Attachment #88482|0 |1 is obsolete|| --- Comment #65 from Christian Mollekopf mollek...@kolabsys.com --- Created attachment 88636 -- https://bugs.kde.org/attachment.cgi?id=88636action=edit version 3 of patch for fallback with invalid uidnext I think this should now restore functionality as before. Can somebody try if it works? A proper fix would be to implement the STATUS command. I won't do that but you're welcome to supply patches. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Attachment #88453|0 |1 is obsolete|| --- Comment #42 from Christian Mollekopf mollek...@kolabsys.com --- Created attachment 88482 -- https://bugs.kde.org/attachment.cgi?id=88482action=edit version 2 of patch for fallback with invalid uidnext The last patch was indeed incomplete, sorry about that. This one should do better. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #44 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Carsten Pfeiffer from comment #43) Thanks Christian, that one works. Great, thanks for testing. kmail shows all mails again, but everytime I switch folders, it will synchronize the entire folder. Yes, that is expected. I guess that was to be expected from the discussion here, so I hope that this is a quick fix and not the solution. I don't plan on working on this any further. It could be improved, but courier should just send UIDNEXT which is what is specified in RFC 3501 (IMAP). Note that this simply reestablishes what was done before (You just didn't have any debug messages telling you that a full sync was executed). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #53 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to Marcel Naziri from comment #51) (In reply to Carsten Pfeiffer from comment #50) (In reply to Marcel Naziri from comment #49) Anyone tested my patch for ImapInterval in kdepimlibs? Will do so tonight or tomorrow night. Completely missed that the patch is attached. I realized that with my patch flags (e.g. read/unread) changed by another client aren't reflected in kmail when refreshing the folder. not until mailbox content is changed (new mail arrived or something moved) the flags are updated. Is this also happening with Christians patch v2? Please note that your patch is really rather a workaround that cannot be upstreamed. Thanks a lot for your analysis though as it pointed me in the right direction. What's currently missing from my patch is that we are not using the optimization that avoid downloading all messages on every sync. This is because we usually rely on a combination of message-count and uidnext to detect if new messages are available or old ones have been deleted. Whitout uidnext we could still avoid a sync if the messagecount remains the same, but then we would run into the problem that we for instance would never notice if i.e. one message has been removed and another one added (which is nasty because it's very unpredictable). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #39 from Christian Mollekopf mollek...@kolabsys.com --- Created attachment 88453 -- https://bugs.kde.org/attachment.cgi?id=88453action=edit patch for fallback with invalid uidnext Can somebody try this patch for kdepim-runtime? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 --- Comment #27 from Christian Mollekopf mollek...@kolabsys.com --- So kdepim-runtime seems to be affected. RetrieveItemsTask::onFinalSelectDone gets -1 values for nextUid which are not correctly mapped to an IMAP interval like 1:* instead it results in 1:-1 That does sound like a server bug, or at least I don't know when UIDNEXT 0 would make any sense. I suppose we can catch this case and just fallback a very large UIDNEXT value. Can other's confirm this is indeed the problem? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 338186] Since updating to the latest Kubuntu packages Kmail is not picking up imap mail.
https://bugs.kde.org/show_bug.cgi?id=338186 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #16 from Christian Mollekopf mollek...@kolabsys.com --- We'll need an imap log (https://techbase.kde.org/Projects/PIM/Akonadi/Debug_IMAP) and what imap server this is failing with. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335795] IMAP namespace support is incomplete/insufficient on large imap accounts
https://bugs.kde.org/show_bug.cgi?id=335795 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |WONTFIX --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- subscriptions allow you to not download what you don't want. I disagree that specifing a prefix path adds anything useful. Therefore I have to close this, sorry. Thanks for the elaborate suggestion though (no irony intended). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 319776] Akonadi crashed, possibly because of sudden lack of network connection, caused by the laptop going into suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=319776 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- CC||mollek...@kolabsys.com --- Comment #19 from Christian Mollekopf mollek...@kolabsys.com --- I just ran into this again after resuming from suspend. Can't really explain what's happending though. akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection christian.mollekopfatgmail.com/Be[156/47975] parent (christian.mollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection christian.mollekopfatgmail.com/Reisen with parent (christian.mollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Archive with parent (cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/INBOX with parent ( cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Personal with parent (cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Receipts with parent (cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Sent with parent ( cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Trash with parent ( cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Travel with parent (cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection cmollekopfatgmail.com/Work with parent ( cmollekopfatgmail.com) akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection new folder with parent () akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection outbox with parent () akonadi_kolab_resource_2(9740) KolabRetrieveCollectionsTask::createCollection: creating collection sent-mail with parent () akonadi_kolab_resource_2(9740)/libakonadi Akonadi::CollectionSync::Private::execute: void Akonadi::CollectionSync::Private::execute() localListDo ne: false deliveryDone: true akonadi_kolab_resource_2(9740)/libakonadi Akonadi::CollectionSync::Private::execute: void Akonadi::CollectionSync::Private::execute() localListDo ne: true deliveryDone: true drkonqi(18437) KCrashBackend::stopAttachedProcess: Sending SIGSTOP to process akonadi_kolab_resource_2(9740)/kdepimlibs (kimap) KIMAP::SessionThread::doCloseSocket: close drkonqi(18437) KCrashBackend::continueAttachedProcess: Sending SIGCONT to process QSocketNotifier: Invalid socket 10 and type 'Read', disabling... The crash can be reproduced sometimes. -- Backtrace: Application: IMAP Account 12 of type Kolab Groupware Server (akonadi_kolab_resource), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. 81T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fa6f84018c0 (LWP 9739))] Thread 2 (Thread 0x7fa6ec08d700 (LWP 18418)): #0 0x0034ef0ea9dd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x0034f20495b4 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7fa6e400e990, timeout=-1, context=0x7fa6e401b420) at gmain.c:4007 #2 g_main_context_iterate (context=context@entry=0x7fa6e401b420, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3708 #3 0x0034f20496dc in g_main_context_iteration (context=0x7fa6e401b420, may_block=1) at gmain.c:3774 #4 0x0034afdb5af6 in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #5 0x0034afd8595f in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #6 0x0034afd85cad in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /lib64/libQtCore.so.4 #7 0x0034afc79e8f in QThread::exec() () from /lib64/libQtCore.so.4 #8 0x0034afc7c6bf in QThreadPrivate::start(void*) () from /lib64/libQtCore.so.4 #9 0x0034ef807f33 in start_thread (arg=0x7fa6ec08d700) at pthread_create.c:309 #10 0x0034ef0f4ded in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7fa6f84018c0 (LWP 9739)): [KCrash Handler] #6 0x0001
[Akonadi] [Bug 319776] Akonadi crashed, possibly because of sudden lack of network connection, caused by the laptop going into suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=319776 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|REOPENED|CONFIRMED Platform|Ubuntu Packages |Compiled Sources Version|4.10|GIT (master) -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 319776] Akonadi crashed, possibly because of sudden lack of network connection, caused by the laptop going into suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=319776 --- Comment #20 from Christian Mollekopf mollek...@kolabsys.com --- That was the wrong console output... akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::SessionPrivate::responseReceived: Received BYE: idle for too long akonadi_kolab_resource_11(9739) ImapResourceBase::doSetOnline: online= false akonadi_kolab_resource_11(9739) ImapResourceBase::doSetOnline: online= true akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::SessionThread::doCloseSocket: close akonadi_kolab_resource_11(9739)/kdeui (Wallet) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet(). kwalletd(9040)/kdeui (Wallet) KWalletD::openAsync: openAsync for :1.1163 klauncher(9023)/kdecore (KSycoca) KSycocaPrivate::openDatabase: Trying to open ksycoca from /var/tmp/kdesycoca-custom klauncher(9023)/kio (KLauncher) KLauncher::processRequestReturn: /usr/bin/kwalletmanager (pid 18048) up and running. akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::LoginJob: KIMAP::LoginJob(0x248b280) akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::SessionThread::reconnect: connectToHost 192.168.122.10 993 akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::doStart: KIMAP::LoginJob(0x248b280) akonadi_kolab_resource_11(9739)/kssl KTcpSocket::showSslErrors: The host name did not match any of the valid hosts for this certificate akonadi_kolab_resource_11(9739)/kssl KTcpSocket::showSslErrors: The certificate is self-signed, and untrusted akonadi_kolab_resource_11(9739)/kssl KTcpSocket::showSslErrors: The certificate has expired akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::SessionThread::sslConnected: Initial SSL handshake failed. cipher.isNull() is false , cipher.usedBits() is 256 , the socket says: Unknown error and the list of SSL errors contains 3 items. akonadi_kolab_resource_11(9739)/kssl KIO::SslUi::askIgnoreSslErrors: Error list empty after removing errors to be ignored. Continuing. kwalletmanager(18050)/kdeui (KNotification) KStatusNotifierItemDBus::KStatusNotifierItemDBus: service is org.kde.StatusNotifierItem-18050-1 akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::handleResponse: Capability * akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::handleResponse: Capabilities updated: (IMAP4rev1, LITERAL+, ID, ENABLE, ACL, RIGHTS=kxte, QUOTA, MAILBOX-REFERRALS, NAMESPACE, UIDPLUS, NO_ATOMIC_RENAME, UNSELECT, CHILDREN, MULTIAPPEND, BINARY, CATENATE, CONDSTORE, ESEARCH, SORT, SORT=MODSEQ, SORT=DISPLAY, THREAD=ORDEREDSUBJECT, THREAD=REFERENCES, ANNOTATEMORE, LIST-EXTENDED, WITHIN, QRESYNC, SCAN, XLIST, URLAUTH, URLAUTH=BINARY, X-NETSCAPE, AUTH=PLAIN, AUTH=LOGIN, SASL-IR, COMPRESS=DEFLATE, IDLE) akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::handleResponse: Capability A01 akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::handleResponse: Login A02 akonadi_kolab_resource_11(9739)/kdepimlibs (kimap) KIMAP::LoginJob::~LoginJob: KIMAP::LoginJob(0x248b280) akonadi_kolab_resource_11(9739) ImapResourceBase::doSetOnline: online= true akonadi_kolab_resource_11(9739)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection INBOX with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Arbeit with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Belege with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Calendar with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Configuration with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Contacts with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Default List with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Drafts with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Freebusy with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Journal with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Mobile List with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Notes with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Privat with parent () akonadi_kolab_resource_11(9739) KolabRetrieveCollectionsTask::createCollection: creating collection Reisen
[Akonadi] [Bug 335795] IMAP namespace support is incomplete/insufficient on large imap accounts
https://bugs.kde.org/show_bug.cgi?id=335795 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to RJVB from comment #2) Have you actually tried to use subscriptions in a use case like the one I described? Your claim about subscriptions is true only in theory, in practice one has to wait longer for a possibility to subscribe to only the desired mailboxes than it takes to decide to install another email client, install, configure and start using it. Much longer. Erm, what? So is the problem that the syncing starts before you have the chance to adjust subscriptions? If that is so, you have an entierly valid point, and we can fix it whenever I get around to it. Please open an according bugreport in that case. We could also add the subscription dialog as part of the setup-dialog, which would probably improve the visibility of the feature (I know the subscription support in the UI is currently pretty bad, and I'm already working on that). So yeah, if speed and ease of use (= not having to subscribe to ALL folders inside/under the mailbox repository folder) aren't useful then I guess the majority of other readers that do provide a prefix path setting are just plain wrong to do so. No irony intended either (sarcasm and cynicism are a different matter) ... I pretty sure subscriptions do in fact solve the problem. It's entierly possible that the implementation isn't perfect and that it requires some adjustments, but that's the solution then, and not adding yet another workaround. BTW, nothing has been resolved here, so I'm setting a more appropriate status. Please don't. I'm the one that has to deal with the tickets, and it helps noone keeping a tickets open that has been declined already. There is only Resolved and if you set it back to unconfirmed there is no way for me to distinguish it from other tickets that I haven't processed yet. Even if it's set to resolved we can keep the discussion going here if you like. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 337744] New: Subscriptions should be configurable before the first sync
https://bugs.kde.org/show_bug.cgi?id=337744 Bug ID: 337744 Summary: Subscriptions should be configurable before the first sync Product: Akonadi Version: GIT (master) Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: mollek...@kolabsys.com CC: kdepim-bugs@kde.org, vkra...@kde.org Otherwise the sync potentially starts downloading loads of data no one needs. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335795] IMAP namespace support is incomplete/insufficient on large imap accounts
https://bugs.kde.org/show_bug.cgi?id=335795 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|RESOLVED|CLOSED --- Comment #5 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to RJVB from comment #4) Yes, there are 2 things which make (made) the current implementation unworkable for me. Most importantly, the fact that there is no way to obtain the list of folders (not) to subscribe to before the whole account is scanned. (And again, on a typical workstation also running an imapd that amounts to transferring all files under your account, possibly even trying to parse them.) Agreed, it should be possible to make that selection before the sync starts. https://bugs.kde.org/show_bug.cgi?id=337744 The other thing is that there is nothing recursive to a subscription, i.e. there is no way I found to select all mailboxes in the directory where one keeps them. It would be nice if the UI allowed recursive actions indeed. I'm aware the UI side isn't pretty in general, and I plan to improve that. One could argue that that's a once-only action, but in reality that would go against the fact that IMAP has always been designed to allow access from multiple locations (i.e., mailboxes might be created or deleted while connecting from a different location). I don't get that part. Server-side subscriptions are for all devices which you may or may not desire, but we allow to override that setting on a per-folder basis using local subscriptions, which should cover all use-cases, no? Isn't there a closed - wontfix status? Indeed there is, once the status was resolved (it's a workflow thingy I suppose...). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 319776] Akonadi crashed, possibly because of sudden lack of network connection, caused by the laptop going into suspend-to-ram
https://bugs.kde.org/show_bug.cgi?id=319776 --- Comment #21 from Christian Mollekopf mollek...@kolabsys.com --- It crashes in qobject on: const QMetaObject *smeta = sender-metaObject(); so it's indeed the session that is invalid. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 336163] autocompletion shows multiple entries for one contact with different quotes
https://bugs.kde.org/show_bug.cgi?id=336163 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- Note that the problem is not necessarily that multiple entires are shown (as covered by 316036), but rather that entires make it into the selection that are not actually valid email addresses, causing the email to be rejected by the server. One reason is possibly faulty indexing of the addresses, perhaps there are others. In any case it probably would make sense to ensure a selected email address is valid before copying into the mail, or even hiding it completely from the selection. From the rfc excerpt I take a name has to be quoted if it contains spaces, otherwise not. So valid would be: John Doe j...@doe.com John j...@doe.com -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335235] kmail akonadi: imap resource cannot be accessed
https://bugs.kde.org/show_bug.cgi?id=335235 --- Comment #5 from Christian Mollekopf mollek...@kolabsys.com --- I'm aware of the GETACL problem, because we don't respect MYRIGHTS (that's on my todolist already), but I don't understand why we're issuing MYRIGHTS if ACL's are disabled. I assume the CAPABILITIES string doesn't contain ACL? If it does that seems like a server bug. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335235] kmail akonadi: imap resource cannot be accessed
https://bugs.kde.org/show_bug.cgi?id=335235 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- For the Too many invalid IMAP commands. problem we would probably need a imap log. You can find here http://techbase.kde.org/Projects/PIM/Akonadi/Debug_IMAP how to obtain one. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328421] Refactor session related codepaths to use jobs
https://bugs.kde.org/show_bug.cgi?id=328421 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Priority|NOR |LO Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 335776] IMAP agent crashes frequently
https://bugs.kde.org/show_bug.cgi?id=335776 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- Can you check in the debug output if the online state changed just before it crashed? You should see a message in doSetOnline (online=), -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 331703] Auto refresh of the IMAP email accounts no longer works
https://bugs.kde.org/show_bug.cgi?id=331703 --- Comment #7 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #6) What you indicate is definitely different than my issue. But I never saw that all folders were kept in sync instantly. But maybe this is dependent on the email provider. What I see and what I also saw in 4.12 is that kmail retrieves changes on the indicated interval. IDLE is only used on the INBOX, and the interval is used for all folders. The interval is working AFAIK, and IDLE is supposed to pick up flag changes and new mail for INBOX only. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328625] Allow forcing encryption protocol version
https://bugs.kde.org/show_bug.cgi?id=328625 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/32aaf98fd2d7387f |im-runtime/423632618ed30781 |1313cf0d135c82dffa643d9a|7a088ae99607d19f3cce98ed --- Comment #9 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 423632618ed307817a088ae99607d19f3cce98ed by Christian Mollekopf. Committed on 07/05/2014 at 14:20. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Allow to override the encryption mode. Some ssl servers advertise an ssl version they don't actually support. This config-only option allows to override the used encryption mode, and supports all available options, so the auto-negotiation can be skipped. M +3-0resources/imap/imapresource.kcfg M +24 -0resources/imap/settings.cpp http://commits.kde.org/kdepim-runtime/423632618ed307817a088ae99607d19f3cce98ed -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/7f3e279cf79ef8e2 |im-runtime/7802a783189adbe4 |4eb64986d538e0075452b91c|e3e67cd9bb60867c82c36d69 --- Comment #13 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 7802a783189adbe4e3e67cd9bb60867c82c36d69 by Christian Mollekopf. Committed on 05/05/2014 at 21:10. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Check available UID's first retrieve 50 time more flags. This way we avoid the UID fragmentation problem (we try to fetch a lot of messages that are not available on the server). It's also a nice first step towards only syncing a certain time-frame. Retrieving 50 times more flags than full messages should still result in low memory consumption while greatly reducing roundtrips. M +68 -33 resources/imap/retrieveitemstask.cpp M +49 -25 resources/imap/tests/testretrieveitemstask.cpp http://commits.kde.org/kdepim-runtime/7802a783189adbe4e3e67cd9bb60867c82c36d69 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329805] After disabling all local subscriptions and restarting kmail akonadi_imap_resource always crashes
https://bugs.kde.org/show_bug.cgi?id=329805 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/e376267dda6972ff |im-runtime/5e8808a6e2eb7171 |c2eeea215901f08145e3c993|b8aafeeb0f553a8e89ae3a8f --- Comment #4 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 5e8808a6e2eb7171b8aafeeb0f553a8e89ae3a8f by Christian Mollekopf. Committed on 08/05/2014 at 15:18. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Don't crash if IDLE collection is not subscribed locally. M +12 -11 resources/imap/imapresource.cpp http://commits.kde.org/kdepim-runtime/5e8808a6e2eb7171b8aafeeb0f553a8e89ae3a8f -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334218] synchronizations of large folders with filesystem contents hogs a Sandybridge core for minutes
https://bugs.kde.org/show_bug.cgi?id=334218 --- Comment #16 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 1af2704a63c6641867eaf2b67976f5309a994cca by Christian Mollekopf, on behalf of Martin Steigerwald. Committed on 03/05/2014 at 14:52. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. Do not sort the directory entry list in listNew() and listCurrent(): According to callgrind dumps at https://bugs.kde.org/show_bug.cgi?id=334218#c4 QDir sorts the list of directory entries unless specified otherwise. After disabling the sorting the callgrind is quite different already: https://bugs.kde.org/show_bug.cgi?id=334218#c7 This already helps shortening the time to synchronize folders visibly, but KMail gets still blocked for half a minute or more. There is another occurence of QDir entry sorting in keycache.cpp which the next commit will address. Thanks to Sergio and David for help and pointing out how to disable the sorting. REVIEW: 117975 DIGEST: Huge performance improvement for POP3 users with large maildir. M +2-0resources/maildir/libmaildir/maildir.cpp http://commits.kde.org/kdepim-runtime/1af2704a63c6641867eaf2b67976f5309a994cca -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334218] synchronizations of large folders with filesystem contents hogs a Sandybridge core for minutes
https://bugs.kde.org/show_bug.cgi?id=334218 --- Comment #17 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 81f30e18c975f9cc44da7c904ed612df804200da by Christian Mollekopf, on behalf of Martin Steigerwald. Committed on 03/05/2014 at 14:53. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. Also do not sort directory entries in listCurrent and listNew in key cache: QDir sorts the list of directory entries unless specified otherwise. The last commit already disabled the sorting in maildir.cpp. This commit completes the work and makes the remaining sorting calls in the callgrind dumps at https://bugs.kde.org/show_bug.cgi?id=334218#c7 go away completely as demonstrated in the callgrind dumps at: https://bugs.kde.org/show_bug.cgi?id=334218#c12 Subjectively this has a huge impact on the performance of KMail with huge maildir. KMail hardly blocks anymore on folder changes and feels much more responsive now. Akonadi maildir resource went from hogging a Sandy Bridge core for minutes to not appearing using 100% of one core in even one averaged 10 second interval in atop. I hardly see it in atop at all anymore, except when accessing very large folders such as one with Linux Kernel mailing list and more than 245000 unread mails. Thanks to Sergio for pointing out the remaining sorting calls in the second callgrind dump and for help. Now the bottleneck appears to be MaildirResource::listRecursive but I do not know whether further optimization is necessary at this point. Both changes tested with kdepimlibs master as of today and KMail 4.12.4 from Debian unstable packages with an enormous maildir including a folder for Linux Kernel mailing list with more than 245000 unread mails. REVIEW: 117975 DIGEST: Huge performance improvement for POP3 users with large maildirs. M +2-0resources/maildir/libmaildir/keycache.cpp http://commits.kde.org/kdepim-runtime/81f30e18c975f9cc44da7c904ed612df804200da -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334448] imap stuck on Retrieving extra folder information for some folders.
https://bugs.kde.org/show_bug.cgi?id=334448 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/c876ae9e9ea92f2f |im-runtime/9442452028441736 |61d127899272cda3ab478770|6159ea8e358a9e7eb0ee5d5f --- Comment #2 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 94424520284417366159ea8e358a9e7eb0ee5d5f by Christian Mollekopf. Committed on 07/05/2014 at 12:04. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Properly count started and completed jobs. I.e. if no job was started because of no metadata capabilities the job would get stuck otherwise. M +14 -7resources/imap/retrievecollectionmetadatatask.cpp http://commits.kde.org/kdepim-runtime/94424520284417366159ea8e358a9e7eb0ee5d5f -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334269] Email retrieval comes to a full HALT after BatchFetcher::fetchNextBatch: fetchNextBatch called while fetch is in process error
https://bugs.kde.org/show_bug.cgi?id=334269 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |im-runtime/c8763c863111afe9 |im-runtime/0de7f0faef78b570 |9cda997bb9ca7e481d0e5142|b3930ec34f0320de7f2f055b --- Comment #6 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 0de7f0faef78b570b3930ec34f0320de7f2f055b by Christian Mollekopf. Committed on 04/05/2014 at 19:29. Pushed by cmollekopf into branch 'kolab/integration/4.13.0'. IMAP-Resource: Fixed stuck BatchFetcher The continuation request can be delivered while a fetch job is in progress if we deliver too many messages (which is likely with the uid based fetches where we can't predict the exact amount of fetched messages). In this case we need to remember the continuation request, and automatically proceed. This causes m_fetchedItemsInCurrentBatch to be off by the messages we delivered too many, but that's not a problem as it means we just deliver too many messages during every batch. M +11 -1resources/imap/retrieveitemstask.cpp http://commits.kde.org/kdepim-runtime/0de7f0faef78b570b3930ec34f0320de7f2f055b -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329805] After disabling all local subscriptions and restarting kmail akonadi_imap_resource always crashes
https://bugs.kde.org/show_bug.cgi?id=329805 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED Latest Commit||http://commits.kde.org/kdep ||im-runtime/e376267dda6972ff ||c2eeea215901f08145e3c993 --- Comment #3 from Christian Mollekopf chrig...@fastmail.fm --- Git commit e376267dda6972ffc2eeea215901f08145e3c993 by Christian Mollekopf. Committed on 08/05/2014 at 08:42. Pushed by cmollekopf into branch 'KDE/4.13'. IMAP-Resource: Don't crash if IDLE collection is not subscribed locally. M +13 -12 resources/imap/imapresource.cpp http://commits.kde.org/kdepim-runtime/e376267dda6972ffc2eeea215901f08145e3c993 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334448] imap stuck on Retrieving extra folder information for some folders.
https://bugs.kde.org/show_bug.cgi?id=334448 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im-runtime/c876ae9e9ea92f2f ||61d127899272cda3ab478770 --- Comment #1 from Christian Mollekopf chrig...@fastmail.fm --- Git commit c876ae9e9ea92f2f61d127899272cda3ab478770 by Christian Mollekopf. Committed on 07/05/2014 at 12:04. Pushed by cmollekopf into branch 'master'. IMAP-Resource: Properly count started and completed jobs. I.e. if no job was started because of no metadata capabilities the job would get stuck otherwise. M +14 -7resources/imap/retrievecollectionmetadatatask.cpp http://commits.kde.org/kdepim-runtime/c876ae9e9ea92f2f61d127899272cda3ab478770 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328625] Allow forcing encryption protocol version
https://bugs.kde.org/show_bug.cgi?id=328625 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im-runtime/32aaf98fd2d7387f ||1313cf0d135c82dffa643d9a --- Comment #6 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 32aaf98fd2d7387f1313cf0d135c82dffa643d9a by Christian Mollekopf. Committed on 07/05/2014 at 14:20. Pushed by cmollekopf into branch 'KDE/4.13'. IMAP-Resource: Allow to override the encryption mode. Some ssl servers advertise an ssl version they don't actually support. This config-only option allows to override the used encryption mode, and supports all available options, so the auto-negotiation can be skipped. M +3-0resources/imap/imapresource.kcfg M +24 -0resources/imap/settings.cpp http://commits.kde.org/kdepim-runtime/32aaf98fd2d7387f1313cf0d135c82dffa643d9a -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328625] Allow forcing encryption protocol version
https://bugs.kde.org/show_bug.cgi?id=328625 --- Comment #7 from Christian Mollekopf mollek...@kolabsys.com --- The above patch allows to specify the used version in .kde/share/config/akonadi_imap_resource_*rc [network] OverrideEncryption=TLSV1 Valid values are: SSLV2, SSLV3, TLSV1, SSL, STARTTLS, UNENCRYPTED TLSV1 is the same as sslv3.1 and SSL is the autonegotiation. The patch will be part of the 4.13.1 release. Please let me know whether this fixes your problem, and let me know if it doesn't. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329203] Akonadi re-downloading message bodies
https://bugs.kde.org/show_bug.cgi?id=329203 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- This should be resolved in current master. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332018] IMAP: A newly created folder doesn't appear until restart of KMail
https://bugs.kde.org/show_bug.cgi?id=332018 --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- We need to issue synchronizeCollectionTree regularly. KMail also currently lacks the option to manually refresh the collection tree. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329805] After disabling all local subscriptions and restarting kmail akonadi_imap_resource always crashes
https://bugs.kde.org/show_bug.cgi?id=329805 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO CC||mollek...@kolabsys.com Resolution|--- |WAITINGFORINFO --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- I tried reproducing this but failed with current master (4.14). Please reopen if you can reproduce it in 4.14 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334269] Email retrieval comes to a full HALT after BatchFetcher::fetchNextBatch: fetchNextBatch called while fetch is in process error
https://bugs.kde.org/show_bug.cgi?id=334269 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #5 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #4) Do the last changes switch the imap resource to read only while it's refetching ? I'm seeing this kind of messages (not directly related to this commit but also visible with it): akonadi_imap_resource_0(11329) RetrieveItemsTask::onExpungeDone: Expunge failed: Expunge failed, server replied: A09 NO mailbox selected READ-ONLY akonadi_imap_resource_1(11332) RetrieveItemsTask::onExpungeDone: Expunge failed: Expunge failed, server replied: A09 NO mailbox selected READ-ONLY akonadi_imap_resource_0(11329) RetrieveItemsTask::onExpungeDone: Expunge failed: Expunge failed, server replied: A15 NO mailbox selected READ-ONLY akonadi_imap_resource_1(11332) RetrieveItemsTask::onExpungeDone: Expunge failed: Expunge failed, server replied: A15 NO mailbox selected READ-ONLY which disappear if I reroll kdepim-runtime to a commit from before the last changes (server capabilities: IMAP4REV1 ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ESORT I18NLEVEL=1 ID IDLE LIST-EXTENDED LIST-STATUS LITERAL+ LOGIN-REFERRALS MULTIAPPEND NAMESPACE QRESYNC QUOTA RIGHTS=EKTX SASL-IR SEARCHRES SORT THREAD=ORDEREDSUBJECT UIDPLUS UNSELECT WITHIN XLIST ) We used to unconditionally expunge, even if we don't have the rights, and then silently ignore any errors. I changed that to only conditionally expunging if we have the necessary rights and then checking for errors. I checked the akonadi rights though and not the actual IMAP ACL's and apparently the check doesn't work in all cases (I get those too for some shared folders). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im-runtime/7f3e279cf79ef8e2 ||4eb64986d538e0075452b91c --- Comment #11 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 7f3e279cf79ef8e24eb64986d538e0075452b91c by Christian Mollekopf. Committed on 05/05/2014 at 21:10. Pushed by cmollekopf into branch 'master'. IMAP-Resource: Check available UID's first retrieve 50 time more flags. This way we avoid the UID fragmentation problem (we try to fetch a lot of messages that are not available on the server). It's also a nice first step towards only syncing a certain time-frame. Retrieving 50 times more flags than full messages should still result in low memory consumption while greatly reducing roundtrips. M +68 -33 resources/imap/retrieveitemstask.cpp M +49 -25 resources/imap/tests/testretrieveitemstask.cpp http://commits.kde.org/kdepim-runtime/7f3e279cf79ef8e24eb64986d538e0075452b91c -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||mollek...@kolabsys.com Ever confirmed|0 |1 --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- The problem with gmail is that it's CONDSTORE support is broken (I think it was something with the tag folders?), and we therefore have to fetch all flags on every sync. I think the resource simply ignored flag changes previously if there were no new messages. I can readd a similar workaround if CONDSTORE is not available (or broken as on GMAIL). Sorry if I introduced performance problems, but I'm generally preferring correctness over performance, but we can re-add optimizations as necessary. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #5 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #4) (In reply to comment #3) The problem with gmail is that it's CONDSTORE support is broken (I think it was something with the tag folders?), and we therefore have to fetch all flags on every sync. I think the resource simply ignored flag changes But shouldn't this generate network traffic ? Because the flags needs to be retrieved from the server, but during this period I do not see any traffic at all until it reaches the point where it can retrieve some new email. This should generate network traffic indeed. Sorry if I introduced performance problems, but I'm generally preferring correctness over performance, but we can re-add optimizations as necessary. Correctness is fine, but in this world Performance is more important to the users. And it seems that this correctness also creates the situation that the IMAP resource is no longer fast enough and starts blocking itself. (As reported in the other bug). That's just a regular bug that needs to be fixed. I guess that the IMAP resource now has reached a point where its developers should decide what it actually supports. If the requirement is that it needs a correct CONDSTORE, then support for gmail should be dropped. Maybe moving the gmail support to a separate resource would be much better, so that this specific gmail resource can have all the things required to support a broken GMAIL. The IMAP resource supports vanilla IMAP plus extensions as required/useful. If we have to employ certain workarounds in order to make the experience better with servers that don't implement all the necessary extensions, then I'm open to that as long as it doesn't become a maintenance burden. Daniel is already working on a specialized IMAP resource that implements the GMAIL specific extensions, so that will be covered eventually. But I'd still expect the plain IMAP resource to work reasonably well with GMAIL as long as they provide regular IMAP. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334269] Email retrieval comes to a full HALT after BatchFetcher::fetchNextBatch: fetchNextBatch called while fetch is in process error
https://bugs.kde.org/show_bug.cgi?id=334269 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im-runtime/c8763c863111afe9 ||9cda997bb9ca7e481d0e5142 --- Comment #2 from Christian Mollekopf chrig...@fastmail.fm --- Git commit c8763c863111afe99cda997bb9ca7e481d0e5142 by Christian Mollekopf. Committed on 04/05/2014 at 19:29. Pushed by cmollekopf into branch 'master'. IMAP-Resource: Fixed stuck BatchFetcher The continuation request can be delivered while a fetch job is in progress if we deliver too many messages (which is likely with the uid based fetches where we can't predict the exact amount of fetched messages). In this case we need to remember the continuation request, and automatically proceed. This causes m_fetchedItemsInCurrentBatch to be off by the messages we delivered too many, but that's not a problem as it means we just deliver too many messages during every batch. M +11 -1resources/imap/retrieveitemstask.cpp http://commits.kde.org/kdepim-runtime/c8763c863111afe99cda997bb9ca7e481d0e5142 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #7 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #6) (In reply to comment #5) This should generate network traffic indeed. Strangely enough I didn't notice any network traffic during this period. As indicated network traffic is only visible around the end. Please let me know if the situation is improved or still the same with the fix for the other bug. Flag fetching definitely is slower because I'm currently fetching the flags just as messages in batches of 100 to avoid overloading akonadi. This obviously results in many roundtrips, and I suppose the batchsize could be greatly increased for flags (because a lot less data than full messages). That's just a regular bug that needs to be fixed. Ok. Just strange that it seems only to hit the gmail IMAP. It was a timing issue, and it only appeared if the network connection is the bottleneck. Apparently gmail is slow ;-) Daniel is already working on a specialized IMAP resource that implements the GMAIL specific extensions, so that will be covered eventually. That is great news :) I will let him know that he already found a test person for it :) But I'd still expect the plain IMAP resource to work reasonably well with GMAIL as long as they provide regular IMAP. Ok. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 334280] IMAP Synchronisation with GMAIL takes 13 minutes to complete !!
https://bugs.kde.org/show_bug.cgi?id=334280 --- Comment #9 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #8) (In reply to comment #7) (In reply to comment #6) (In reply to comment #5) This should generate network traffic indeed. Strangely enough I didn't notice any network traffic during this period. As indicated network traffic is only visible around the end. Please let me know if the situation is improved or still the same with the fix for the other bug. With the fix for the other bug, the synchronization went back to about 5 minutes and now I see network traffic during the flag retrieval. What exactly does the number mean in this line : akonadi_imap_resource_16(30157)/kdepimlibs (kimap) BatchFetcher::fetchNextBatch: Fetching 257301 to 257400 It means UID's 257301 to 257400 are fetched which only correlates to the number of messages that ever have been in the folder (not to the amount you currently have). Does that mean that I have 257400 emails in that folder ? If so, then something else is wrong. I know that I have a number of high volume email lists (e.g. kde-com...@kde.org), but I am deleting the emails from there every 3 days to reduce the total number of emails. I also cleaned up in gmail.com itself, so I shouldn't have those many emails. Flag fetching definitely is slower because I'm currently fetching the flags just as messages in batches of 100 to avoid overloading akonadi. This obviously results in many roundtrips, and I suppose the batchsize could be greatly increased for flags (because a lot less data than full messages). Can I increase the number somewhere ? Just to test if I can find a better number for my system and to retrieve things a little faster ? In imapresource.cpp (setItemSyncBatchSize) we define the batch size. This directly correlates to the number of messages that are loaded into memory, so I wouldn't make this one too big. In retrieveitemstask.cpp:668 you could increase the passed-in batch-size for flag fetching only. I think it should work if you simply set a multiplier (e.g. 10*batchSize()). It's not configurable in a configfile. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328625] Allow forcing encryption protocol version
https://bugs.kde.org/show_bug.cgi?id=328625 --- Comment #4 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #3) it seems a bit anachronistic to me, for akonadi to only work properly if the mailserver still supports SSLv2. as far as i remember that protocol version was even removed from the openssl packages for debian/ubuntu years ago. so regarding the config file solution i'd vote for this: make akonadi use SSLv3/TLS by default, and if you're really still stuck with SSLv2-only, than *that* would be the thing you'd have to turn on in a config file. That's not what we're doing. We're using the auto-negotiation that apparently is broken on some servers (there's a report somewhere, if only I could find it). This causes the server to report an ssl version it doesn't actually support and thus the connection fails. For this case it's useful to be able to force the used version and thus skipping the broken negotiation. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 333647] after upgrade to 4.13: one of two IMAP resources is reported not functional
https://bugs.kde.org/show_bug.cgi?id=333647 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- (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? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328625] Allow forcing encryption protocol version
https://bugs.kde.org/show_bug.cgi?id=328625 --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- A user just ran into this, so we really should have this config file option. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328625] Allow forcing encryption protocol version
https://bugs.kde.org/show_bug.cgi?id=328625 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 333762] New: Certificate dialog loops
https://bugs.kde.org/show_bug.cgi?id=333762 Bug ID: 333762 Summary: Certificate dialog loops Classification: Unclassified Product: Akonadi Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: mollek...@kolabsys.com CC: kdepim-bugs@kde.org, vkra...@kde.org If you cancel it it reappears, and upon every new connection attempt a new one is opened, potentially leading to a boatload of dialogs. https://bugs.kde.org/show_bug.cgi?id=233628 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745556 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 316106] exchange email account offline at startup
https://bugs.kde.org/show_bug.cgi?id=316106 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #4 from Christian Mollekopf mollek...@kolabsys.com --- Great, thanks for reporting back! -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 309245] The IMAP resource stays offline even when the IMAP server is available again
https://bugs.kde.org/show_bug.cgi?id=309245 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |FIXED --- Comment #13 from Christian Mollekopf mollek...@kolabsys.com --- This should work now in 4.13 (it retries after the specified sync interval, or 5 minutes if set to sync manually). -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332018] IMAP: A newly created folder doesn't appear until restart of KMail
https://bugs.kde.org/show_bug.cgi?id=332018 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||mollek...@kolabsys.com Ever confirmed|0 |1 --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- With 4.13 it doesn't depend on a restart of kmail anymore, but the remotely created folder still didn't get synchronized by the imap resource on the first try. I'll need to investigate that. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 333005] New: Groupware objects should be filtered from search results.
https://bugs.kde.org/show_bug.cgi?id=333005 Bug ID: 333005 Summary: Groupware objects should be filtered from search results. Classification: Unclassified Product: kmail2 Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: search Assignee: kdepim-bugs@kde.org Reporter: mollek...@kolabsys.com CC: m...@vhanda.in Currently groupware objects show up in the results as mail, we should probably hide all results that are in a hidden collection. Reproducible: Always -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 319171] Infinite popup message when imap connection error
https://bugs.kde.org/show_bug.cgi?id=319171 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com --- Comment #13 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #12) Thank you Christian, but is there a way to implement this solution right now? Because this bug really drives me crazy at the moment. Or do I have to wait for the 4.13 release on April 16th? Unfortunately you'll have to wait. But there might be release candidate packages for your distributions, which would also allow you to give me feedback in case you're not yet happy with the solution. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329857] akonadi imap fails if Internet is not ready
https://bugs.kde.org/show_bug.cgi?id=329857 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||imlibs/5d128773819d50278a19 ||4d6a16d5fa36c7e81908 --- Comment #6 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 5d128773819d50278a194d6a16d5fa36c7e81908 by Christian Mollekopf. Committed on 23/03/2014 at 19:00. Pushed by cmollekopf into branch 'KDE/4.13'. Avoid setting the Agent online if it needs network but there is none. Without this patch an agent is online initially and only reacts to subsequent, online status changes. This cause for example the imap resource to go online when started without network connection (resulting in a wrong initial status), and as the imap resource tried to connect and failed, it set itself to offline, resulting in it not reacting to the network becoming available. With this patch all network detection code can be removed from the imap resource and it properly reacts to network changes. REVIEW: 117008 M +9-1akonadi/agentbase.cpp http://commits.kde.org/kdepimlibs/5d128773819d50278a194d6a16d5fa36c7e81908 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 319171] Infinite popup message when imap connection error
https://bugs.kde.org/show_bug.cgi?id=319171 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im-runtime/a13c4655ea54d990 ||2d98d97c11b5e4ba996bbceb --- Comment #11 from Christian Mollekopf chrig...@fastmail.fm --- Git commit a13c4655ea54d9902d98d97c11b5e4ba996bbceb by Christian Mollekopf. Committed on 23/03/2014 at 17:37. Pushed by cmollekopf into branch 'KDE/4.13'. IMAP-Resource: Async dialogs. Async password request dialog that is aborted after disconnecting. This properly aborts the dialog after the connection attempt is no longer relevant, and avoids the stacking of dialogs. The configuration dialog is also made async to avoid similar problems. With this change the dialog appears at most once, and vanishes if the network is disconnected again. Related: bug 306955 M +16 -12 resources/imap/imapresource.cpp M +3-1resources/imap/imapresource.h M +3-0resources/imap/passwordrequesterinterface.cpp M +1-0resources/imap/passwordrequesterinterface.h M +7-0resources/imap/sessionpool.cpp M +1-0resources/imap/sessionpool.h M +69 -20 resources/imap/settingspasswordrequester.cpp M +8-0resources/imap/settingspasswordrequester.h http://commits.kde.org/kdepim-runtime/a13c4655ea54d9902d98d97c11b5e4ba996bbceb -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329857] akonadi imap fails if Internet is not ready
https://bugs.kde.org/show_bug.cgi?id=329857 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Latest Commit|http://commits.kde.org/kdep |http://commits.kde.org/kdep |imlibs/5d128773819d50278a19 |im-runtime/e49c200ba4387a31 |4d6a16d5fa36c7e81908|e997fe24a4a86c8bb8045abc --- Comment #7 from Christian Mollekopf chrig...@fastmail.fm --- Git commit e49c200ba4387a31e997fe24a4a86c8bb8045abc by Christian Mollekopf. Committed on 23/03/2014 at 17:38. Pushed by cmollekopf into branch 'KDE/4.13'. IMAP-Resource: Removed network-change handling With the fixed AgentBase we no longer need to handle network changes. This results in the imap resource correctly reacting to network changes. M +1-13 resources/imap/imapresource.cpp http://commits.kde.org/kdepim-runtime/e49c200ba4387a31e997fe24a4a86c8bb8045abc -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 306955] Akonadi IMAP resource runs amok when using a server with a self-signed certificate
https://bugs.kde.org/show_bug.cgi?id=306955 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im-runtime/a13c4655ea54d990 ||2d98d97c11b5e4ba996bbceb --- Comment #6 from Christian Mollekopf chrig...@fastmail.fm --- Git commit a13c4655ea54d9902d98d97c11b5e4ba996bbceb by Christian Mollekopf. Committed on 23/03/2014 at 17:37. Pushed by cmollekopf into branch 'KDE/4.13'. IMAP-Resource: Async dialogs. Async password request dialog that is aborted after disconnecting. This properly aborts the dialog after the connection attempt is no longer relevant, and avoids the stacking of dialogs. The configuration dialog is also made async to avoid similar problems. With this change the dialog appears at most once, and vanishes if the network is disconnected again. Related: bug 319171 M +16 -12 resources/imap/imapresource.cpp M +3-1resources/imap/imapresource.h M +3-0resources/imap/passwordrequesterinterface.cpp M +1-0resources/imap/passwordrequesterinterface.h M +7-0resources/imap/sessionpool.cpp M +1-0resources/imap/sessionpool.h M +69 -20 resources/imap/settingspasswordrequester.cpp M +8-0resources/imap/settingspasswordrequester.h http://commits.kde.org/kdepim-runtime/a13c4655ea54d9902d98d97c11b5e4ba996bbceb -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 331703] Auto refresh of the IMAP email accounts no longer works
https://bugs.kde.org/show_bug.cgi?id=331703 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |FIXED --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- I think this has been fixed in akonadi 68480a5d0b2e53ad24bc. Please reopen if this is still not working. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.
https://bugs.kde.org/show_bug.cgi?id=332400 --- Comment #3 from Christian Mollekopf mollek...@kolabsys.com --- Unless KTcpSocket reads the data and hides it internally, the IDLE notifications simply never arrive at the client. I checked KTcpSocket's byteAvailable/stat/canReadLine as well as the sockets revc-q with netstat. We still get the idle for too long after 30mins, so the connection seems to be generally ok. As we can see above, it seems as the server sends the idle for too long, the pending notifications also get pushed through. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 327822] The IMAP Resource does not detect namespace changes, but it should
https://bugs.kde.org/show_bug.cgi?id=327822 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 Severity|normal |task -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 328393] The imap resource should notify the user about errors
https://bugs.kde.org/show_bug.cgi?id=328393 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 331678] KMAIL
https://bugs.kde.org/show_bug.cgi?id=331678 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |DUPLICATE --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- *** This bug has been marked as a duplicate of bug 329805 *** -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329805] After disabling all local subscriptions and restarting kmail akonadi_imap_resource always crashes
https://bugs.kde.org/show_bug.cgi?id=329805 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||iraj...@gmail.com --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- *** Bug 331678 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 331948] IMAP folders not automatically updated
https://bugs.kde.org/show_bug.cgi?id=331948 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |DUPLICATE --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- *** This bug has been marked as a duplicate of bug 331703 *** -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 331703] Auto refresh of the IMAP email accounts no longer works
https://bugs.kde.org/show_bug.cgi?id=331703 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||nqn1...@gmail.com --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- *** Bug 331948 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added CC||mollek...@kolabsys.com Component|IMAP resource |server Assignee|chrig...@fastmail.fm|kdepim-bugs@kde.org --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- FYI: Die Datei ist zu gross means The file is too large -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 331848] displaying, moving, deleting mails takes 10-20 seconds when Akonadi synchronizes in background
https://bugs.kde.org/show_bug.cgi?id=331848 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |WAITINGFORINFO --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- Is this still the case with 4.13? I have several mailboxes with 17k+ mails (190k in total), and reading mails is even during synchronization near instant. I know there used to be problems, but for me they seem to be resolved. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 297783] No feedback on IMAP connection problems
https://bugs.kde.org/show_bug.cgi?id=297783 Christian Mollekopf chrig...@fastmail.fm changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||im-runtime/6571fc1924d3ee79 ||84d5d233d2a2cb626f5ca53b --- Comment #2 from Christian Mollekopf chrig...@fastmail.fm --- Git commit 6571fc1924d3ee7984d5d233d2a2cb626f5ca53b by Christian Mollekopf. Committed on 25/03/2014 at 08:08. Pushed by cmollekopf into branch 'KDE/4.13'. IMAP-Resource: cancelTask on error and deferTask on connection error. This way the resource retries if there was a temporary connection problem and reports the problem instead of silently going offline. M +4-3resources/imap/imapresource.cpp http://commits.kde.org/kdepim-runtime/6571fc1924d3ee7984d5d233d2a2cb626f5ca53b -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 331848] displaying, moving, deleting mails takes 10-20 seconds when Akonadi synchronizes in background
https://bugs.kde.org/show_bug.cgi?id=331848 --- Comment #4 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #3) I did not yet see KDE SC 4.13 packages for Debian. I will test with KDE SC 4.13 once packages become available. For now I raised innodb_buffer_pool_size considerably (from the default low 80 MiB to 1024 MiB), but KMail seems to be totally unresponsive here at the moment. Raising the buffer pool size on my laptop from 80 MiB to 256 MiB for a huge POP3 account seems to have helped, but here it does not seem to have any visible effect. Doesn't display a mail for over an hour already. With no significant activity – neither CPU or disk I/O wise – in atop and Akonadiconsole not showing any activity for the IMAP resource either. I am currently using Evolution with EWS plugin which gives much better results. Granted, it doesn't even try to synchronize folders I did not yet click on, but maybe thats a quite sane approach. (Seems to be choosable in configuration.) FWIW, my innodb_buffer_pool_size is 8M and I have no such problems. If there is no cpu nor I/O activity I doubt it's doing anything. I never used pop, so no idea about that one, but maildir for local mail + imap for everything large works fine here. I can only suggest to check if the resource where you try to read mail is actually online and to check what akonadiserver returns using akonadiconsole. The protocol is very IMAP like, so you might be able to figure something out using the debugger in akonadiconsole. -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #7 from Christian Mollekopf mollek...@kolabsys.com --- I think with your home on NFS you're unfortunately in an unsupported situation (at least as far as I'm concerned). I don't have any experience myself with it, but I already heard a couple of times that running this with home on nfs doesn't really work. If this is indeed an NFS related issue, the best you can do is open a wishlist item for NFS support, but I doubt anyone will invest a lot of time in that, or fix it yourself. Sorry about that, but we can only cater so many usecases. I'll leave it up to Daniel to close this as WONTFIX. Let us know though if you think the issue is unrelated to NFS. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332013] on moving a mail: ItemRetrieverException: Unable to retrieve item from resource: NO PartHelperException, unable to open for writing, file too big
https://bugs.kde.org/show_bug.cgi?id=332013 --- Comment #8 from Christian Mollekopf mollek...@kolabsys.com --- Apparently there was some success in the past with mariadb over nfs at least: https://bugs.kde.org/show_bug.cgi?id=275261 (see the last comment) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329857] akonadi imap fails if Internet is not ready
https://bugs.kde.org/show_bug.cgi?id=329857 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED CC||mollek...@kolabsys.com Ever confirmed|0 |1 --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- I just wanted to look into that, till are you already working on it? -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329857] akonadi imap fails if Internet is not ready
https://bugs.kde.org/show_bug.cgi?id=329857 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Assignee|a...@kde.org|mollek...@kolabsys.com -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 329857] akonadi imap fails if Internet is not ready
https://bugs.kde.org/show_bug.cgi?id=329857 --- Comment #4 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #3) I can only say it still happen, imap is showed as disconnected, but i think akonadi google is affected. too. it starts as connected, but it is never updated. Thanks Jup, I can reproduce it and have a patch ready. It's just waiting to be reviewed. It should make it into 4.13 hopefully. Thanks for reporting. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332400] New: IMAP IDLE stops working after some time.
https://bugs.kde.org/show_bug.cgi?id=332400 Bug ID: 332400 Summary: IMAP IDLE stops working after some time. Classification: Unclassified Product: Akonadi Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: mollek...@kolabsys.com CC: kdepim-bugs@kde.org, vkra...@kde.org IDLE works for some time after starting up the resource, but then new events suddenly stop being delivered: C: A08 IDLE S: + idling S: * 3791 EXISTS S: * 0 RECENT S: * 3792 EXISTS S: * 1 RECENT S: * 3793 EXISTS S: * 2 RECENT S: * 3794 EXISTS S: * 2 RECENT Since it doesn't look like the connection is being dropped or anything alike this could be a server bug (I tried with cyrus). Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.
https://bugs.kde.org/show_bug.cgi?id=332400 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Christian Mollekopf mollek...@kolabsys.com --- also netstat shows two open tcp connections to the server, so it must be something else. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 332400] IMAP IDLE stops working after some time.
https://bugs.kde.org/show_bug.cgi?id=332400 --- Comment #2 from Christian Mollekopf mollek...@kolabsys.com --- And then somtime way later: C: A08 IDLE S: + idling S: * 3791 EXISTS S: * 0 RECENT S: * 3792 EXISTS S: * 1 RECENT S: * 3793 EXISTS S: * 2 RECENT S: * 3794 EXISTS S: * 2 RECENT S: * 3795 EXISTS S: * 3 RECENT S: * 3796 EXISTS S: * 4 RECENT S: * 3797 EXISTS X akonadi_imap_resource_0(28523) ImapIdleManager::onStatsReceived: IDLE stats received: KIMAP::IdleJob(0x1402f60) INBOX 3795 3 akonadi_imap_resource_0(28523) ImapIdleManager::onStatsReceived: Cached information: /INBOX 73 3794 2 akonadi_imap_resource_0(28523) ImapIdleManager::onStatsReceived: Resync needed for INBOX 73 akonadi_imap_resource_0(28523) ImapIdleManager::onStatsReceived: IDLE stats received: KIMAP::IdleJob(0x1402f60) INBOX 3796 4 akonadi_imap_resource_0(28523) ImapIdleManager::onStatsReceived: Cached information: /INBOX 73 3795 3 akonadi_imap_resource_0(28523) ImapIdleManager::onStatsReceived: Resync needed for INBOX 73 akonadi_imap_resource_0(28523)/kdepimlibs (kimap) KIMAP::SessionThread::doCloseSocket: close akonadi_imap_resource_0(28523) ImapIdleManager::onIdleStopped: IDLE dropped maybe we should econnect? akonadi_imap_resource_0(28523)/kdepimlibs (kimap) KIMAP::SessionPrivate::responseReceived: Received BYE: idle for too long akonadi_imap_resource_0(28523)/kdepimlibs (kimap) KIMAP::SessionPrivate::responseReceived: Received BYE: Fatal error: Lost connection to select ed backend akonadi_imap_resource_0(28523)/kdepimlibs (kimap) KIMAP::SessionThread::doCloseSocket: close akonadi_imap_resource_0(28523)/kdepimlibs (kimap) KIMAP::SessionThread::doCloseSocket: close akonadi_imap_resource_0(28523)/kdepimlibs (kimap) KIMAP::SessionThread::doCloseSocket: close akonadi_imap_resource_0(28523) ImapIdleManager::reconnect: attempting to reconnect IDLE session akonadi_imap_resource_0(28523) ImapIdleManager::onSessionRequestDone: Starting IDLE connection akonadi_imap_resource_0(28523)/kdepimlibs (kimap) KIMAP::LoginJob::LoginJob: KIMAP::LoginJob(0x18e94f0) akonadi_imap_resource_0(28523)/kdepimlibs (kimap) KIMAP::SessionThread::reconnect: connectToHost imap.mykolab.com 143 -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kdepimlibs] [Bug 327865] Endless fetch loop with favorite collections
https://bugs.kde.org/show_bug.cgi?id=327865 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Component|mail|general Version Fixed In||4.13 b335be0 Resolution|--- |FIXED Product|kontact |kdepimlibs --- Comment #11 from Christian Mollekopf mollek...@kolabsys.com --- This has been fixed for 4.13 in kdepimlibs [b335be0] -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kmail2] [Bug 289476] KMail Hangs When Trying to Load Large IMAP Inbox / Blocks Ability to Send Mail
https://bugs.kde.org/show_bug.cgi?id=289476 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||mollek...@kolabsys.com Resolution|--- |WAITINGFORINFO --- Comment #7 from Christian Mollekopf mollek...@kolabsys.com --- Please reopen if you can still reproduce this in 4.13 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kdepimlibs] [Bug 329004] EntityOrderProxyModel emits layoutChanged on every dataChanged signal
https://bugs.kde.org/show_bug.cgi?id=329004 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 327894] Kmail can not delete emails (imap). Emails are downloaded again after removal.
https://bugs.kde.org/show_bug.cgi?id=327894 --- Comment #17 from Christian Mollekopf mollek...@kolabsys.com --- (In reply to comment #15) I have a problem with exact same symptoms (messages sent to trash appear seconds later as ghosts, have to delete from separate MUA) but have not done quite as deep an investigation. In my case the server is Dovecot and multiple simultaneous connections from different clients works perfectly fine. I'm not sure any other client uses more than one session to the same server at a time except for bulk download. The use of a separate thread for IDLE makes no sense to me, it sounds like whomever set that up didn't quite get the concept. The intended way to use IMAP IDLE, and the way basically everything else that works does it, is you connect, refresh mail, perform whatever user actions have been queued, then call IDLE and you stop. Whenever the connection closes, that means something changes so you repeat the process starting at connect, refresh everything, do queued user-initiated actions, call IDLE, wait. ad naseum. That doesn't resemble anything in RFC 2177. AFAIU IDLE works like this: * the client opens a connection * the client sends IDLE command * the server can now send unsolicited responses for for arriving mail etc. * the client stops the command using DONE We're doing this in a separate session, which should work. Ideally we would be reconnecting every 29mins to keep the server from closing the connection, but currently we simply wait for the server to close the connection and then reopen a new one. Anyways, this probably has nothing to do with the bug at hand. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 306955] Akonadi IMAP resource runs amok when using a server with a self-signed certificate
https://bugs.kde.org/show_bug.cgi?id=306955 Christian Mollekopf mollek...@kolabsys.com changed: What|Removed |Added Version|4.9 |4.11 --- Comment #4 from Christian Mollekopf mollek...@kolabsys.com --- I just reproduced this with an account where the password changed and indeed it spawns a new dialog on every reconnect. I could also trigger it manually by simply reconnecting the wlan or entering sleep. -- You are receiving this mail because: You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
