4 .TH INC %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
6 inc \- incorporate new mail
15 .RB [ \-changecur " | " \-nochangecur ]
20 .RB [ \-silent " | " \-nosilent ]
21 .RB [ \-truncate " | " \-notruncate ]
29 incorporates mail from the user's incoming mail drop into
34 You may specify which folder to use with
36 If no folder is specified, then
38 will use either the folder given by a (non\-empty)
40 entry in the user's profile, or the folder named
42 If the specified (or default) folder doesn't
43 exist, the user will (in
45 mode) be queried prior to its creation.
47 When the new messages are incorporated into the folder, they are assigned
48 numbers starting with the next highest number for the folder. As the
49 messages are processed, a
51 listing of the new mail is produced.
53 If the user's profile contains a
54 .RI ` "Msg\-Protect: nnn" '
56 will be used as the protection on the newly created messages, otherwise
59 default of 0644 will be used. For all subsequent operations
60 on these messages, this initially assigned protection will be preserved.
65 is specified (usually as a default
66 switch in the profile), then
68 will append a header line and a
69 line per message to the end of the specified audit\-file with the format:
74 <scan line for first message>
75 <scan line for second message>
80 This is useful for keeping track of volume and source of incoming mail.
87 may also produce audits to this (or another) file, perhaps with
89 information to keep an exact correspondence
92 will be in the current directory unless a full path is specified.
95 will incorporate even improperly formatted messages into the
96 user's mh folder, inserting a blank line prior to the offending component
97 and printing a comment identifying the bad message.
99 In all cases, the user's mail drop will be zeroed, unless the
104 .RI ` Unseen\-Sequence '
105 is present and non\-empty, then
107 will add each of the newly incorporated messages to
108 each sequence named by the profile entry.
110 will not zero each sequence prior to adding messages.
112 The interpretation of the
118 switches is the same as in
124 switch, one can direct
126 to incorporate messages from a file other than the user's maildrop.
127 Note that the named file will NOT be zeroed, unless the
131 If the environment variable
135 uses it as the location of the user's maildrop instead of the default
139 switch still overrides this, however). If this
140 environment variable is not set, then
142 will consult the profile entry
144 for this information. If the value found is
145 not absolute, then it is interpreted relative to the user's
147 directory. If the value is not found, then
149 will look in the standard system location for the user's maildrop.
155 to be quiet and not ask any questions at all. This is useful for putting
157 in the background and going on to other things.
162 .ta \w'%etcdir%/ExtraBigFileName 'u
163 ^$HOME/.mmh/profile~^The user profile
164 ^%mailspool%/$USER~^Location of mail drop
167 .SH "PROFILE COMPONENTS"
171 .ta \w'ExtraBigProfileName 'u
172 ^Path:~^To determine the user's mail storage
173 ^Alternate\-Mailboxes:~^To determine the user's mailboxes
174 ^Inbox:~^To determine the inbox, default `inbox'
175 ^Folder\-Protect:~^To set mode when creating a new folder
176 ^Msg\-Protect:~^To set mode when creating a new message and audit\-file
177 ^Unseen\-Sequence:~^To name sequences denoting unseen messages
185 .RB ` +folder "' defaulted by `Inbox' above"
188 .RB ` \-form "' defaulted as described above"
190 .RB ` \-truncate "' if `" \-file " name' not given, `" \-notruncate "' otherwise"
191 .RB ` \-width "' defaulted to the width of the terminal"
195 The folder into which messages are being incorporated will become the
196 current folder. The first message incorporated will become the current
199 option is specified. This leaves the context ready for a
201 of the first new message.
projects / mmh / blob