1 .TH INC %manext1% 2016-11-02 "%nmhversion%"
6 inc \- incorporate new mail to an nmh folder
17 .RB [ \-changecur " | " \-nochangecur ]
24 .RB [ \-silent " | " \-nosilent ]
25 .RB [ \-truncate " | " \-notruncate ]
39 .RB [ \-sasl " | " \-nosasl ]
46 .RB [ \-certverify " | " \-nocertverify ]
51 incorporates mail from the user's incoming mail drop into an
54 If the mail drop is a file, it can be in
59 If the mail drop is a directory it is considered to be in
63 You may specify which folder to use with
65 If no folder is specified, then
67 will use either the folder given by a (non-empty)
69 entry in the user's profile, or the folder named
70 .RI \*(lq inbox \*(rq.
71 If the specified (or default) folder doesn't
72 exist, the user will be queried prior to its creation.
74 When the new messages are incorporated into the folder, they are assigned
75 numbers starting with the next highest number for the folder.
76 As the messages are processed, a
78 listing of the new mail is produced.
80 The newly created messages will have a mode of 0600, see chmod(1),
81 on filesystems that support it.
83 .RI \*(lq "Msg\-Protect: nnn" \*(rq
84 profile entry gives the mode to use, in octal.
85 For all subsequent operations on these messages, this initially assigned
86 mode will be preserved.
91 is specified (usually as a default switch in the user's profile), then
93 will append a header line and a line per message to the specified
94 audit-file with the format:
99 <scan line for first message>
100 <scan line for second message>
105 This is useful for keeping track of volume and source of incoming mail.
112 may also output audit information to this (or another) file, perhaps with
113 .RI \*(lq Message\-Id \*(rq
114 information to keep an exact correspondence history.
115 .RI \*(lq Audit-file \*(rq
116 is assumed to be in the user's nmh directory unless a full path is specified.
119 will incorporate even improperly formatted messages into the user's
120 nmh folder, inserting a blank line prior to the offending component
121 and printing a comment identifying the bad message.
123 In all cases, except the use of
126 (see below), the user's mail drop will be zeroed, unless the
131 .RI \*(lq Unseen\-Sequence \*(rq
132 is present and non-empty, then
134 will add each of the newly incorporated messages to each sequence
135 named in the profile entry.
137 will not zero each sequence prior to adding messages.
139 The interpretation of the
147 switches is the same as in
153 switch, one can direct
155 to incorporate messages from a file other than the user's mail drop.
156 Note that the named file will
158 be zeroed, unless the
164 switch does not support the use of standard input.
167 command can be used to incorporate mail from the standard input stream.
169 If the environment variable
173 uses it as the location of the user's mail drop instead of the default
177 switch still overrides this, however).
178 If this environment variable is not set, then
180 will consult the profile entry
181 .RI \*(lq MailDrop \*(rq
182 for this information. If the value found is not absolute, then it is
183 interpreted relative to the user's
185 directory. If the value is not found, then
187 will look in the standard system location for the user's mail drop.
193 to be quiet and not ask any questions at all. This is useful for putting
195 in the background and going on to other things.
198 will normally check local mail drops for mail, as covered above.
200 .RI \*(lq pophost \*(rq
202 .RI \*(lq mts.conf \*(rq,
206 switch is given, or if the
208 environment variable is set, then
210 will query this POP service host for mail to incorporate. If
214 is specified as well, the command-line switch will override
215 the environment variable. The
217 switch specifies the port name or number used to connect to the POP
218 server. If unspecified, the default is \*(lqpop3\*(rq.
220 To specify a username for authentication with the POP server, use the
223 switch. The credentials profile entry in
225 describes the ways to supply a username and password.
232 will use the specified command to establish the connection to the POP
235 in the command will be substituted by the hostname to connect to.
237 When using POP, if the
244 the user's mail drop from the POP service host to the named file.
246 For debugging purposes, you may give the switch
248 which will allow you to monitor the POP transaction. If
249 .B \-sasl \-saslmech xoauth2
250 is used, the HTTP transaction is also shown.
254 has been compiled with SASL support, the
256 switch will enable the use of SASL authentication.
257 Depending on the SASL mechanism used, this may require an
258 additional password prompt from the user (but the
260 file can be used to store this password, as described in
261 .IR mh\-profile (5)).
264 switch can be used to select a particular SASL mechanism.
266 If SASL authentication is successful,
268 will attempt to negotiate a security layer for session encryption.
269 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
270 when viewing the POP transaction with the
274 man page description of
276 for its other features.
280 has been compiled with OAuth support, the
283 .B \-saslmech xoauth2
284 switches will enable OAuth authentication. The
286 switch must be used, and the
288 must be an email address the user has for the service, which must
289 be specified with the
292 switch. Before using this, the user must authorize nmh by running
294 and granting authorization to that account. See
300 has been compiled with TLS support, the
302 switch will require the negotiation of TLS when connecting
303 to the remote POP server.
305 will negotiate TLS immediately after the connection has taken place,
306 before any POP commands are sent or received. Data encrypted by TLS is
307 labeled `(tls-encrypted)' and `(tls-decrypted)` when viewing the POP
312 switch will disable all attempts to negotiate TLS.
314 When using TLS the default is to verify the remote certificate and SubjectName
315 against the local trusted certificate store. This can be controlled by
320 switches. See your OpenSSL documentation for more information on certificate
329 mts configuration file.
332 Location of the system mail drop.
334 .SH "PROFILE COMPONENTS"
338 To determine the user's nmh directory.
340 Alternate\-Mailboxes:
341 To determine the user's mailboxes.
344 To determine the inbox.
347 To set mode when creating a new folder.
350 To set mode when creating a new message and audit-file.
353 To name sequences denoting unseen messages.
367 defaulted by \*(lqInbox\*(rq above.
387 The width of the terminal.
392 The folder into which messages are being incorporated will become the
393 current folder. The first message incorporated will become the current
396 option is specified. This leaves the context ready for a
398 of the first new message.