Roundcube 1.0.3.0 with Xeams IMAP - can't mark messages

[jellex]

Hi all,
I think this is a typical Xeams IMAP backend (implementation) problem, but I'm asking here because I want to troubleshoot the problem and hope to find some help here.

The problem is that no webfrontends will work with Xeams IMAP. I've tried both Roundcube and RainLoop. Connecting the IMAP server works great, but marking messages (\Answered \Flagged \Deleted \Seen \Draft) doesn't work. Roundcube gives me the error "Can't mark message(s)".
FYI some Roundcube logs: http://pastebin.com/cW4dXFG2

The strange thing is that this happens only with webfrontends (Roundcube) using the Xeams IMAP. Using desktop (or android) clients like Thunderbird, Evolution, Aquamail, etc DO work with marking messages. I'm also sure the folders and files have the right permissions.

My question is: Can anybody give me a hint where to look for solving the problem? Where can this go wrong and why is it Roundcube that can't mark messages? What's the difference between Roundcube and a mail-desktop-client? Thanks!

I've also tested the backend with a telnet on 143 session. The outcome is that everything seems to work, but not marking messages:

# telnet xeams.domain.com 143 Trying 123.456.789.0... Connected to xeams.domain.com. Escape character is '^]'. * OK Synametrics IMAP4rev1 server ready 11/21/14 6:53 PM

a login [email protected] P4ssW0rd
a OK LOGIN completed

a capability
* CAPABILITY IMAP4rev1
a OK CAPABILITY completed
a LIST "" "*"
* LIST () "/" "Inbox"
* LIST () "/" "Junk"
* LIST () "/" "PossibleJunk"
* LIST () "/" "Sent"
* LIST () "/" "Drafts"
* LIST () "/" "Trash"
* LIST () "/" "Archive"
a OK LIST completed

a STATUS INBOX (MESSAGES)
* STATUS "INBOX" (MESSAGES 7)
a OK STATUS COMPLETED

a STATUS INBOX (MESSAGES UNSEEN RECENT)
* STATUS "INBOX" (MESSAGES 7 UNSEEN 5 RECENT 0)
a OK STATUS COMPLETED

a SELECT INBOX
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* 6 EXISTS
* OK [UIDVALIDITY 10] UID validity status
* OK [UIDNEXT 8] Predicted next UID
* 0 RECENT
* OK [PERMENENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
a OK [READ-WRITE] SELECT completed

a fetch 1:* flags
* 1 FETCH (flags (\Seen))
* 2 FETCH (flags (\Seen))
* 3 FETCH (flags ())
* 4 FETCH (flags ())
* 5 FETCH (flags ())
* 6 FETCH (flags ())
a OK FETCH completed

a fetch 1:* INTERNALDATE
* 1 FETCH (INTERNALDATE "Tue, 18 Nov 2014 21:45:08 +0100 (CET)")
* 2 FETCH (INTERNALDATE "Tue, 18 Nov 2014 21:47:19 +0100 (CET)")
* 3 FETCH (INTERNALDATE "Tue, 18 Nov 2014 21:45:08 +0100 (CET)")
* 4 FETCH (INTERNALDATE "Tue, 18 Nov 2014 21:47:19 +0100 (CET)")
* 5 FETCH (INTERNALDATE "Tue, 18 Nov 2014 21:45:08 +0100 (CET)")
* 6 FETCH (INTERNALDATE "Tue, 18 Nov 2014 21:47:19 +0100 (CET)")
a OK FETCH completed

a store 1:* +flags seen
[NO OUTPUT, TELNET session 'hangs'...]

[JohnDoh]

This sounds like an IMAP server problem rather than Roundcube. The fact that it does not respond right over telnet is key. Out of interest when you mark a message in a desktop client like Thunderbird do those changes show up in other clients? I would guess that Thunderbird is appling the changes to its offline versions of your emails and nothing else. You could turn on imap_debug in your Roundcube config and then check the log to see the conversation with your server.

[jellex]

Hi,
Late response, sorry, didn't notice your reply.

I still haven't got it to work yet. Have enables imap_debug which outputs the following trying to mark 'testmail' as UNREAD.
All seems okay I guess. Just can't figure out what's happening... 
When I try to mark it UNREAD, Roundcube gives me a message "Can't mark message(s)". This is generated by Roundcube so there must be a way to see why Roundcube gives the error or not?

Also, when I mark a message in my Android mailapp, it does show up in Roundcube, so it must be changing the flags in the IMAP folder itself.

Any help would be appreciated. Thanks.

==> RoundCube/logs/imap <==
[18-Dec-2014 22:51:19 +0000]: [86E7] S: * OK Synametrics IMAP4rev1 server ready 12/18/14 11:51 PM
[18-Dec-2014 22:51:19 +0000]: [86E7] C: A0001 CAPABILITY
[18-Dec-2014 22:51:19 +0000]: [86E7] S: * CAPABILITY IMAP4rev1
[18-Dec-2014 22:51:19 +0000]: [86E7] S: A0001 OK CAPABILITY completed
[18-Dec-2014 22:51:19 +0000]: [86E7] C: A0002 LOGIN ****** [24]
[18-Dec-2014 22:51:19 +0000]: [86E7] S: A0002 OK LOGIN completed
[18-Dec-2014 22:51:19 +0000]: [86E7] C: A0003 SELECT INBOX
[18-Dec-2014 22:51:19 +0000]: [86E7] S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
[18-Dec-2014 22:51:19 +0000]: [86E7] S: * 1 EXISTS
[18-Dec-2014 22:51:19 +0000]: [86E7] S: * OK [UIDVALIDITY 14] UID validity status
[18-Dec-2014 22:51:19 +0000]: [86E7] S: * OK [UIDNEXT 2] Predicted next UID
[18-Dec-2014 22:51:19 +0000]: [86E7] S: * 0 RECENT
[18-Dec-2014 22:51:19 +0000]: [86E7] S: * OK [PERMENENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]
[18-Dec-2014 22:51:19 +0000]: [86E7] S: A0003 OK [READ-WRITE] SELECT completed
[18-Dec-2014 22:51:19 +0000]: [86E7] C: A0004 LOGOUT
[18-Dec-2014 22:51:19 +0000]: [86E7] S: * BYE IMAP4rev1 Server logging out
[18-Dec-2014 22:51:19 +0000]: [86E7] S: A0004 OK LOGOUT completed
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * OK Synametrics IMAP4rev1 server ready 12/18/14 11:51 PM
[18-Dec-2014 22:51:19 +0000]: [B8F2] C: A0001 CAPABILITY
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * CAPABILITY IMAP4rev1
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: A0001 OK CAPABILITY completed
[18-Dec-2014 22:51:19 +0000]: [B8F2] C: A0002 LOGIN ****** [24]
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: A0002 OK LOGIN completed
[18-Dec-2014 22:51:19 +0000]: [B8F2] C: A0003 STATUS INBOX (MESSAGES UNSEEN)
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * STATUS "INBOX" (MESSAGES 1 UNSEEN 0)
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: A0003 OK STATUS COMPLETED
[18-Dec-2014 22:51:19 +0000]: [B8F2] C: A0004 SELECT INBOX
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * 1 EXISTS
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * OK [UIDVALIDITY 14] UID validity status
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * OK [UIDNEXT 2] Predicted next UID
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * 0 RECENT
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * OK [PERMENENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)]

