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 NOT be zeroed, unless the
162 switch does not support the use of standard input.
165 command can be used to incorporate mail from the standard input stream.
167 If the environment variable
171 uses it as the location of the user's mail drop instead of the default
175 switch still overrides this, however).
176 If this environment variable is not set, then
178 will consult the profile entry
179 .RI \*(lq MailDrop \*(rq
180 for this information. If the value found is not absolute, then it is
181 interpreted relative to the user's
183 directory. If the value is not found, then
185 will look in the standard system location for the user's mail drop.
191 to be quiet and not ask any questions at all. This is useful for putting
193 in the background and going on to other things.
196 will normally check local mail drops for mail, as covered above.
198 .RI \*(lq pophost \*(rq
200 .RI \*(lq mts.conf \*(rq,
204 switch is given, or if the
206 environment variable is set, then
208 will query this POP service host for mail to incorporate. If
212 is specified as well, the command-line switch will override
213 the environment variable. The
215 switch specifies the port name or number used to connect to the POP
216 server. If unspecified, the default is \*(lqpop3\*(rq.
218 To specify a username for authentication with the POP server, use the
221 switch. The credentials profile entry in
223 describes the ways to supply a username and password.
230 will use the specified command to establish the connection to the POP
233 in the command will be substituted by the hostname to connect to.
235 When using POP, if the
242 the user's mail drop from the POP service host to the named file.
244 For debugging purposes, you may give the switch
246 which will allow you to monitor the POP transaction. If
247 .B \-sasl \-saslmech xoauth2
248 is used, the HTTP transaction is also shown.
252 has been compiled with SASL support, the
254 switch will enable the use of SASL authentication.
255 Depending on the SASL mechanism used, this may require an
256 additional password prompt from the user (but the
258 file can be used to store this password, as described in
259 .IR mh\-profile (5)).
262 switch can be used to select a particular SASL mechanism.
264 If SASL authentication is successful,
266 will attempt to negotiate a security layer for session encryption.
267 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
268 when viewing the POP transaction with the
272 man page description of
274 for its other features.
278 has been compiled with OAuth support, the
281 .B \-saslmech xoauth2
282 switches will enable OAuth authentication. The
284 switch must be used, and the
286 must be an email address the user has for the service, which must
287 be specified with the
290 switch. Before using this, the user must authorize nmh by running
292 and granting authorization to that account. See
298 has been compiled with TLS support, the
300 switch will require the negotiation of TLS when connecting
301 to the remote POP server.
303 will negotiate TLS immediately after the connection has taken place,
304 before any POP commands are sent or received. Data encrypted by TLS is
305 labeled `(tls-encrypted)' and `(tls-decrypted)` when viewing the POP
310 switch will disable all attempts to negotiate TLS.
312 When using TLS the default is to verify the remote certificate and SubjectName
313 against the local trusted certificate store. This can be controlled by
318 switches. See your OpenSSL documentation for more information on certificate
327 mts configuration file.
330 Location of the system mail drop.
332 .SH "PROFILE COMPONENTS"
336 To determine the user's nmh directory.
338 Alternate\-Mailboxes:
339 To determine the user's mailboxes.
342 To determine the inbox.
345 To set mode when creating a new folder.
348 To set mode when creating a new message and audit-file.
351 To name sequences denoting unseen messages.
365 defaulted by \*(lqInbox\*(rq above.
385 The width of the terminal.
390 The folder into which messages are being incorporated will become the
391 current folder. The first message incorporated will become the current
394 option is specified. This leaves the context ready for a
396 of the first new message.