1 .TH INC %manext1% "July 1, 2012" "%nmhversion%"
6 inc \- incorporate new mail
15 .RB [ \-changecur " | " \-nochangecur ]
22 .RB [ \-silent " | " \-nosilent ]
23 .RB [ \-truncate " | " \-notruncate ]
44 incorporates mail from the user's incoming mail drop into
48 If the mail drop is a file, it can be in
53 If the mail drop is a directory it will considered to be a
57 You may specify which folder to use with
59 If no folder is specified, then
61 will use either the folder given by a (non\-empty)
63 entry in the user's profile, or the folder named
64 .RI \*(lq inbox \*(rq.
65 If the specified (or default) folder doesn't
66 exist, the user will be queried prior to its creation.
68 When the new messages are incorporated into the folder, they are assigned
69 numbers starting with the next highest number for the folder. As the
70 messages are processed, a
72 listing of the new mail is produced.
74 If the user's profile contains a
75 .RI \*(lq "Msg\-Protect: nnn" \*(rq
76 entry, it will be used as the protection on the newly created
77 messages, otherwise the
79 default of 0600 will be used (on filesystems that support it). For
80 all subsequent operations on these messages, this initially assigned
81 protection will be preserved.
86 is specified (usually as a default
87 switch in the profile), then
89 will append a header line and a
90 line per message to the end of the specified audit\-file with the format:
95 <scan line for first message>
96 <scan line for second message>
101 This is useful for keeping track of volume and source of incoming mail.
108 may also produce audits to this (or another) file, perhaps with
109 .RI \*(lq Message\-Id \*(rq
110 information to keep an exact correspondence
112 .RI \*(lq Audit\-file \*(rq
113 will be in the user's nmh directory unless a full path is specified.
116 will incorporate even improperly formatted messages into the
117 user's nmh folder, inserting a blank line prior to the offending component
118 and printing a comment identifying the bad message.
120 In all cases, the user's mail drop will be zeroed, unless the
125 .RI \*(lq Unseen\-Sequence \*(rq
126 is present and non\-empty, then
128 will add each of the newly incorporated messages to
129 each sequence named by the profile entry.
131 will not zero each sequence prior to adding messages.
133 The interpretation of the
141 switches is the same as in
147 switch, one can direct
149 to incorporate messages from a file other than the user's maildrop.
150 Note that the name file will NOT be zeroed, unless the
154 If the environment variable
158 uses it as the location of the user's maildrop instead of the default
162 switch still overrides this, however). If this
163 environment variable is not set, then
165 will consult the profile entry
166 .RI \*(lq MailDrop \*(rq
167 for this information. If the value found is
168 not absolute, then it is interpreted relative to the user's
170 directory. If the value is not found, then
172 will look in the standard system location for the user's maildrop.
178 to be quiet and not ask any questions at all. This is useful for putting
180 in the background and going on to other things.
184 will normally check local mail drops for mail, as covered above. But
186 .RI \*(lq pophost \*(rq
188 .RI \*(lq mts.conf \*(rq,
192 switch is given, or if the
194 environment variable is set, then
196 will query this POP service host for mail to incorporate. If
200 is specified as well, the commandline switch will override
201 the environment variable.
205 to assume that your account name on
206 the POP server is the same as your current username. To specify
207 a different username, use the
212 When using POP, you will normally need to type the password for
213 your account on the POP server, in order to retrieve your messages.
214 It is possible to automate this process by creating a
215 .RI \*(lq .netrc \*(rq
216 file containing your login account information for this POP server.
217 For each POP server, this file should have a line of the following
218 form. Replace the words
223 with your own account information.
235 .RI \*(lq .netrc \*(rq
236 file should be owned and readable only by you.
243 will use the specified command to establish the connection to the POP
246 in the command will be substituted by the hostname to connect to.
253 switch is considered. If given, then
255 simply uses the POP to
257 the user's maildrop from the POP service host to the named file. This switch
258 is provided for those users who prefer to use
260 to read their maildrops.
262 For debugging purposes, you may give the switch
264 which will allow you to watch the POP transaction take place
265 between you and the POP server.
269 has been compiled with SASL support, the
272 the use of SASL authentication. Depending on the SASL mechanism used, this
273 may require an additional password prompt from the user (but the
274 .RI \*(lq .netrc \*(rq
275 file can be used to store this password). The
277 switch can be used to select a particular SASL mechanism.
279 If SASL authentication is successful,
281 will attempt to negotiate a security layer for session encryption.
282 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
283 when viewing the POP transaction with the
289 .ta \w'%etcdir%/ExtraBigFileName 'u
290 ^$HOME/\&.mh\(ruprofile~^The user profile
291 ^%etcdir%/mts.conf~^nmh mts configuration file
292 ^%mailspool%/$USER~^Location of mail drop
294 .SH "PROFILE COMPONENTS"
298 .ta \w'ExtraBigProfileName 'u
299 ^Path:~^To determine the user's nmh directory
300 ^Alternate\-Mailboxes:~^To determine the user's mailboxes
301 ^Inbox:~^To determine the inbox, default \*(lqinbox\*(rq
302 ^Folder\-Protect:~^To set mode when creating a new folder
303 ^Msg\-Protect:~^To set mode when creating a new message and audit\-file
304 ^Unseen\-Sequence:~^To name sequences denoting unseen messages
313 .RB ` +folder "' defaulted by \*(lqInbox\*(rq above"
316 .RB ` \-format "' defaulted as described above"
318 .RB ` \-truncate "' if `" \-file " name' not given, `" \-notruncate "' otherwise"
319 .RB ` \-width "' defaulted to the width of the terminal"
323 The folder into which messages are being incorporated will become the
324 current folder. The first message incorporated will become the current
327 option is specified. This leaves the context ready for a
329 of the first new message.
333 switch must be interpreted as a single
334 token by the shell that invokes
336 Therefore, one must usually place the argument to this switch inside
projects / mmh / blob