==> RoundCube/logs/imap <==
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: A0004 OK [READ-WRITE] SELECT completed
[18-Dec-2014 22:51:19 +0000]: [B8F2] C: A0005 UID SEARCH 1
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * SEARCH 1
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: A0005 OK SEARCH completed
[18-Dec-2014 22:51:19 +0000]: [B8F2] C: A0006 UID SEARCH ALL
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * SEARCH 1
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: A0006 OK SEARCH completed
[18-Dec-2014 22:51:19 +0000]: [B8F2] C: A0007 UID FETCH 1 (UID RFC822.SIZE FLAGS INTERNALDATE BODY.PEEK[HEADER.FIELDS (DATE FROM TO SUBJECT CONTENT-TYPE CC REPLY-TO LIST-POST DISPOSITION-NOTIFICATION-TO X-PRIORITY)])
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * 1 FETCH (UID 1 RFC822.SIZE 569 FLAGS (\Seen) INTERNALDATE "Thu, 11 Dec 2014 22:16:33 +0100 (CET)" BODY[HEADER.FIELDS ("DATE" "FROM" "TO" "SUBJECT" "CONTENT-TYPE" "CC" "REPLY-TO" "LIST-POST" "DISPOSITION-NOTIFICATION-TO" "X-PRIORITY")] {181}
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: DATE: Thu, 11 Dec 2014 22:16:32 +0100
FROM: User Lastname <[email protected]>
TO: [email protected]
SUBJECT: testmail
CONTENT-TYPE: text/plain; charset=US-ASCII;
format=flowed

[18-Dec-2014 22:51:19 +0000]: [B8F2] S: )
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: A0007 OK UID FETCH completed
[18-Dec-2014 22:51:19 +0000]: [B8F2] C: A0008 LOGOUT
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: * BYE IMAP4rev1 Server logging out
[18-Dec-2014 22:51:19 +0000]: [B8F2] S: A0008 OK LOGOUT completed

[alec]

Nothing wrong in that log, except that I don't see STORE command. Is it from the moment when you mark the message as read?

[jellex]

Yes, it starts and ends with only logs from marking the message as read.
Roundcube immediately gives me the error message as in attachment which reads:
"There is an error! Can't mark message(s)."

The STORE command? Is this something I can report to the Xeams devs (to fix)?

Thanks.