Bug 399811 - imap (dovecot) is no longer accessible
Summary: imap (dovecot) is no longer accessible
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 5.7.3
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-14 19:58 UTC by Ivan S. J.
Modified: 2023-02-18 14:40 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 Ivan S. J. 2018-10-14 19:58:28 UTC
SUMMARY
kmail 5.7.3 cannot access IMAP folders anymore. kmail 4.11.15 and 4.14 can.
Symptom is no new emails arrive and system log fills up with:

---snip---
Oct 14 21:36:09 isjsys4.i1.dk akonadi_imap_resource[4026]: org.kde.pim.imapresource: Session login cancelled
Oct 14 21:36:09 isjsys4.i1.dk akonadi_imap_resource[4026]: org.kde.pim.kimap: Connection to server lost  4
Oct 14 21:36:09 isjsys4.i1.dk akonadi_imap_resource[4026]: org.kde.pim.imapresource: Session login cancelled
Oct 14 21:36:10 isjsys4.i1.dk akonadi_imap_resource[4026]: org.kde.pim.kimap: Connection to server lost  4
Oct 14 21:36:10 isjsys4.i1.dk akonadi_imap_resource[4026]: org.kde.pim.imapresource: Session login cancelled
Oct 14 21:36:10 isjsys4.i1.dk akonadi_imap_resource[4026]: org.kde.pim.kimap: Connection to server lost  4
---snip---

IMAP server is dovecot 2.1.7

I have tried to remove .config/akonadi* and .local/share/akonadi* and *kmail* and reconfiguring; Changing from imaps (port 993) to plain imap (port 143); Restarting akonadi with akonadictl. Same result.

STEPS TO REPRODUCE
1. Use dovecot 2.1.7
2. Configure IMAP account as usual
3. (no profit)

OBSERVED RESULT
IMAP folder doesn't appear. Status in settings->configure accounts flashes rapidly between ready/offline.

EXPECTED RESULT
That the IMAP folder would work.

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: ?
KDE Frameworks Version: 5.45.0
Qt Version: 5.9.4

ADDITIONAL INFORMATION
Comment 1 Christophe Marin 2018-10-14 20:33:05 UTC
5.7.3 is quite old. Please retry after installing (at least) KDE Applications 18.04.3.
Comment 2 Ivan S. J. 2018-10-14 21:30:25 UTC
Correction: The "About kmail" dialog says 5.7.3, but rpm -q says kmail-17.12.3. It's the newest available in opensuse leap 15.0/15.1
Comment 3 Christoph Feck 2018-10-15 02:19:54 UTC
You can install newer versions of KDE software on openSUSE Leap via KDE backport repositories. Please ask for help in a forum of your distribution how to add them.
Comment 4 Mara G. 2018-10-16 19:37:46 UTC
I have the same (or a very similar) problem since upgrading to 18.08.1 on Debian unstable a few days ago. Connections to three different IMAP accounts fail silently (The account simply goes offline after a while).

Debug output with QT_LOGGING_RULES="org.kde.pim.* = true" says:

...
org.kde.pim.kimap: close
org.kde.pim.kimap: Connection to server lost  0
org.kde.pim.imapresource: Session login cancelled
org.kde.pim.kimap: KIMAP::LoginJob(0x56521befc090)
...

Trying to debug the imap session via KIMAP_LOGFILE only results in lots of empty logfiles.

One of the servers is dovecot 2.2.13, the only message in the server log is:

...
Oct 16 20:48:14 X dovecot: imap-login: Disconnected (no auth attempts in 3 secs): user=<>, rip=77.177.x.x, lip=188.40.x.x, TLS handshaking: Disconnected, session=<f1UF/1x4hABNsS2y>
Oct 16 20:48:51 X dovecot: imap-login: Disconnected (no auth attempts in 30 secs): user=<>, rip=77.177.x.x, lip=188.40.x.x, TLS handshaking: Disconnected, session=<njE4AV14iABNsS2y>
Oct 16 20:48:54 X dovecot: imap-login: Disconnected (no auth attempts in 3 secs): user=<>, rip=77.177.x.x, lip=188.40.x.x, TLS handshaking: Disconnected, session=<YKFjAV14pABNsS2y>
...


Version: 5.9.1
KDE Frameworks 5.49.0
Qt 5.11.1
Comment 5 Ivan S. J. 2018-10-16 22:32:57 UTC
I tried installing Opensuse tumbleweed in a virtual machine. It has kmail-18.08.1. It works.
I then tried installing Opensuse 15.0 in a virtual machine. It has kmail-17.12.3. That surprisingly worked. This is the same version as I have on my laptop where it doesn't work. I'm fairly sure the last time kmail worked on my laptop it was kmail-4.14.10 (opensuse 42.2).

So I suspect it is something in the configuration or cache files that causes akonadi-imap to malfunction. Which configuration files might that be? Any directions on how to obtain useful debug log?

@Mara: Is there any way for you to install 18.08.1/debian in a virtual machine (or 100% clean&fresh user account) and check if that works? (so we can determine if we have the same problem).
Comment 6 Mara G. 2018-10-17 16:56:44 UTC
Same problem with a new user. I probably won't be able to try a new install until sometime next week.
Comment 7 Ivan S. J. 2018-12-02 22:29:35 UTC
I upgraded a machine to Opensue leap 15.0 with kmail 5.7.3 (rpm: kmail-17.12.3-lp150.1.2.x86_64).
I backed up a user account. Then deleted the user and created the user again. I then restored the .config directory and only that.
Result: kmail invoked kwallet, which I had to create anew (I chose traditional blowfish), and kmail could access the IMAP server without any noticeable problems.

So whatever prevents my laptop-kmail from using imap is probably not something in .config
Comment 8 Justin Zobel 2023-01-19 00:19:07 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 9 Bug Janitor Service 2023-02-03 05:01:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Bug Janitor Service 2023-02-18 03:47:34 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 11 Ivan S. J. 2023-02-18 14:40:07 UTC
I don't have the laptop with the problem anymore, so I cannot recreate the problem. So closing this case is fine.

I did find the lack of debugging information in kmail frustrating. All I could get out of the logs was "it doesn't work but I won't tell you why or any diagnostics codes or messages"