1SENDFILES(1) General Commands Manual SENDFILES(1)
2
3
4
6 sendfiles - send multiple files by MIME message with nmh
7
9 sendfiles [-help] [-version] [-compress bzip2 | compress | gzip | lzma
10 | none]
11 [-from sender] [-delay n | -n]
12 -to recipient -subject subject | recipient subject
13 file/directory1 [file/directory2 ...]
14
16 The shell script sendfiles is used to send a collection of files and
17 directories via electronic mail.
18
19 sendfiles will archive the files and directories you name with the tar
20 command, and then mail the compressed archive to the “recipient” with
21 the given “subject”. The archive will be automatically split up into
22 as many messages as necessary in order to get past most mailers.
23
24 The -to switch specifies the recipient. The -subject switch specifies
25 the subject. Alternatively, these two required values can be provided
26 without their corresponding switch names.
27
28 The -from switch can, and should, be used to specify the sender's mail‐
29 box (name and email address). Alternatively, the PERSON environment
30 variable can be used for the same purpose. If neither is used, send‐
31 files will supply a “From:” header field using the sender's local mail‐
32 box, see localmbox in mh-format(5).
33
34 The -compress command line switch can be used to override the run-time
35 determination of the compression program by sendfiles. -compress none
36 (alternatively, -none) disables compression.
37
38 Sometimes you want sendfiles to pause after posting a partial message.
39 This is usually the case when you are running sendmail and expect to
40 generate a lot of partial messages. The -delay switch specifies the
41 number of seconds to pause in between postings, e.g.,
42
43 sendfiles -delay 30 -to recipient -subject “subject” files ...
44
45 will pause 30 seconds in between each posting. An alternate form of
46 the switch with just the delay time, -30, for example, is also sup‐
47 ported.
48
49 Extracting the Received Files
50 When these messages are received, invoke mhstore once for the list of
51 messages. The default is for mhstore to store the combined parts as a
52 new message in the current folder, although this can be changed using
53 storage formatting strings. You can then use mhlist to find out what's
54 inside; possibly followed by mhstore again to write the archive to a
55 file where you can subsequently uncompress and untar it. For instance:
56
57 % mhlist 5-8
58 msg part type/subtype size description
59 5 message/partial 47K part 1 of 4
60 6 message/partial 47K part 2 of 4
61 7 message/partial 47K part 3 of 4
62 8 message/partial 18K part 4 of 4
63 % mhstore 5-8
64 reassembling partials 5,6,7,8 to folder inbox as message 9
65 % mhlist -verbose 9
66 msg part type/subtype size description
67 9 application/octet-stream 118K
68 (extract with uncompress | tar xvpf -)
69 type=tar
70 conversions=compress
71 % mhstore 9
72 % uncompress < 9.tar.Z | tar xvpf -
73
74 Alternately, by using the -auto switch, mhstore will automatically do
75 the extraction for you:
76
77 % mhlist 5-8
78 msg part type/subtype size description
79 5 message/partial 47K part 1 of 4
80 6 message/partial 47K part 2 of 4
81 7 message/partial 47K part 3 of 4
82 8 message/partial 18K part 4 of 4
83 % mhstore 5-8
84 reassembling partials 5,6,7,8 to folder inbox as message 9
85 % mhlist -verbose 9
86 msg part type/subtype size description
87 9 application/octet-stream 118K
88 (extract with uncompress | tar xvpf -)
89 type=tar
90 conversions=compress
91 % mhstore -auto 9
92 -- tar listing appears here as files are extracted
93
94 As the second tar listing is generated, the files are extracted. A
95 prudent user will never put -auto in the .mh_profile file. The correct
96 procedure is to first use mhlist to find out what will be extracted.
97 Then mhstore can be invoked with -auto to perform the extraction.
98
100 $HOME/.mh_profile The user profile
101
103 Path: To determine the user's nmh directory
104 Current-Folder: To find the default current folder
105
107 mhbuild(1), mhlist(1), mhshow(1), mhstore(1), mh-format(5)
108
109 Proposed Standard for Message Encapsulation (RFC 934)
110
112 `-delay 0'
113 `-from localmbox'
114
116 None
117
118
119
120nmh-1.7.1 2012-11-14 SENDFILES(1)