Hi,
(bug dropped in my mailbox)
After sending an e-mail RoundCube attempts to append the e-mail to the Sent folder.
RoundCube (actually, the Iloha library) does not handle the response to the APPEND command correctly, resulting in a properly sent e-mail, and a client timing out.
Example conversation:
a APPEND "Drafts" (\Seen) {555145}
< a NO [OVERQUOTA] Quota exceeded (mailbox for user is full)
RoundCube reads the response line but doesn't parse it.
Attached patch at least fixes the not-parsing-and-client-hanging part, logging the actual response line to the error log. But a proper error message to the user would be better.
Does anybody have any idea if IMAP errors are standardized, and if so, how would I get the message from program/lib/imap.inc back to program/steps/mail/sendmail.inc, to show the user a proper message?
Robin
--- 8< --- detachments --- 8< --- The following attachments have been detached and are available for viewing. http://detached.gigo.com/rc/7d/tCH2Il93/imap-append-error-ha.diff Only click these links if you trust the sender, as well as this message. --- 8< --- detachments --- 8< ---
List info: http://lists.roundcube.net/dev/
Robin Elfrink wrote:
a APPEND "Drafts" (\Seen) {555145}
< a NO [OVERQUOTA] Quota exceeded (mailbox for user is full)
Attached patch at least fixes the not-parsing-and-client-hanging part, logging the actual response line to the error log. But a proper error message to the user would be better.
Does anybody have any idea if IMAP errors are standardized, and if so,
http://tools.ietf.org/html/rfc5530
how would I get the message from program/lib/imap.inc back to program/steps/mail/sendmail.inc, to show the user a proper message?
Currently there's no way. You need to extend imap classes and iil_ParseResult() to handle result code/text.
On Aug 26, 2009, at 6:48 PM, A.L.E.C wrote:
Does anybody have any idea if IMAP errors are standardized, and if
so,
Ah, thanks.
But 'an optional machine-readable response code' is not very useful
i'm afraid.
Robin
List info: http://lists.roundcube.net/dev/
Robin Elfrink wrote:
But 'an optional machine-readable response code' is not very useful i'm afraid.
On servers that support this we can show localized message: "Unable to save message. Quota exceeded" on others: "Unable to save message. Server response: <message returned by server>".