The server is broken, as it does not double periods (full stops) at the start of the line
See RFC977, 2.4.1. Text Responses.
This is confusing the code, which thinks it has found end of text.
When the next command is sent, it gets the next line of text, rather than the proper reply (which would presumably be sent after the final period), so reports an error.
Having said that, it should be possible to allow for this bad behaviour, as the termination line does look uniquely identifiable.
The situation is that the server is not RFC-compliant.
Also that LIST ACTIVE does not seem to work.
If it is not supported, it should treat it like "LIST invalid" and respond with "501 bad command usage" or something similar.
The initial part of the listing looks rather odd - why does the server allow such strange names?
And at the end, there are a couple of odd names, too.