Problems with imap proxy sending invalid username

[Maxim Dounin]

Hello!

On Wed, Jul 14, 2010 at 09:28:50AM -0500, Pat wrote:

> New user of nginx, trying to get started. I set up a php
> authentication script. Whenever I login it seems to pass on the
> wrong username and does not send any password at all.

[...]

> 2010/07/14 09:03:42 [debug] 22837#0: *4 ngx_imap_start: line.data:
> a001 LOGIN {8}
> �0R

This isn't what nginx normally logs, looks like you added this 
logging yourself, right?  You did it wrong - this string contains 
only 16 bytes ("a001 LOGIN {8}" CRLF).

> 2010/07/14 09:03:42 [debug] 22837#0: *4 send: fd:8 16 of 16
> 2010/07/14 09:03:42 [debug] 22837#0: *4 mail proxy dummy handler
> 
> 2010/07/14 09:03:42 [debug] 22837#0: *4 mail proxy imap auth handler
> 2010/07/14 09:03:42 [debug] 22837#0: *4 recv: fd:8 23 of 4096
> 2010/07/14 09:03:42 [error] 22837#0: *4 upstream sent invalid
> response: "a001 NO Login failed." while reading response from
> upstream, client: 10.2.5.60, server: 0.0.0.0:143, login: "trashcan",
> upstream: 10.0.7.134:143

Here we see that your backend replied "NO Login failed." right 
after it got initial "a001 LOGIN {8}" CRLF string.  Expected reply 
is command continuation request.

Looks like your backend just doesn't support IMAP4rev1, at least 
not string literals.  See RFC 3501 for details.

Maxim Dounin