zwily/cinch — comment on commit 682bd12667f1b586adda316a9b615d8b93f9f6e5
File:  line 0
By zwily:

Actually, that wasn't the problem at all. Cinch is actually sending \r\n\r\n after every command, and this server was not ignoring the blank line. So cinch sent this:

USER foo\r\n\r\n

Changing that above from \r\n to \n made it send this:

USER foo\n\r\n

That worked because the server split on \r\n and then stripped the \n off the end of the command. A better fix would be to figure out why cinch is sending two crlfs after commands...