fetches files from a SAFT server to the local user spool.
In the SAFT server spool there must lay your sendfile public key to
identify yourself. This key can be generated by the
command and has to be transfered to the SAFT server at the very first time.
This prevents other people to steal your files.
You may list or fetch your files from the server. But remember,
they are stored first in your local sendfile spool. You have to call
to really receive them to your current directory.
Explicitly force IPv4 or IPv6 connections. By default, the program will try to resolve the name given, and
choose the appropriate protocol automatically. If resolving a host name returns both IPv4 and IPv6 addresses,
fetchfile will try to use the adresses in the order they are returned by the resolver.
Only list the files on the server.
Fetch all files.
Keep files on server after fetching.
Delete files without receiving.
Specify the file number instead of the file name.
Call receive automaticly afterwards.
Restrict file selection to this specifc user.
Show version information and exit.
Be verbose and show SAFT protocol messages.
Send files to stdout directly.
Ignore testing whether file has been already fetched.
Quiet mode 1: print no transfer messages.
Quiet mode 2: print no transfer, information or warning messages.
Initialize fetchfile and the pgp key pair.
Specify an alternate saft server and/or alternate user.
Read configuration file "config" or "restrictions" from server.
Write configuration file "config" or "restrictions" to server.
filename or filenumber
Specify the name of the file or its number (with option -n).
fetchfile -Cr=config -s saft.belwue.de
Your local spool directory.
Your local private spool directory if /var/spool/sendfile/$USER/ does not
Your configuration files for the server. See sendfile(1) for a description.