Re: nginx imap proxy issue with imap


#1

Hello!

On Wed, Nov 12, 2008 at 09:48:27PM -0000, David Farrar wrote:

server for 30 seconds. This is too many for real life.
guess it may interest other users of nginx if this behaviour is new or rare:

The other test checks if there is an established connection to the
authentication process and stops processing commands if there isn’t, writing
the waiting message to tell the client that it can expect a slight pause. I
saw the number of running authentication processes increasing and
descreasing fairly quickly but I don’t yet know how dovecot is managing its
authentication pool so I can only guess at what’s happening here without
looking into it.

Yes, indeed. I’m somehow missed this possibility assuming that
connection to devecot’s auth process can’t go away in the middle of
operation - but it of course can.

[…]

Getting back to nginx (if people are still reading) -

:slight_smile:

I’m not all that
familiar with imap but I guess that you could safely read data until a line
with the correct tag is encountered with running the risk of eating a
response from some other command?

Not really - arbitrary garbage should still close the connection.
But in most cases (not when waiting for initial greeting) we may
safely read/skip/pass-to-client unexpected untagged responses.

If I have to maintain an out of tree patch
then the one liner for dovecot is looking the better option but I’d rather
ask first if this change could be made to nginx since there are surely other
similar situations that it would avoid.

Personally I think that this change should be made to nginx
eventually, but I’m not Igor.

Maxim D.