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 ]
36 .RB [ \-sasl " | " \-nosasl ]
43 .RB [ \-certverify " | " \-nocertverify ]
48 incorporates mail from the user's incoming mail drop into an
51 If the mail drop is a file, it can be in
56 If the mail drop is a directory it is considered to be in
60 You may specify which folder to use with
62 If no folder is specified, then
64 will use either the folder given by a (non-empty)
66 entry in the user's profile, or the folder named
67 .RI \*(lq inbox \*(rq.
68 If the specified (or default) folder doesn't
69 exist, the user will be queried prior to its creation.
71 When the new messages are incorporated into the folder, they are assigned
72 numbers starting with the next highest number for the folder.
73 As the messages are processed, a
75 listing of the new mail is produced.
77 The newly created messages will have a mode of 0600, see chmod(1),
78 on filesystems that support it.
80 .RI \*(lq "Msg\-Protect: nnn" \*(rq
81 profile entry gives the mode to use, in octal.
82 For all subsequent operations on these messages, this initially assigned
83 mode will be preserved.
88 is specified (usually as a default switch in the user's profile), then
90 will append a header line and a line per message to the specified
91 audit-file with the format:
96 <scan line for first message>
97 <scan line for second message>
102 This is useful for keeping track of volume and source of incoming mail.
109 may also output audit information to this (or another) file, perhaps with
110 .RI \*(lq Message\-Id \*(rq
111 information to keep an exact correspondence history.
112 .RI \*(lq Audit-file \*(rq
113 is assumed to be in the user's nmh directory unless a full path is specified.
116 will incorporate even improperly formatted messages into the user's
117 nmh folder, inserting a blank line prior to the offending component
118 and printing a comment identifying the bad message.
120 In all cases, except the use of
123 (see below), the user's mail drop will be zeroed, unless the
128 .RI \*(lq Unseen\-Sequence \*(rq
129 is present and non-empty, then
131 will add each of the newly incorporated messages to each sequence
132 named in the profile entry.
134 will not zero each sequence prior to adding messages.
136 The interpretation of the
144 switches is the same as in
150 switch, one can direct
152 to incorporate messages from a file other than the user's mail drop.
153 Note that the named file will
155 be zeroed, unless the
161 switch does not support the use of standard input.
164 command can be used to incorporate mail from the standard input stream.
166 If the environment variable
170 uses it as the location of the user's mail drop instead of the default
174 switch still overrides this, however).
175 If this environment variable is not set, then
177 will consult the profile entry
178 .RI \*(lq MailDrop \*(rq
179 for this information. If the value found is not absolute, then it is
180 interpreted relative to the user's
182 directory. If the value is not found, then
184 will look in the standard system location for the user's mail drop.
190 to be quiet and not ask any questions at all. This is useful for putting
192 in the background and going on to other things.
195 will normally check local mail drops for mail, as covered above.
197 .RI \*(lq pophost \*(rq
199 .RI \*(lq mts.conf \*(rq,
203 switch is given, or if the
205 environment variable is set, then
207 will query this POP service host for mail to incorporate. If
211 is specified as well, the command-line switch will override
212 the environment variable. The
214 switch specifies the port name or number used to connect to the POP
215 server. If unspecified, the default is \*(lqpop3\*(rq.
217 To specify a username for authentication with the POP server, use the
220 switch. The credentials profile entry in
222 describes the ways to supply a username and password.
229 will use the specified command to establish the connection to the POP
232 in the command will be substituted by the hostname to connect to.
234 For debugging purposes, you may give the switch
236 which will allow you to monitor the POP transaction. If
237 .B \-sasl \-saslmech xoauth2
238 is used, the HTTP transaction is also shown.
242 has been compiled with SASL support, the
244 switch will enable the use of SASL authentication.
245 Depending on the SASL mechanism used, this may require an
246 additional password prompt from the user (but the
248 file can be used to store this password, as described in
249 .IR mh\-profile (5)).
252 switch can be used to select a particular SASL mechanism.
254 If SASL authentication is successful,
256 will attempt to negotiate a security layer for session encryption.
257 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
258 when viewing the POP transaction with the
264 for its other features.
268 has been compiled with OAuth support, the
271 .B \-saslmech xoauth2
272 switches will enable OAuth authentication. The
274 switch must be used, and the
276 must be an email address the user has for the service, which must
277 be specified with the
280 switch. Before using this, the user must authorize nmh by running
282 and granting authorization to that account. See
288 has been compiled with TLS support, the
290 switch will require the negotiation of TLS when connecting
291 to the remote POP server.
293 will negotiate TLS immediately after the connection has taken place,
294 before any POP commands are sent or received. Data encrypted by TLS is
295 labeled `(tls-encrypted)' and `(tls-decrypted)' when viewing the POP
300 switch will disable all attempts to negotiate TLS.
302 When using TLS the default is to verify the remote certificate and SubjectName
303 against the local trusted certificate store. This can be controlled by
308 switches. See your OpenSSL documentation for more information on certificate
317 mts configuration file.
320 Location of the system mail drop.
322 .SH "PROFILE COMPONENTS"
326 To determine the user's nmh directory.
328 Alternate\-Mailboxes:
329 To determine the user's mailboxes.
332 To determine the inbox.
335 To set mode when creating a new folder.
338 To set mode when creating a new message and audit-file.
341 To name sequences denoting unseen messages.
355 defaulted by \*(lqInbox\*(rq above.
375 The width of the terminal.
378 The folder into which messages are being incorporated will become the
379 current folder. The first message incorporated will become the current
382 option is specified. This leaves the context ready for a
384 of the first new message.