1 .TH INC %manext1% "February 16, 2013" "%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.
217 to assume that your account name on
218 the POP server is the same as your current username. To specify
219 a different username, use the
224 When using POP, you will normally need to type the password for
225 your account on the POP server, in order to retrieve your messages.
226 It is possible to automate this process by creating a
227 .RI \*(lq .netrc \*(rq
228 file containing your login account information for this POP server.
229 For each POP server, this file should have a line of the following
230 form. Replace the words
235 with your own account information.
247 .RI \*(lq .netrc \*(rq
248 file should be owned and readable only by you.
255 will use the specified command to establish the connection to the POP
258 in the command will be substituted by the hostname to connect to.
265 switch is considered. If given, then
267 simply uses the POP to
269 the user's maildrop from the POP service host to the named file. This switch
270 is provided for those users who prefer to use
272 to read their maildrops.
274 For debugging purposes, you may give the switch
276 which will allow you to watch the POP transaction take place
277 between you and the POP server.
281 has been compiled with SASL support, the
284 the use of SASL authentication. Depending on the SASL mechanism used, this
285 may require an additional password prompt from the user (but the
286 .RI \*(lq .netrc \*(rq
287 file can be used to store this password). The
289 switch can be used to select a particular SASL mechanism.
291 If SASL authentication is successful,
293 will attempt to negotiate a security layer for session encryption.
294 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
295 when viewing the POP transaction with the
305 mts configuration file.
308 Location of the system mail drop.
310 .SH "PROFILE COMPONENTS"
314 To determine the user's nmh directory.
316 Alternate\-Mailboxes:
317 To determine the user's mailboxes.
320 To determine the inbox.
323 To set mode when creating a new folder.
326 To set mode when creating a new message and audit\-file.
329 To name sequences denoting unseen messages.
341 defaulted by \*(lqInbox\*(rq above.
359 \-notruncate otherwise.
362 The width of the terminal.
367 The folder into which messages are being incorporated will become the
368 current folder. The first message incorporated will become the current
371 option is specified. This leaves the context ready for a
373 of the first new message.