Re: error 500 problem

[Michael Albinus]

Christian Lynbech <address@hidden> writes:

Hi Christian,

> I apologize for not responding to this earlier. Unfortunately, something
> happened at the ftp server, perhaps a software update, which means it
> has changed behaviour.
>
> Before, I could trigger the "500 ...not impl..." report if I called ftp
> on the command line with the -n option. Now, it happily starts up with
> no 500 reports no matter how I call it.

No problem. I've committed the patch meanwhile, it doesn't hurt.

> However, it now fails in a new way. I think what happens is that it
> starts up in passive mode which seems to confuse ange-ftp. At least when
> one does an "ls", nothing seems to happen, ftp just hangs. If I then
> execute an "passive off", ls starts to produce output as I am used to.
>
> Ange-ftp has some support for passive mode, but it expects that it
> should turn it on and this fails somehow (at least in the eyes of
> ange-ftp) and there is no way to actively turn passive off, as far as I
> can tell from them code. The documentation of `ange-ftp-passive-host-alist'
> seems to suggest one can control it in either direction.

Yes. Reading the code, the following should suffice for you:

(add-to-list 'ange-ftp-passive-host-alist
             (cons (regexp-quote "your host") "off"))

Instead of (regexp-quote "your host") you could use any regexp which
matches your host name(s).

Please tell us, if it doesn't work. Maybe there is still an error in
ange-ftp. In that case, I would like also to see the ange-ftp buffer.

> Thanks for the looking into it.

Best regards, Michael.