These commands are believed to be fully compliant with RFC959 and RFC1123:
PORT, PASV, USER, PASS, CWD, CDUP, QUIT, DELE, PWD, SYST, NOOP, STOR, APPE,
-ABOR, RNFR, RNTO, MKD, RMD, ALLO, REIN, ACCT, HELP and STAT.
+ABOR, RNFR, RNTO, MKD, RMD, ALLO, REIN, ACCT, HELP, STAT and MODE.
These commands are not implemented at all: SMNT, STOU and SITE.
RFC1123-compliant.)
STRU:
-The STRU command is included, but it ignores its argument and always uses
-file structure (if you really need record structure, mail me; when I'm done
+The STRU command is included, but only file structure is supported (all other
+modes are refused; if you really need record structure, mail me; when I'm done
laughing, I will consider implementing it). RFC959 violation, but RFC1123
excuses the missing record structure.
-MODE:
-The MODE command is included, but it ignores its argument and always uses
-stream mode (the other two are never used anyway). RFC959 violation, it
-requires all other modes to be refused.
-
RETR:
The RETR command is believed to be compliant with RFC959. (There is no default
data port, though -- I'm unsure about this.)
LIST/NLST:
-The LIST and NLST commands ignore some flags (like `-R') given to them. (This
-is much better than it was before, though.) The RFCs say nothing about
-directory listing formats anyway, but I guess this is a violation of GNU ls :-)
+The LIST and NLST commands ignore some flags (like `-1') given to them. (This
+is much better than it was before, though, even recursive listings should work
+now.) The RFCs say nothing about directory listing formats anyway, but I guess
+this is a violation of GNU ls :-)
REST:
The REST command is implemented, but it doesn't check that its argument really