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 ]
50 incorporates mail from the user's incoming mail drop into
54 If the mail drop is a file, it can be in
59 If the mail drop is a directory it will considered to be a
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. As the
76 messages are processed, a
78 listing of the new mail is produced.
80 If the user's profile contains a
81 .RI \*(lq "Msg\-Protect: nnn" \*(rq
82 entry, it will be used as the protection on the newly created
83 messages, otherwise the
85 default of 0600 will be used (on filesystems that support it). For
86 all subsequent operations on these messages, this initially assigned
87 protection will be preserved.
92 is specified (usually as a default
93 switch in the profile), then
95 will append a header line and a
96 line per message to the end of the specified audit\-file with the format:
101 <scan line for first message>
102 <scan line for second message>
107 This is useful for keeping track of volume and source of incoming mail.
114 may also produce audits to this (or another) file, perhaps with
115 .RI \*(lq Message\-Id \*(rq
116 information to keep an exact correspondence
118 .RI \*(lq Audit\-file \*(rq
119 will be in the user's nmh directory unless a full path is specified.
122 will incorporate even improperly formatted messages into the
123 user's nmh folder, inserting a blank line prior to the offending component
124 and printing a comment identifying the bad message.
126 In all cases, 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
135 each sequence named by 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 maildrop.
156 Note that the name file will NOT be zeroed, unless the
162 switch does not support use of standard input. Instead,
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 maildrop instead of the default
175 switch still overrides this, however). If this
176 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
181 not absolute, then it is 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 maildrop.
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.
197 will normally check local mail drops for mail, as covered above. But
199 .RI \*(lq pophost \*(rq
201 .RI \*(lq mts.conf \*(rq,
205 switch is given, or if the
207 environment variable is set, then
209 will query this POP service host for mail to incorporate. If
213 is specified as well, the commandline switch will override
214 the environment variable. The
216 switch specifies the port name or number used to connect to the POP
217 server. If unspecified the default is \*(lqpop3\*(rq.
219 To specify a username for authentication with the POP server, use the
222 switch. The credentials profile entry in the mh\-profile(5) man page
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.
240 switch is considered. If given, then
242 simply uses the POP to
244 the user's maildrop from the POP service host to the named file.
246 For debugging purposes, you may give the switch
248 which will allow you to watch the POP transaction take place
249 between you and the POP server. If
250 .B \-sasl \-saslmech xoauth2
251 is used, the HTTP transaction is also shown.
255 has been compiled with SASL support, the
258 the use of SASL authentication. Depending on the SASL mechanism used, this
259 may require an additional password prompt from the user (but the
261 file can be used to store this password, as described in the
262 mh-profile(5) man page). The
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 grant authorization to that account. See the
296 man page for more details.
300 has been compiled with TLS support, the
302 switch will require the negotiation of TLS when connecting
303 to the remote POP server. The
305 switch 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)` with viewing the POP
312 switch will disable all attempts to negotiate TLS.
320 mts configuration file.
323 Location of the system mail drop.
325 .SH "PROFILE COMPONENTS"
329 To determine the user's nmh directory.
331 Alternate\-Mailboxes:
332 To determine the user's mailboxes.
335 To determine the inbox.
338 To set mode when creating a new folder.
341 To set mode when creating a new message and audit\-file.
344 To name sequences denoting unseen messages.
358 defaulted by \*(lqInbox\*(rq above.
376 \-notruncate otherwise.
379 The width of the terminal.
384 The folder into which messages are being incorporated will become the
385 current folder. The first message incorporated will become the current
388 option is specified. This leaves the context ready for a
390 of the first new message.