Problems with IMAP4S LOGIN command

TOPdesk Systeembeheer ([email protected]) <[email protected]>
Newsgroups gmane.mail.perdition.user
Message-ID <[email protected]>
Hi everybody,

Since an upgrade to our backend IMAPS server (Zarafa 6.20.7), we have some trouble authenticating via our perdition IMAP4S proxy (version 1.17-7etch1). I've enabled debug and connection logging, and I see that the LOGIN command is splitted in 3 lines instead of sending the whole command in one. Is that normal? Can I configure it somewhere?

Here is the log I get:

Jul  2 14:33:45 floor perdition[9781]: Connect: xx.xx.xx.xx -> [IP proxy]
Jul  2 14:33:45 floor perdition[9781]: SSL connection using AES128-SHA
Jul  2 14:33:45 floor perdition[9781]: SELF:   "* OK IMAP4 Ready floor 0001d839\r\n"
Jul  2 14:33:46 floor perdition[9781]: CLIENT: "1.584 CAPABILITY\r\n"
Jul  2 14:33:46 floor perdition[9781]: SELF:   "* CAPABILITY IMAP4 IMAP4REV1\r\n"
Jul  2 14:33:46 floor perdition[9781]: SELF:   "1.584 OK CAPABILITY\r\n"
Jul  2 14:33:46 floor perdition[9781]: CLIENT: "2.584 LOGIN piekjepuk 6012417\r\n"
Jul  2 14:33:46 floor perdition[9781]: username_add_domain: username_add_domain 0 1 0x807bd1c
Jul  2 14:33:46 floor perdition[9781]: getserver: do_dbserver_get
Jul  2 14:33:46 floor perdition[9781]: SSL connection using AES256-SHA
Jul  2 14:33:46 floor perdition[9781]: REAL:   "* OK Zarafa IMAP gateway ready\r\n"
Jul  2 14:33:46 floor perdition[9781]: SELF:   "flim07 CAPABILITY\r\n"
Jul  2 14:33:46 floor perdition[9781]: REAL:   "* CAPABILITY IMAP4rev1 CHILDREN XAOL-OPTION IDLE\r\n"
Jul  2 14:33:46 floor perdition[9781]: REAL:   "flim07 OK CAPABILITY Completed\r\n"
Jul  2 14:33:46 floor perdition[9781]: SELF:   "flim08 LOGIN {6}\r\n"
Jul  2 14:33:46 floor perdition[9781]: REAL:   "flim08 BAD LOGIN must have 2 arguments\r\n"
Jul  2 14:33:46 floor perdition[9781]: imap4_out_response: invalid tag from server 1
Jul  2 14:33:46 floor perdition[9781]: imap4_out_authenticate: imap4_out_response login
Jul  2 14:33:46 floor perdition[9781]: SELF:   "piekjepuk {7}\r\n"
Jul  2 14:33:46 floor perdition[9781]: REAL:   "piekjepuk BAD Command not recognized\r\n"
Jul  2 14:33:46 floor perdition[9781]: imap4_out_response: invalid tag from server 1
Jul  2 14:33:46 floor perdition[9781]: imap4_out_authenticate: imap4_out_response name
Jul  2 14:33:46 floor perdition[9781]: SELF:   "6012417\r\n"
Jul  2 14:33:46 floor perdition[9781]: REAL:   "* BAD Command not recognized\r\n"
Jul  2 14:33:46 floor perdition[9781]: SELF:   "* BAD Command not recognized\r\n"
Jul  2 14:34:46 floor perdition[9781]: REAL:   "* BYE Connection closed because of timeout\r\n"
Jul  2 14:34:46 floor perdition[9781]: SELF:   "* BYE Connection closed because of timeout\r\n"
Jul  2 14:34:46 floor perdition[9781]: REAL:   ""
Jul  2 14:34:46 floor perdition[9781]: token_read: token_fill_buffer
Jul  2 14:34:46 floor perdition[9781]: read_line: token_read
Jul  2 14:34:46 floor perdition[9781]: imap4_out_response: read_line
Jul  2 14:34:46 floor perdition[9781]: imap4_out_authenticate: imap4_out_response passwd
Jul  2 14:34:46 floor perdition[9781]: main: protocol->out_authenticate -1
Jul  2 14:34:46 floor perdition[9781]: Fatal error authenticating user. Exiting child.

Any ideas? Thank you very much in advance!

Best regards,

--
Xesc

______________________________________________
Perdition-users mailing list
[email protected]
http://lists.vergenet.net/listinfo/perdition-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.