First, I would like to state that Rebex FTP and Rebex FTP/SSL doesn't modify the uploaded file data in any way in either ASCII or binary mode - the data is send as-is in both cases.
If you see an additional control M character at the end of each line when you open the file at the Unix server, it most likely represents the character (code 13) that is used as a part of Windows/DOS end-of-line sequence . The character (code 10) is the Unix end-of-line sequences. In binary mode, the original sequences are left intact and many Unix applications can't handle that (some display it as control M or ^M).
Normally, the to conversion is performed by the FTP server when ASCII transfer mode is specified, but this doesn't work ar your server some reason. To make it possible to tell what is going on, would it be possible to do this?
- Upload a text file to the server in ASCII mode.
- Download this text file from the server in binary mode.
- Send us (to firstname.lastname@example.org) both the original text file (before the upload) and the downloaded text file (which was uploaded using ASCII and downloaded using binary). Please send both in a ZIP file to prevent mail servers from modifying them. By comparing the two files, we should be able to tell what is going on.