Error numbers vs. human-readable text

[Dan White]

On 07/08/11 13:20 +0200, Frank Elsner wrote:
>[root at mailbackend-a /]# telnet localhost 143
>Trying 127.0.0.1...
>Connected to localhost.
>Escape character is '^]'.
>* OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID MUPDATE=mupdate://mupdate-febe.intern.tu-berlin.de/ AUTH=DIGEST-MD5 SASL-IR] mailcluster2.intern.tu-berlin.de Cyrus IMAP4 (Murder) v2.3.11 server ready
>. logout
>* BYE LOGOUT received
>. OK Completed                                  <--- This looks OK
>Connection to localhost closed by foreign host.
>[root at mailbackend-a /]#
>
>[elsnccpa at mailbackend-2 ~]$ telnet localhost 143
>Trying 127.0.0.1...
>Connected to localhost.
>Escape character is '^]'.
>* OK [CAPABILITY IMAP4 IMAP4rev1 LITERAL+ ID MUPDATE=mupdate://mupdate-febe.intern.tu-berlin.de/ AUTH=DIGEST-MD5 SASL-IR COMPRESS=DEFLATE] mailbackend-2-febe.intern.tu-berlin.de Cyrus IMAP Murder v2.3.16 server ready
>. logout
>* BYE Unknown code imap 54
>. OK Unknown code imap 55                       <--- This is ugly
>Connection to localhost closed by foreign host.
>[elsnccpa at mailbackend-2 ~]$
>
>What might be the error in compilation or install that prevents correct mapping
>to the human-readable text?

Most likely something went wrong during configure/compile time. compile_et
should have generated imap/imap_err.c and imap/imap_err.h, from
imap/imap_err.et, which contains the response messages.

You may need to specify an explicit path to compile_et with:

--with-com_err=PATH

when configuring.

-- 
Dan White