Roundcube Community Forum

 

Solved: Error message Unable to send command: A0005 FETCH 1:*

Started by dubbelklik, May 28, 2015, 05:03:44 PM

Previous topic - Next topic

dubbelklik

Today for one of my mailboxes RoundCube started to give an error while loading the list of emails (the unread counter is correct). Other mailboxes work fine with this installation.

This message is shown in RoundCube:
Server error: Unable to send command: A0005 FETCH 1:* (UID FLAGS BODY.PEEK[HEADER.FIELDS (SUBJECT)])

It is running on a Synology NAS DS 213 DSM 5.0 using Dovecot 1.2.0 and RoundCube 1.0.2.
In /var/log/dovecot you see the entry dovecot: May 28 22:59:19 Error: child 16875 (imap) killed with signal 11.

In the logs-directory of RoundCube no errors or log entries are to be found.

When I open the mailbox with Mozilla Thunderbird or MS Outlook 2010 the e-mail are loaded successfully and are accessible.

Can anybody tell me what is wrong?

dubbelklik

The message has changed to Server error: Unable to send command: A0006 FETCH 1:* (UID FLAGS BODY.PEEK[HEADER.FIELDS (SUBJECT)]).

The log of imap_debug is below


28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready.
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] C: A0001 ID ("name" "Roundcube" "version" "1.1.1" "php" "5.5.13" "os" "Linux" "command" "/roundcube/?_task=m$
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * ID NIL
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: A0001 OK ID completed.
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] C: A0002 AUTHENTICATE PLAIN ****** [49]
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: A0002 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES MULTIAPP$
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] C: A0003 SELECT Sent
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent $Forwarded NonJunk)
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $MDNSent $Forwarded NonJunk \*)] Flags per$
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * 2877 EXISTS
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * 0 RECENT
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * OK [UIDVALIDITY 1366742865] UIDs valid
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * OK [UIDNEXT 2881] Predicted next UID
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * OK [HIGHESTMODSEQ 2953]
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: A0003 OK [READ-WRITE] Select completed.
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] C: A0004 UID SEARCH RETURN (COUNT MAX) ALL UNDELETED
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: * ESEARCH (TAG "A0004") UID MAX 2880 COUNT 2877
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] S: A0004 OK Search completed (0.004 secs).
[28-May-2015 23:12:18 +0200]: <mtos5du8> [5388] C: A0005 UID SORT (SUBJECT) US-ASCII ALL UNDELETED

alec

It looks like sorting by subject fails (or takes too long) on your mailbox. Change the sorting and you'll be fine.

dubbelklik

You are completely right: I feel stupid I didn't see it. The sorting is back on date and everything is fine.
Thank you for the quick repsonse.