Fri, 10 Apr 2026 16:31:14 +0000 https://bugs.horde.org/ticket/3778 log in when the username contains spaces Hello, The Cyrus Imap server permits usernames (mailboxes) to contain spaces, bu in order to make use of them in the A001 login command, the username has to be quoted. However imp/lib/IMAP/Client.php does not quote the user name and trying to enter IMP with user name X Y and password Z generates the command A001 login X Y Z which obviously has three parameters instead of two. Thefore I would like to ask you to quote the username before passing it to the IMAP-server, e.g. by prepending $username = '"'. $username . '"'; to imp-4.1.1/lib/IMAP/Client.php:login($usrname) (put it on line 470). Sun, 16 Apr 2006 18:47:50 +0000 https://bugs.horde.org/ticket/3778#t19011 Fixed in HEAD and IMP 4.1.2. However, as noted in the comments in the code: We should use a literal string to send the username, but some IMAP servers don't support a literal string request inside of a literal string. Thus, use a quoted string for the username (which should probably be OK since it is very unlikely a username will include a double-quote character). i.e. we should be doing this: a001 LOGIN {3} + OK foo {3} + OK bar but certain IMAP implementations (i.e. up-imapproxy) don't support this: a001 login {e} + go ahead foo {3} a001 NO LOGIN failed Literal string requests MUST (per RFC 3501) be honored inside of a literal string itself. up-imapproxy is broken and needs to be fixed. I am going to send the devs a message and let them know about this. As stated above, this shouldn't be critical because I don't know of a single IMAP server or OS that allows double quotes in a username. But theoretically this is possible. Mon, 17 Apr 2006 15:51:59 +0000 https://bugs.horde.org/ticket/3778#t19026 In the second example, this line: a001 login {e} should obviously read: a001 login {3} Mon, 17 Apr 2006 16:00:15 +0000 https://bugs.horde.org/ticket/3778#t19030