Bug#471563: After the first 'id' command is issues Cyrus IMAPD always returns an error

[Dan White]

On 17/01/10 21:53 +0100, Sergio Gelato wrote:
>* Dan White [2010-01-16 21:58:33 -0600]:
>>> a1 id ("vendor" "Zimbra" "os" "Linux" "os-version" "12")
>>> * ID ("name" "Cyrus IMAPD" "version" "v2.2.13-Debian-2.2.13-10 2006/11/13 16:17:53" "vendor" "Project Cyrus" "support-url" "http://asg.web.cmu.edu/cyrus" "os" "Linux" "os-version" "2.6.18-ovz-028stab051.1" "environment" "Built w/ Cyrus SASL 2.1.22; Running w/Cyrus SASL 2.1.22; Built w/Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003); Running w/Sleepycat Software: Berkeley DB 4.2.52: (December  3, 2003); Built w/OpenSSL 0.9.8c 05 Sep 2006; Running w/ OpenSSL 0.9.8c 05 Sep 2006; CMU Sieve 2.2; TCP Wrappers; NET-SNMP; mmap = shared; lock = fcntl; nonblock = fcntl; idle = poll")
>>> a1 OK Completed
>>> a2 id ("vendor" "zimbra")
>>> a2 NO Only one Id allowed in non-authenticated state
>
>I don't see NO listed as a valid response in RFC 2971 § 3.1, only OK and BAD.
>So it would seem that this behavior is not RFC-compliant.

I agree. The server should be sending a NIL/OK.
According to http://www.rfc-editor.org/rfcxx00.html, 2971 is still current.

I'll work on a bug report for upstream and see how difficult it'll be to
patch existing behavior.

-- 
Dan White