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 firstname.lastname@example.org:file2
These examples assume a username is required. If the server is running without authentication, or allows anonymous access, you may omit the "user@" portion.
If the file or path names contain spaces or other special characters, surround the entire argument in quotes, like this:
movedat "My File" "email@example.com:My File"
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 firstname.lastname@example.org:directory/
When the remote destination is a directory, you can send multiple files in a single command:
movedat file1 file2 file3 email@example.com:directory/
The server always uses forward slash '/' as its path delimiter. 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 firstname.lastname@example.org:dirname/subdirname
But be careful not to end a quoted Windows path with a backslash, as this confuses the Windows shell into ignoring the end quote. See the Known Issues section for details.
movedat -h "C:\My Dir\" "email@example.com:My Name/My Folder" Local Application: Invalid Argument: Folder transfer requires source and destination directories
The Windows version of movedat also treats a single character followed by a colon as a local volume, rather than a server with a single character name.
movedat C:\mydir\myfile firstname.lastname@example.org:C:/dirname/subdirname
The file will initially be uploaded with a name ending in "-sv.tmp" and an accompanying "-sv.met". If the upload is interrupted, do not rename these files as doing so may prevent the upload from being resumed. See the Upload Status section for more about these files.
When you begin a Send operation, the destination folder will be searched for files or partial downloads with the same name. If a useable partial upload is found, you may choose to Resume it or replace the existing file.
Once a file has been successfully uploaded, the server will attempt rename the temporary file and to set the modification date, access rights, ownership, and group id of the uploaded file to match those of the local file.
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 (devices, sockets, pipes, etc.) cannot be uploaded or targeted as the destination of a Send. If an irregular file already exists at the destination path, then the upload will fail. See the Known Issues section for further details.