1 .TH INC %manext1% "April 18, 2014" "%nmhversion%"
6 inc \- incorporate new mail
15 .RB [ \-changecur " | " \-nochangecur ]
22 .RB [ \-silent " | " \-nosilent ]
23 .RB [ \-truncate " | " \-notruncate ]
37 .RB [ \-sasl " | " \-nosasl ]
46 incorporates mail from the user's incoming mail drop into
50 If the mail drop is a file, it can be in
55 If the mail drop is a directory it will considered to be a
59 You may specify which folder to use with
61 If no folder is specified, then
63 will use either the folder given by a (non\-empty)
65 entry in the user's profile, or the folder named
66 .RI \*(lq inbox \*(rq.
67 If the specified (or default) folder doesn't
68 exist, the user will be queried prior to its creation.
70 When the new messages are incorporated into the folder, they are assigned
71 numbers starting with the next highest number for the folder. As the
72 messages are processed, a
74 listing of the new mail is produced.
76 If the user's profile contains a
77 .RI \*(lq "Msg\-Protect: nnn" \*(rq
78 entry, it will be used as the protection on the newly created
79 messages, otherwise the
81 default of 0600 will be used (on filesystems that support it). For
82 all subsequent operations on these messages, this initially assigned
83 protection will be preserved.
88 is specified (usually as a default
89 switch in the profile), then
91 will append a header line and a
92 line per message to the end of the specified audit\-file with the format:
97 <scan line for first message>
98 <scan line for second message>
103 This is useful for keeping track of volume and source of incoming mail.
110 may also produce audits to this (or another) file, perhaps with
111 .RI \*(lq Message\-Id \*(rq
112 information to keep an exact correspondence
114 .RI \*(lq Audit\-file \*(rq
115 will be in the user's nmh directory unless a full path is specified.
118 will incorporate even improperly formatted messages into the
119 user's nmh folder, inserting a blank line prior to the offending component
120 and printing a comment identifying the bad message.
122 In all cases, the user's mail drop will be zeroed, unless the
127 .RI \*(lq Unseen\-Sequence \*(rq
128 is present and non\-empty, then
130 will add each of the newly incorporated messages to
131 each sequence named by the profile entry.
133 will not zero each sequence prior to adding messages.
135 The interpretation of the
143 switches is the same as in
149 switch, one can direct
151 to incorporate messages from a file other than the user's maildrop.
152 Note that the name file will NOT be zeroed, unless the
158 switch does not support use of standard input. Instead,
161 command can be used to incorporate mail from the standard input stream.
163 If the environment variable
167 uses it as the location of the user's maildrop instead of the default
171 switch still overrides this, however). If this
172 environment variable is not set, then
174 will consult the profile entry
175 .RI \*(lq MailDrop \*(rq
176 for this information. If the value found is
177 not absolute, then it is interpreted relative to the user's
179 directory. If the value is not found, then
181 will look in the standard system location for the user's maildrop.
187 to be quiet and not ask any questions at all. This is useful for putting
189 in the background and going on to other things.
193 will normally check local mail drops for mail, as covered above. But
195 .RI \*(lq pophost \*(rq
197 .RI \*(lq mts.conf \*(rq,
201 switch is given, or if the
203 environment variable is set, then
205 will query this POP service host for mail to incorporate. If
209 is specified as well, the commandline switch will override
210 the environment variable. The
212 switch specifies the port name or number used to connect to the POP
213 server. If unspecified the default is \*(lqpop3\*(rq.
215 To specify a username for authentication with the POP server, use the
218 switch. The credentials profile entry in the mh\-profile(5) man page
219 describes the ways to supply a username and password.
226 will use the specified command to establish the connection to the POP
229 in the command will be substituted by the hostname to connect to.
236 switch is considered. If given, then
238 simply uses the POP to
240 the user's maildrop from the POP service host to the named file.
242 For debugging purposes, you may give the switch
244 which will allow you to watch the POP transaction take place
245 between you and the POP server.
249 has been compiled with SASL support, the
252 the use of SASL authentication. Depending on the SASL mechanism used, this
253 may require an additional password prompt from the user (but the
255 file can be used to store this password, as described in the
256 mh-profile(5) man page). The
258 switch can be used to select a particular SASL mechanism.
260 If SASL authentication is successful,
262 will attempt to negotiate a security layer for session encryption.
263 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
264 when viewing the POP transaction with the
274 mts configuration file.
277 Location of the system mail drop.
279 .SH "PROFILE COMPONENTS"
283 To determine the user's nmh directory.
285 Alternate\-Mailboxes:
286 To determine the user's mailboxes.
289 To determine the inbox.
292 To set mode when creating a new folder.
295 To set mode when creating a new message and audit\-file.
298 To name sequences denoting unseen messages.
311 defaulted by \*(lqInbox\*(rq above.
329 \-notruncate otherwise.
332 The width of the terminal.
337 The folder into which messages are being incorporated will become the
338 current folder. The first message incorporated will become the current
341 option is specified. This leaves the context ready for a
343 of the first new message.
projects / nmh / blob