To send a file to a remote computer, specify the local file path first, then the remote server and path second. For example, to send file1 to example.com and name it file2 on the server, type:
movedat file1 example.com:file2
All directories in the remote path must exist, unless -B BuildPath is specified.
To save a file into a directory using the same base name, specify the directory as the remote destination and follow it by a forward slash '/'. For example:
movedat file1 example.com:directory/
When the remote destination is a directory, you can send multiple files in a single command:
movedat file1 file2 file3 example.com:directory/
You can also send multiple files using wild-card characters or one of the Moving Directories options.
The server always uses forward slash '/' as its path delimter. But on Windows machines, local pathnames will use the backslash '\' character. So sending a file using the Windows version of movedat could look like this:
movedat C:\mydir\myfile example.com:dirname/subdirname
The windows version of movedat also treats a single character followed by a colon as a local target, rather than a server with a single character name.
Once a file has been successfully uploaded, the server will attempt to set the modification date, access rights, ownership, and group id of the uploaded file to match those of the local file. Whether or not this is successful will depend on the server version, operating systems, and your login access rights.
If a file upload has been interrupted, attempting to send to the same destination will require that you choose whether you want to resume, start over, or skip the file. See the section on Resuming for details.
When the source of a Send is a symbolic link, data from the link target will be sent. This applies to symbolic links pointing to both files and folders.
When Sending folders, the handling of symbolic links depends on whether Streaming Folders is enabled. See Copying Folders for details.
If a symbolic link exists on the server with the same name as a sent file, the sever will attempt to replace the link with the sent file. This will occur regardless of the link's target. If a server-side link points to a folder and you wish to place a sent file in that folder, you must end the link pathname with a slash '/'.
For example, the following would attempt to place "sourcefile" in a folder pointed to by "link":
movedat sourcefile email@example.com:path/link/
movedat sourcefile firstname.lastname@example.org:path/link/destfile
But in this example, "link" would be deleted and replaced by the contents of sourcefile, creating a regular file named "link":
movedat sourcefile email@example.com:path/link
Windows symbolic links are copied as if the target file were in the place of the link. Windows shortcut files (.lnk) are copied as regular files and their targets are ignored.
Irregular files cannot be targeted as the destination of a Send. If an irregular file (device, socket, pipe, etc.) already exists at the destination path, then the upload will fail with an "Object Unavailable" error. See the Known Issues section for further details.