SWilliams,
this is an old bug that we had three years ago, seesm it´s not been fixed yet. You will have to fix it yourself, it´s not too difficult.
What happens is that the actual inbound or outbound filename is registred in a table, some F97yyy or so. The field size for the filenames is some 250 bytes. When a BSFN retrieves this filename is retrieves it with all blanks patted up to 250 positions. When you pass a filename like
"c:\mydir\myfile.txt<BLANK><BLANK><BLANK>" to windows it will find it. However, if you pass filename like
/user/jde/myfile<BLANK><BLANK><BLANK>" to Unix, it will not find it, unless the actual filename has all these extra blanks.
What you need to do is find the BSFN and change it (I do not remeber the name, it´s three years ago). Add a right-trim for blanks to it. Worked for us.
Thanks, Gerd