If you are sending files via FTP using StingRay and the receiving site is receiving them with a .bin extension then there are two possible reasons for this. In the address book entry for the site you are sending to there is an option to set Mac Extra.
This field determines how the files are transferred from StingRay to the remote site. This setting can depend upon the remote site, chosen protocol and the type of data. There are 3 options to choose from:
- Full: All file information is transferred to the remote site. (Default)
- Data-fork only: Only the data-fork is extracted from the file and sent to the remote site.
- MacBinary: The file is transferred to the remote site as a MacBinary file.
Setting the 'Mac Extra' for the outgoing job will change what questions the StingRay server asks the remote FTP server. Full will make the StingRay ask 'MACB' - if it gets a reply saying the remote server supports this then it's 
very likely the files will be sent in a MacBinary format.
Try setting the option to 'Datafork Only', as this will just send the file in a binary format but will strip the resource fork. This is fine for files not susceptible to corruption for example PDF or TXT files.
