Seth Woolley's Man Viewer

Manual for sendfile - man sendfile

([section] manual, -k keyword, -K [section] search, -f whatis)
man plain no title

SENDFILE(1)                                                        SENDFILE(1)



NAME
       sendfile(1,2) - send(2,n) file(1,n)(s) via Internet


SYNOPSIS
       sendfile(1,2)  [  -stMgduvolSPiqQV  ]  [  -c="  comment"  ] [ -C=program ] [
       -ps=[my_ID] ] [ -pe=[to_user] ] [ -m LIMIT ] file(1,n) [...]  user[@host(1,5)]

       sendfile(1,2) -a="archive" [ -uviqQ ] [ -c=" comment" ]  [  -C=program  ]  [
       -ps[=my_ID] ] [ -pe[=to_user] ] file_or_directory [...]  recipient


DESCRIPTION
       sendfile(1,2) sends files to the specified recipient.

       On  the receiving site there must be a SAFT-server (Simple Asynchronous
       File Transfer) installed like sendfiled  which  stores  incoming  files
       into the recipients spool-directory.


       SAFT knows about 4 file(1,n) types:

       BINARY  Byte-stream file(1,n) which will not be modified.

       SOURCE  Record  oriented  program  source file. Only EOL will be trans-
               lated.

       TEXT    Human readable text files. EOL and the character set(7,n,1 builtins) (like Ger-
               man(1,5,7) umlauts) will be translated.

       MIME    Multipurpose  Internet  Mail  Extension  file(1,n) as defined by RFC
               2045-2049.

       Files can be sent compressed or pgp-encrypted and/or pgp-signed.  As an
       extension  to  SAFT,  sendfile(1,2) is able to send(2,n) multiple binary files in(1,8)
       one archive file.

       Default mode for sendfile(1,2) is sending compressed binary files.  Compres-
       sion will be disabled for hosts which are inside your LAN and for files
       which cannot be compressed.

       With the helper program sfconf you can easily configure sendfile.


ARGUMENTS
       You have to specify at least one file(1,n) name and the recipient's address.
       An address can be specified as:

       user
           a local user or a sendfile(1,2) alias (see below), e.g.: framstag

       user@host(1,5)
           an user on a remote host(1,5), e.g.: framstag@bofh.belwue.de

       saft://host(1,5)/user
           like above, but in(1,8) URL-syntax, e.g.: saft://bofh.belwue.de/framstag

       saft://host:port/user
           like above, but with alternate  SAFT-port,  e.g.:  saft://bofh.bel-
           wue.de:4870/framstag


OPTIONS
       -s      Send in(1,8) source mode (not needed if(3,n) sending to a unix host(1,5)).

       -t      Send in(1,8) text mode (not needed if(3,n) sending to a unix host(1,5)).

       -M      Send MIME file(1,n) (must be external composed before!).

       -g      Send  in(1,8) guessed mode: sendfile(1,2) tries to guess the correct mode
               (source, text or binary). This will not work in(1,8) every case  and
               not on all platforms!

       -i      Print more transaction information.

       -v      Verbose mode: show SAFT protocol messages.

       -V      Show version(1,3,5) information and exit.

       -u      Send uncompressed.

       -a      Send  files  or  whole  directories as one archive (binary mode
               only).  You have to specify an archive name.

       -d      Delete previous sent file. No wildcards allowed.

       -o      Overwrite already sent file(1,n)(s) with same name.

       -P      Read file(1,n) from stdin. You must specify a file(1,n) name, too.

       -S      Spool file(1,n) into outgoing queue(1,3) for later processing.  You  must
               run a sendfiled which supports this mode.

       -l      List files in(1,8) the outgoing spool.

       -q      Quiet mode 1: print no transfer messages.

       -Q      Quiet  mode  2:  print no transfer, information or warning mes-
               sages.

       -c      Add a short comment to a single file.

       -C      Force usage of specified compression program (gzip or bzip2).

       -pc     Encrypt file(1,n)(s) with pgp (IDEA symmetric).

       -pe     Encrypt file(1,n)(s) with pgp (public key).

       -ps     Add pgp signature(s) to the file(1,n)(s).

       -m      Limit the maximum thruput (in(1,8) KB/s).

ARGUMENTS
       user    Recipient user name. Can be an alias, too. See below.

       file(1,n)    File name to be sent. Only when using the  -a="archive"  option
               you may specify any file(1,n) or directory.


EXAMPLES
       sendfile(1,2) -t project.txt chief@bigvax.somewhere.net
       sendfile(1,2) -a=jokes -c 'from Gary Larson' *.gif framstag


FILES
       /usr/local/etc/sendfile.deny
             Users  which are not allowed to receive files or messages (set(7,n,1 builtins) by
             root).

       /var/spool/sendfile(1,2)/$USER/config(1,5)/config(1,5)
             Your configuration file. Valid entries are (the | symbol means  "
             or"):

                bell = on|off

             add a bell when a file(1,n) or message arrives.

                deleting = on|off

             allow remote users(1,5) to delete their files after transmission

                msglog = on|off

             log incoming messages in(1,8) /var/spool/sendfile(1,2)/$USER/msglog

                notification = none|both|mail(1,8) [user@host(1,5)]|message [user@host(1,5)]

             send(2,n) a notification when a file(1,n) has been arrived via mail(1,8) or mes-
             sage or none or both mechanism.

                forward = user@host(1,5)

             set(7,n,1 builtins) a forward address.

       /var/spool/sendfile(1,2)/$USER/config(1,5)/restrictions
             List of addresses from where you don't want  messages  or  files.
             The format is:

                user@host(1,5) [mfb]

             m  stands  for  messages, f for files and b for both. Wildcards *
             and ? are allowed. Examples:

                gates@microsoft.com b
                *aol.com m

             You may also specify the addresses in(1,8) URL-syntax.


       /var/spool/sendfile(1,2)/$USER/config(1,5)/aliases
             The sendfile(1,2) alias file. Format:

                alias address [sendfile-options]

             Example:

                chief grmblfz@bigvax.somewhere.net
                ccc chaoscomputerclub@saft.ccc.de -pe -ps

             You may also specify the addresses in(1,8) URL-syntax.


SEE ALSO
       sfconf receive(1) sendmsg(1) fetchfile(1)


AUTHOR
       Ulli Horlacher  -  framstag@rus.uni-stuttgart.de



3rd Berkeley Distribution                                          SENDFILE(1)

References for this manual (incoming links)