instead, of standards complying
220 (vsFTPd 1.1.3 bla bla)
Running the FTPD Got past fork changed group opened tty /home/directory/bla/bla/log /system/ftpd.logdoing signal signal listening 220 strange FTP server (Version 5.437 Fri Dec 24 08:39:24 CST 2004) ready.
which of course is completely non-standard and doesnt comply to ftp prodotocl.
however, i have actualy found one ftp client that manages to get 220 out of this mess, and after that everything works fine. This client is CuteFTP Pro. Problem is, that none of other ftp clients (windows default, windows commander, ultraedit built in, filezilla) i have tried, understands that, and i would really like to use open source client instead of expensive and bloated cuteftp.
So, question is - could it be possible to do some kind of workaround in winscp, using some script/configuration or whatever, to get through this odd welcome message?
Is there something i can do, apart of downloading source and building my own custom version of winscp client?