- Previous message: Sebastian Langenhorst: "Cyrus IMAPd 2.3.12p2 - Unknown code 54?"
- In reply to: Sebastian Langenhorst: "Cyrus IMAPd 2.3.12p2 - Unknown code 54?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: Wesley Craig (no email)
Date: Thu Jun 19 2008 - 11:42:15 EDT
On 19 Jun 2008, at 12:08, Sebastian Langenhorst wrote:
> C: E00001 CAPABILITY
> S: * CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID MUPDATE=mupdate://
> mupdate/ STARTTLS AUTH=PLAIN AUTH=GSSAPI SASL-IR ACL RIGHTS=kxte
> QUOTA MAILBOX-REFERRALS NAMESPACE UIDPLUS NO_ATOMIC_RENAME UNSELECT
> CHILDREN MULTIAPPEND BINARY SORT SORT=MODSEQ THREAD=ORDEREDSUBJECT
> THREAD=REFERENCES ANNOTATEMORE CATENATE CONDSTORE SCAN IDLE URLAUTH
> S: E00001 OK Unknown code 54
Examining .../imap/imapd.c cmd_capability(), you see that this
message is produced with this line:
prot_printf(imapd_out, "\r\n%s OK %s\r\n", tag,
error_message(IMAP_OK_COMPLETED));
The "Unknown code 54" is returned by error_message
(IMAP_OK_COMPLETED). IMAP_OK_COMPLETED is "defined" in .../imap/
imap_err.et, which ought to be processed during build time to
produce .../imap/imap_err.c and imap_err.h. These .et files are
intended to be used as part of the com_err package. configure.ac
attempts to use the com_err supplied with the system, if there is
one. Did you build Cyrus IMAPd on this platform? Please examine the
configure log, to see where it's getting com_err et al.
:wes
|
|
|