The problem described occurs if the server does support SITE CHMOD command but it has been forbidden intentionally.
Consider the following real-life example. My ftp server is configured to chmod all uploaded files to 664, chmod newly created dirs to 775, and chgrp them all to "ftpadmin", so valuable files uploaded by anonymous users to a "heap" dir could later be put to a proper "classified" dir. I have configured permissions to be group-writable so this administration task could be performed by the members of "ftpadmin" group. Now if I copy some file to the upload dir as an anonymous user with the help of mc, it basically ruins my intentions as it sets back copied file permissions to those of original file (which are not group-writable most of the time). If I forbid SITE CHMOD ftp command, mc still tries to chmod file and fails, resulting a red Retry - Skip - Cancel dialog. The patch proposed by OP works nicely. Andrey -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
