550 error on certain characters

[scarecrow]

This happens with the latest Filezilla 3.2.8.1 under winXP.

Code: Select all

CWD 2009 Gregorian - Masters Of Chant Chapter VII  [FLAC]
Απάντηση:	250 CWD command successful
Εντολή:	PWD
Απάντηση:	257 "/users/someone/2009 Gregorian - Masters Of Chant Chapter VII  [FLAC]" is the current directory
Εντολή:	PASV
Απάντηση:	227 Entering Passive Mode (91,121,113,175,253,192).
Εντολή:	MLSD
Απάντηση:	550 Unable to handle command
Σφάλμα:	Άνοιγμα φακέλου απέτυχε

The remote server is proFTPd with TLS enabled, although it doesn't matter if I connect with TLS or not- I get the same error.
This happens with directories where there are brackets [ ]
I don't have issues entering any other kind of directories (with no brackets present).
I also tried Total Commander, which has no trouble entering these directories.

[botg]

This is a bug in ProFTPD. You need to upgrade to a more recent version. If you are already using the most recent version you need to switch to a different server.

[scarecrow]

Ah... OK, but then- why older versions of Filezilla (e.g. 3.2.3) work OK on the same server?
I can undesrtand that each one has its own opinion about the FTP standards, but this is really too much...
For the record, the version of ProFTPd used is rather recent (1.3.2).

[botg]

Older versions of FileZilla did things differently. The way FZ works now is better and fully compatible with the FTP standards.

[scarecrow]

Noted- and understood. However, since I have no control over the server, I cannot do much for the time being (apart from using 3.2.3, or another client).
Thanks for the input.

[botg]

You could contact the server administrator. If he's worth his paycheck he'll solve this problem for you. If he refuses to fix this problem for you he should be fire imho.

[boco]

@botg: You really should provide an option to fallback to LIST. And yes, I know that MLSx is the better choice.

[botg]

I'm no longer adding workarounds for broken servers. If I do those broken servers will never get fixed.

[scarecrow]

OK, now comes another question:
I'm trying to build filezilla 3.2.3 under ArchLinux (for ,errr, a broken server... ).
However, I can't, because the configuration script is looking for libgnutls-config which is deprecated/removed from newer than 2.8 gnutls builds (Arch currently has 2.8.3).
Can you suggest a patch, or something to solve the issue?

[botg]

3.2.3 is heavily outdated. The most recent version is 3.2.8.1 which compiles fine.

[scarecrow]

Ah... yes, I know. Actually, I don't have to compile 3.2.8.1 at all: it's in the semi-official "community" repos of ArchLinux, pre-compiled.
I asked about HOW to compile an older filezilla release, which needs older/deprecated libs. Since you are reluctant to answer, no problem- I will use gftp (yeah, that old, buggy, outdated, slow client...).
gftp is working fine on that "bad" server, without any issues... while 3.2.8.1 does not.
Please, have in mind thet the server side of things is mostly out of our reach...

[boco]

Yes, I don't understand either. It would be easy to just ignore MLSx support for such servers.

[scarecrow]

Yep- I have seen in the build instructions how to build new filezilla releases with older gnutls versions.
But... I want to do the exact opposite: Build an older filezilla relase with current gnutls libs.
I will agree with boco: Having LIST instead of MLSx on that kind of servers would be optimal, but since Tim is not willing to support it anymore, any tip about building older filezillas (and 3.2.3 in particular) would be most welcome.
In our forums (Archlinux) I have found a patch for another program which does not build against the current gnutls. I will try to adapt it for filezilla old versions, but since I'm rather goofy on C++, don't hold your breath...

[botg]

You need to contact your server administrator so that he can fix his broken server.

If your server administrator refuses to fix this problem he should be fired, because he's either clueless or lazy, or even both.

[scarecrow]

Well, I've contacted the server admin, and he absolutely refuses switching to a RC version of proFTPd - but he promised he will upgrade when 1.3.3 hits the road.
Up to then, and since I failed compiling 3.2.3, I ended up using the statically built 3.2.3 from sourceforge.
Please consider the case closed- for now, and thanks for your input.