When I connect from a windows machine using command line FTP to a mac and grab a file (.cab extension) it initiates the transfer in ASCII. However, if I copy that same file to a windows or linux server and then try the transfer using the same client, the transfer is initiated in Binary mode...
What is different in the Mac FTP server that would cause this?
I'm guessing: either the ftpd simply doesn't auto-detect if a file is text or binary, in which case the client has to explicitly request to change mode before transfer begins, or ftpd doesn't know the extension ".cab" is binary. The man page for ftpd doesn't mention anything about auto-detecting a file's nature.
I'm definitely not changing modes on the client explicitly. That's what makes it so odd... It appears to definitely have something to do with the server. I just can't seem to figure out what.
Ah, well, it is my experience that ftp clients start a new session in ascii mode. Thus, you are
required to change them to binary mode explicitly. The exception would be if the mode was changed automatically at the server. So you should type "binary" before executing your transfer.
As for your question "What is different" in the OS X ftpd -- well, that it simply doesn't support the feature you find elsewhere.
Unfortunately, the transfer happens as part of an automated process and I cannot force the switch to binary. Therefore I may be forced to use a Linux/Windows FTP server.
As for the daemon.... I tried sawpping out the Apple xftpd for proftpd with the same results.