Bug 353439 - IMAP does not sync, gets stuck at 0% and hangs there
Summary: IMAP does not sync, gets stuck at 0% and hangs there
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR grave
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-02 08:29 UTC by Igilama
Modified: 2018-02-01 09:54 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Igilama 2015-10-02 08:29:30 UTC
Kubuntu Beta 2
KMail 5.0.1
Akonadi 15.08

I just created a new IMAP resource - MS Exchange 2010 and it does not sync a single email, it gets stuck right away at 0%.

Possibly related bug:
https://bugs.kde.org/show_bug.cgi?id=351814

akonadi output is in Additional Information

Server Info:

IMAP4
IMAP4REV1
AUTH=NTLM
AUTH=GSSAPI
AUTH=PLAIN
UIDPLUS
CHILDREN
IDLE
NAMESPACE
LITERAL+

IMAP log is outputting endlessly the following (different UID etc.):
S: * SEARCH
S: A014689 OK SEARCH completed.
C: A014690 UID SEARCH UID 29366001:29368000


Reproducible: Always

Steps to Reproduce:
1. Create an IMAP resource
2. Try to update folder
3. Sync hangs at 0%

Actual Results:  
does not sync

Expected Results:  
should sync

log_kimap: connectToHost "xxx" 143
log_kimap: KIMAP::LoginJob(0x1b01a70)
log_kimap: "StartTls" "A000001"
"The issuer certificate of a locally looked up certificate could not be found"
"No certificates could be verified"
log_kimap: Initial SSL handshake failed. cipher.isNull() is false , cipher.usedBits() is 128 , the socket says: "Unknown error" and the list of SSL errors contains 2 items.
log_kimap: "Capability" "*"
log_kimap: Capabilities updated:  ("IMAP4", "IMAP4rev1", "AUTH=NTLM", "AUTH=GSSAPI", "AUTH=PLAIN", "UIDPLUS", "CHILDREN", "IDLE", "NAMESPACE", "LITERAL+")
log_kimap: "Capability" "A000002"
log_kimap: "Login" "+"
log_kimap: "Login" "A000003"
log_imapresource: Starting retrieval for  "INBOX"
log_kimap: KIMAP::LoginJob(0x1b01a70)
log_kimap: Unhandled response:  * 8736 EXISTS 
log_imapresource: Starting message retrieval. Elapsed(ms):  264
log_imapresource: MessageCount:  8736 Local message count:  0
log_imapresource: UidNext:  141208 Local UidNext:  0
log_imapresource: HighestModSeq:  0 Local HighestModSeq:  0
log_imapresource: Fetching complete mailbox  "INBOX"
akonadiagentbase_log: 8736
8736
Comment 1 Igilama 2015-10-02 08:51:17 UTC
the IMAP log file has 30MB and ~1,000,000 lines already so it doesn't seem like it plans to stop:

[...]
C: A065535 UID SEARCH UID 262128001:262130000
S: * SEARCH
S: A065535 OK SEARCH completed.
C: A000000 UID SEARCH UID 262130001:262132000
S: * SEARCH
S: A000000 OK SEARCH completed.
[...]
Comment 2 Denis Kurz 2017-06-23 20:22:32 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 3 Denis Kurz 2018-02-01 09:54:08 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.