1 .TH INC %manext1% "October 9, 2016" "%nmhversion%"
6 inc \- incorporate new mail
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
55 If the mail drop is a file, it can be in
60 If the mail drop is a directory it will considered to be a
64 You may specify which folder to use with
66 If no folder is specified, then
68 will use either the folder given by a (non\-empty)
70 entry in the user's profile, or the folder named
71 .RI \*(lq inbox \*(rq.
72 If the specified (or default) folder doesn't
73 exist, the user will be queried prior to its creation.
75 When the new messages are incorporated into the folder, they are assigned
76 numbers starting with the next highest number for the folder. As the
77 messages are processed, a
79 listing of the new mail is produced.
81 If the user's profile contains a
82 .RI \*(lq "Msg\-Protect: nnn" \*(rq
83 entry, it will be used as the protection on the newly created
84 messages, otherwise the
86 default of 0600 will be used (on filesystems that support it). For
87 all subsequent operations on these messages, this initially assigned
88 protection will be preserved.
93 is specified (usually as a default
94 switch in the profile), then
96 will append a header line and a
97 line per message to the end of the specified audit\-file with the format:
102 <scan line for first message>
103 <scan line for second message>
108 This is useful for keeping track of volume and source of incoming mail.
115 may also produce audits to this (or another) file, perhaps with
116 .RI \*(lq Message\-Id \*(rq
117 information to keep an exact correspondence
119 .RI \*(lq Audit\-file \*(rq
120 will be in the user's nmh directory unless a full path is specified.
123 will incorporate even improperly formatted messages into the
124 user's nmh folder, inserting a blank line prior to the offending component
125 and printing a comment identifying the bad message.
127 In all cases, the user's mail drop will be zeroed, unless the
132 .RI \*(lq Unseen\-Sequence \*(rq
133 is present and non\-empty, then
135 will add each of the newly incorporated messages to
136 each sequence named by the profile entry.
138 will not zero each sequence prior to adding messages.
140 The interpretation of the
148 switches is the same as in
154 switch, one can direct
156 to incorporate messages from a file other than the user's maildrop.
157 Note that the name file will NOT be zeroed, unless the
163 switch does not support use of standard input. Instead,
166 command can be used to incorporate mail from the standard input stream.
168 If the environment variable
172 uses it as the location of the user's maildrop instead of the default
176 switch still overrides this, however). If this
177 environment variable is not set, then
179 will consult the profile entry
180 .RI \*(lq MailDrop \*(rq
181 for this information. If the value found is
182 not absolute, then it is interpreted relative to the user's
184 directory. If the value is not found, then
186 will look in the standard system location for the user's maildrop.
192 to be quiet and not ask any questions at all. This is useful for putting
194 in the background and going on to other things.
198 will normally check local mail drops for mail, as covered above. But
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 the mh\-profile(5) man page
224 describes the ways to supply a username and password.
231 will use the specified command to establish the connection to the POP
234 in the command will be substituted by the hostname to connect to.
241 switch is considered. If given, then
243 simply uses the POP to
245 the user's maildrop from the POP service host to the named file.
247 For debugging purposes, you may give the switch
249 which will allow you to watch the POP transaction take place
250 between you and the POP server. If
251 .B \-sasl \-saslmech xoauth2
252 is used, the HTTP transaction is also shown.
256 has been compiled with SASL support, the
259 the use of SASL authentication. Depending on the SASL mechanism used, this
260 may require an additional password prompt from the user (but the
262 file can be used to store this password, as described in the
263 mh-profile(5) man page). The
265 switch can be used to select a particular SASL mechanism.
267 If SASL authentication is successful,
269 will attempt to negotiate a security layer for session encryption.
270 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
271 when viewing the POP transaction with the
275 man page description of
277 for its other features.
281 has been compiled with OAuth support, the
284 .B \-saslmech xoauth2
285 switches will enable OAuth authentication. The
287 switch must be used, and the
289 must be an email address the user has for the service, which must
290 be specified with the
293 switch. Before using this, the user must authorize nmh by running
295 and grant authorization to that account. See the
297 man page for more details.
301 has been compiled with TLS support, the
303 switch will require the negotiation of TLS when connecting
304 to the remote POP server. The
306 switch will negotiate TLS immediately after the connection has taken place,
307 before any POP commands are sent or received. Data encrypted by TLS is
308 labeled `(tls-encrypted)' and `(tls-decrypted)` with viewing the POP
313 switch will disable all attempts to negotiate TLS.
315 When using TLS the default is to verify the remote certificate and SubjectName
316 against the local trusted certificate store. This can be controlled by
321 switches. See your OpenSSL documentation for more information on certificate
330 mts configuration file.
333 Location of the system mail drop.
335 .SH "PROFILE COMPONENTS"
339 To determine the user's nmh directory.
341 Alternate\-Mailboxes:
342 To determine the user's mailboxes.
345 To determine the inbox.
348 To set mode when creating a new folder.
351 To set mode when creating a new message and audit\-file.
354 To name sequences denoting unseen messages.
368 defaulted by \*(lqInbox\*(rq above.
386 \-notruncate otherwise.
389 The width of the terminal.
394 The folder into which messages are being incorporated will become the
395 current folder. The first message incorporated will become the current
398 option is specified. This leaves the context ready for a
400 of the first new message.