Fri, 10 Apr 2026 09:04:32 +0000 https://bugs.horde.org/ticket/7229 Login will fail if using a password with } character Currently authenticating with IMP against an LDAP server For some reasons ; one user could never log in... I had no idea why as all users are connecting fine ; it only fails with that account. After experimenting ; I found out that the issue only occurs if the password contains the } character. The password was: Voelc7Ods} If you remove the } in the password ; then you can log in okay When running imp/test.php it shows the error: Attempting to automatically determine the correct connection parameters for your server: * Trying protocol imap/notls, Port 143: ERROR - The server returned the following error message: Server disables LOGIN, no recognized SASL authenticator * Trying protocol imap/ssl, Port 993: ERROR - The server returned the following error message: Certificate failure for mail.hydrix.com: unable to get local issuer certificate: /C=AU/O=*.hydrix.com/OU=GT81237634/OU=See www.rapidssl.com/resources/cps (c)08/OU=Domain Control Validated - RapidSSL(R)/CN=*.hydrix.com * Trying protocol imap/ssl/novalidate-cert, Port 993: ERROR - The server returned the following error message: Error in IMAP command received by server.Error in IMAP command received by server.Error in IMAP command received by server.Too many login failures * Trying protocol imap/tls/novalidate-cert, Port 143: ERROR - The server returned the following error message: Error in IMAP command received by server.Error in IMAP command received by server.Error in IMAP command received by server.Too many login failures Could not determine a successful connection protocol. Make sure your mail server is running and you have specified the correct port. Sat, 23 Aug 2008 07:14:25 +0000 https://bugs.horde.org/ticket/7229#t48384 IMP is an IMAP client - what do you mean you're using it against an LDAP server? Mon, 25 Aug 2008 00:01:52 +0000 https://bugs.horde.org/ticket/7229#t48406 > IMP is an IMAP client - what do you mean you're using it against an > LDAP server? My mistake... It's currently set-up as: IMP -> courier-imap (IMAPS/993) -> LDAP (for authentication). Other clients have no problem authenticating with IMAP (outlook, thunderbird, apple mail).. Just IMP will fail when the password contains a } character Mon, 25 Aug 2008 00:42:04 +0000 https://bugs.horde.org/ticket/7229#t48407 Seems that the issue doesn't occur of the '{' isn't located at the end of the password. Mon, 25 Aug 2008 01:51:26 +0000 https://bugs.horde.org/ticket/7229#t48408 Works fine for me - having a '}' in the password. Note that '{' is an invalid character for an IMAP password. Mon, 25 Aug 2008 05:56:13 +0000 https://bugs.horde.org/ticket/7229#t48411 > Works fine for me - having a '}' in the password. Note that '{' is > an invalid character for an IMAP password. Did you try with the password I provided ? Voelc7Ods} Mon, 25 Aug 2008 06:30:31 +0000 https://bugs.horde.org/ticket/7229#t48412 > Did you try with the password I provided ? > Voelc7Ods} Yes. Most likely your IMAP server is broken unless someone else can reproduce this. Mon, 25 Aug 2008 16:52:03 +0000 https://bugs.horde.org/ticket/7229#t48442 > Yes. Most likely your IMAP server is broken unless someone else can > reproduce this. This only happens with IMP all other clients work fine Mon, 25 Aug 2008 21:31:49 +0000 https://bugs.horde.org/ticket/7229#t48451 > This only happens with IMP all other clients work fine So what? What does this prove? Mon, 25 Aug 2008 22:00:51 +0000 https://bugs.horde.org/ticket/7229#t48453 > So what? What does this prove? that the issue only happens with IMP obviously Mon, 25 Aug 2008 22:13:13 +0000 https://bugs.horde.org/ticket/7229#t48454 >> So what? What does this prove? > that the issue only happens with IMP obviously No it doesn't. We send login information differently than other MUA's (using the {} notatic). However, different does not mean broken. See RFC 3501 [4.3]. So, unless you can show otherwise, the assumption is that *your* IMAP server is broken since nobody else can reproduce this issue. Mon, 25 Aug 2008 22:37:26 +0000 https://bugs.horde.org/ticket/7229#t48455 For easy reference: A string is in one of two forms: either literal or quoted string. The literal form is the general form of string. The quoted string form is an alternative that avoids the overhead of processing a literal at the cost of limitations of characters which may be used. A literal is a sequence of zero or more octets (including CR and LF), prefix-quoted with an octet count in the form of an open brace ("{"), the number of octets, close brace ("}"), and CRLF. In the case of literals transmitted from server to client, the CRLF is immediately followed by the octet data. In the case of literals transmitted from client to server, the client MUST wait to receive a command continuation request (described later in this document) before sending the octet data (and the remainder of the command). Mon, 25 Aug 2008 22:39:07 +0000 https://bugs.horde.org/ticket/7229#t48456 More trace: change username's password to Voelc7Ods} go to horde ; imp/test.php: enter mail server username and password PHP Mail Server Support Test Attempting to automatically determine the correct connection parameters for your server: Trying protocol imap/notls, Port 143: ERROR - The server returned the following error message: Server disables LOGIN, no recognized SASL authenticator Trying protocol imap/ssl, Port 993: ERROR - The server returned the following error message: Certificate failure for mail.hydrix.com: unable to get local issuer certificate: /C=AU/O=*.hydrix.com/OU=GT81237634/OU=See www.rapidssl.com/resources/cps (c)08/OU=Domain Control Validated - RapidSSL(R)/CN=*.hydrix.com Trying protocol imap/ssl/novalidate-cert, Port 993: ERROR - The server returned the following error message: Error in IMAP command received by server.Error in IMAP command received by server.Error in IMAP command received by server.Too many login failures Trying protocol imap/tls/novalidate-cert, Port 143: ERROR - The server returned the following error message: Error in IMAP command received by server.Error in IMAP command received by server.Error in IMAP command received by server.Too many login failures Could not determine a successful connection protocol. Make sure your mail server is running and you have specified the correct port. > openssl s_client -connect mail.hydrix.com:993 --- * OK [CAPABILITY IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE AUTH=PLAIN ACL ACL2=UNION XMAGICTRASH] Courier-IMAP ready. Copyright 1998-2008 Double Precision, Inc. See COPYING for distribution information. ---- No change password to foofoo: go into imp/test.php again: PHP Mail Server Support Test Attempting to automatically determine the correct connection parameters for your server: Trying protocol imap/notls, Port 143: ERROR - The server returned the following error message: Server disables LOGIN, no recognized SASL authenticator Trying protocol imap/ssl, Port 993: ERROR - The server returned the following error message: Certificate failure for mail.hydrix.com: unable to get local issuer certificate: /C=AU/O=*.hydrix.com/OU=GT81237634/OU=See www.rapidssl.com/resources/cps (c)08/OU=Domain Control Validated - RapidSSL(R)/CN=*.hydrix.com Trying protocol imap/ssl/novalidate-cert, Port 993: SUCCESS - INBOX has 33 messages (0 new 0 recent) Trying protocol imap/tls/novalidate-cert, Port 143: SUCCESS - INBOX has 33 messages (0 new 0 recent) The following configurations were successful and may be used in your imp/config/servers.php file: Configuration 1 'server' => 'mail.hydrix.com' 'protocol' => 'imap/ssl/novalidate-cert' 'port' => '993' Configuration 2 'server' => 'mail.hydrix.com' 'protocol' => 'imap/tls/novalidate-cert' 'port' => '143' The following IMAP server information was discovered from the remote server: Namespace Information NAMESPACE: "INBOX." DELIMITER: . TYPE: personal NAMESPACE: "#shared." DELIMITER: . TYPE: shared NAMESPACE: "shared." DELIMITER: . TYPE: shared IMAP server capabilities: Array ( [UIDPLUS] => 1 [CHILDREN] => 1 [NAMESPACE] => 1 [THREAD] => Array ( [0] => ORDEREDSUBJECT [1] => REFERENCES ) [SORT] => 1 [QUOTA] => 1 [IDLE] => 1 [AUTH] => Array ( [0] => PLAIN ) [ACL] => 1 [ACL2] => Array ( [0] => UNION ) [XMAGICTRASH] => 1 ) IMAP CHILDREN support: SUPPORTED IMAP Charset Search Support: Server supports searching with the UTF-8 character set. ---- Mon, 25 Aug 2008 22:42:28 +0000 https://bugs.horde.org/ticket/7229#t48457 > No it doesn't. We send login information differently than other > MUA's (using the {} notatic). However, different does not mean > broken. See RFC 3501 [4.3]. So, unless you can show otherwise, the > assumption is that *your* IMAP server is broken since nobody else can > reproduce this issue. humm.... okay then... So it works with all email clients I can think of , but not with IMP... So the issue must be with courier-imap... Nothing can be wrong with your baby obviously don't know why I'm wasting my time trying to help here... Mon, 25 Aug 2008 22:45:41 +0000 https://bugs.horde.org/ticket/7229#t48458 > So it works with all email clients I can think of , but not with IMP... > > So the issue must be with courier-imap... The problem is likely not with courier-imap but with c-client (the PHP module we use to interface with the IMAP server). Trying protocol imap/ssl/novalidate-cert, Port 993: ERROR - The server returned the following error message: Error in IMAP command received by server.Error in IMAP command received by server.Error in IMAP command received by server.Too many login failures This error message would be thrown by imap_open(). Since imap_open() is not controlled by IMP, there is nothing we can do if it is broken (thus, IMP isn't broken). That being said, I don't see the same behavior meaning that this bug would most likely be fixed by upgrading your c-client library and rebuilding PHP. Tue, 26 Aug 2008 01:26:23 +0000 https://bugs.horde.org/ticket/7229#t48463 I was able to reproduce this using PHP 4.4.8. PHP 5.2.6 with the same c-client shows no problems. I would recommend upgrading to PHP 5. See also: http://bugs.php.net/bug.php?id=23005 http://bugs.php.net/bug.php?id=27031 Wed, 27 Aug 2008 07:26:41 +0000 https://bugs.horde.org/ticket/7229#t48495