GNOME Bugzilla – Bug 730377
in inbox, no messages are displayed anymore
Last modified: 2014-05-21 20:15:04 UTC
Since the update to 13.12.2 (Debian unstable), Evolution does not display any messages in a IMAP INBOX anymore. This happens only to one (my default) account where (if I remember correctly) the inbox is stored under the path "INBOX" and subdirectories under "INBOX/<dir>". Subdirectories are displayed correctly, the inbox does not say "no messages".
I can confirm this bug, it hit me yesterday when I updated to 13.12.2 (on debian jessie). One of my IMAP accounts is affected, the other one isn't. When I use another client I can still access all the messages in my inbox. I also made sure that evolution is set to "view: all messages". I also noticed that I'm not able to move messages from another folder to my inbox anymore (I wanted to try out if it disappears when I move it there).
Created attachment 276794 [details] imapx debugging output I'll attach the debugging output of CAMEL_DEBUG=imapx:io evolution >& logfile
[Tentatively increasing priority/severity though might turn out as false alarm].
Created attachment 276797 [details] screenshot I'll attach a screenshot of the window showing the "empty" inbox folder
Thanks for a bug report and logs. This looks like bug #728976, thus let's move there. *** This bug has been marked as a duplicate of bug 728976 ***
(In reply to comment #2) > Created an attachment (id=276794) [details] > imapx debugging output > > I'll attach the debugging output of > CAMEL_DEBUG=imapx:io evolution >& logfile Your log ends with > [imapx:B] Data read failed with error 'TLS-Verbindung wurde unerwartet > geschlossen' which might be like "Connection closed unexpectedly". I suspect the problem is that the server rejected the other connection, thus as I mentioned at bug #728976 comment #16: ...maybe the server doesn't like concurrent connections and kicks evolution off, thus go to ~/.config/evolution/sources and search for all .source files with string ConcurrentConnections. You may have there either ConcurrentConnections=5 or ConcurrentConnections=3. Change the value to 1, to disable concurrent connections for now. This change requires restart of evolution-source-registry (or simply relogin to the session). If it is really caused by this, then it might fix it.
Setting ConcurrentConnections=1 did not fix it for me.
Lukas, please move to bug #728976. By the way, do you connect to a courier server too? You can find that out when running evolution as: $ CAMEL_DEBUG=imapx:io evolution lines with CAPABILITY or somewhere there mention Courier, if it is a Courier server.
Milan, yes it is a courier.
This bug was solved as cited below, but it probably not a duplicate of bug 728976. (In reply to comment #24) > I managed to setup a courier server and I can reproduce this behaviour too, on > an Inbox folder. What I missed in nagy's log from the other bug was this: > > [imapx:A] I/O: 'A00012 LSUB "" INBOX' > > [imapx:A] I/O: '* LSUB (\Noselect \HasChildren) "." "INBOX" > > A00012 OK LSUB completed' > > The \Noselect means "do not touch this folder at all". I do not know why > courier returns that flag when it doesn't return it in previous requests, but > anyway, Inbox is a special folder, which should be always available, thus > ignore this flag for Inbox. This happened after my changes to IMAPx to check > for subscribed folders in all namespaces, it seems. > > Created commit 8877374 in eds master (3.13.2+) > Created commit b8922e4 in eds evolution-data-server-3-12 (3.12.3+) > > [1] https://git.gnome.org/browse/evolution-data-server/commit/?id=8877374