I noticed whilst a file was being copied from an FTP if the server drops out, example in the case the server was rebooted, Opus displays an error message correctly. If you wait until the server is up and running again before pressing retry Opus does not seem to be able to reconnect to restart the file operation. It just sits there doing nothing. I tried pausing and then resuming but nothing changes, you have to abort the operation before starting all over again.
Any ideas if this is a bug or just me?
I have seen this sort of behavior before as well - the CURRENT file in progress has to be SKIPPED, but the rest seem to work ok after that one.
It might be nice to have a "requeue" type option - since retrying doesn't work the first time.
It would be nice if Leo or Greg could at least acknowledge if this is a bug 
I don't know if it's a "bug"... but either way, asking for GPSoft to confirm something one way or another makes me wonder if you've actually reported the issue to them? Submit it as an official support request if you really want them to acknowledge it (link in my signature)... or feature enhancement (I expect Opus is currently intended to have a "resume" feature on broken ftp transfers...).