5 .TH INC %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
7 inc \- incorporate new mail
16 .RB [ \-changecur " | " \-nochangecur ]
23 .RB [ \-silent " | " \-nosilent ]
24 .RB [ \-truncate " | " \-notruncate ]
37 .RB [ \-apop " | " \-noapop ]
49 incorporates mail from the user's incoming mail drop into
54 You may specify which folder to use with
56 If no folder is specified, then
58 will use either the folder given by a (non\-empty)
60 entry in the user's profile, or the folder named
61 .RI \*(lq inbox \*(rq.
62 If the specified (or default) folder doesn't
63 exist, the user will be queried prior to its creation.
65 When the new messages are incorporated into the folder, they are assigned
66 numbers starting with the next highest number for the folder. As the
67 messages are processed, a
69 listing of the new mail is produced.
71 If the user's profile contains a
72 .RI \*(lq "Msg\-Protect: nnn" \*(rq
74 will be used as the protection on the newly created messages, otherwise
77 default of 0644 will be used. For all subsequent operations
78 on these messages, this initially assigned protection will be preserved.
83 is specified (usually as a default
84 switch in the profile), then
86 will append a header line and a
87 line per message to the end of the specified audit\-file with the format:
92 <scan line for first message>
93 <scan line for second message>
98 This is useful for keeping track of volume and source of incoming mail.
105 may also produce audits to this (or another) file, perhaps with
106 .RI \*(lq Message\-Id \*(rq
107 information to keep an exact correspondence
109 .RI \*(lq Audit\-file \*(rq
110 will be in the user's nmh directory unless a full path is specified.
113 will incorporate even improperly formatted messages into the
114 user's nmh folder, inserting a blank line prior to the offending component
115 and printing a comment identifying the bad message.
117 In all cases, the user's mail drop will be zeroed, unless the
122 .RI \*(lq Unseen\-Sequence \*(rq
123 is present and non\-empty, then
125 will add each of the newly incorporated messages to
126 each sequence named by the profile entry.
128 will not zero each sequence prior to adding messages.
130 The interpretation of the
138 switches is the same as in
144 switch, one can direct
146 to incorporate messages from a file other than the user's maildrop.
147 Note that the name file will NOT be zeroed, unless the
151 If the environment variable
155 uses it as the location of the user's maildrop instead of the default
159 switch still overrides this, however). If this
160 environment variable is not set, then
162 will consult the profile entry
163 .RI \*(lq MailDrop \*(rq
164 for this information. If the value found is
165 not absolute, then it is interpreted relative to the user's
167 directory. If the value is not found, then
169 will look in the standard system location for the user's maildrop.
175 to be quiet and not ask any questions at all. This is useful for putting
177 in the background and going on to other things.
182 will normally check local mail drops for mail, as covered above. But
184 .RI \*(lq pophost \*(rq
186 .RI \*(lq mts.conf \*(rq,
190 switch is given, or if the
192 environment variable is set, then
194 will query this POP service host for mail to incorporate. If
198 is specified as well, the commandline switch will override
199 the environment variable.
203 to assume that your account name on
204 the POP server is the same as your current username. To specify
205 a different username, use the
210 When using POP, you will normally need to type the password for
211 your account on the POP server, in order to retrieve your messages.
212 It is possible to automate this process by creating a
213 .RI \*(lq .netrc \*(rq
214 file containing your login account information for this POP server.
215 For each POP server, this file should have a line of the following
216 form. Replace the words
221 with your own account information.
233 .RI \*(lq .netrc \*(rq
234 file should be owned and readable only by you.
241 will use the specified command to establish the connection to the POP
244 in the command will be substituted by the hostname to connect to.
251 switch is considered. If given, then
253 simply uses the POP to
255 the user's maildrop from the POP service host to the named file. This switch
256 is provided for those users who prefer to use
258 to read their maildrops.
260 For debugging purposes, you may give the switch
262 which will allow you to watch the POP transaction take place
263 between you and the POP server.
267 has been compiled with APOP support, the
271 to use APOP rather than standard POP3 authentication. Under APOP, a
272 unique string (generally of the format
273 .RI < pid . timestamp @ hostname >
274 ) is announced by the POP server.
283 where digest is the MD5 hash of the unique string followed by a
284 `secret' shared by client and server, essentially equivalent to the user's
285 password (though an APOP-enabled POP3 server could have separate APOP and plain
286 POP3 passwords for a single user).
288 disables APOP in cases where it'd otherwise be used.
292 has been compiled with KPOP support, the
296 to use Kerberized POP rather than standard POP3 on a given invocation.
297 If POPSERVICE was also #defined to "kpop",
299 will be hardwired to always use KPOP.
303 has been compiled with SASL support, the
306 the use of SASL authentication. Depending on the SASL mechanism used, this
307 may require an additional password prompt from the user (but the
308 .RI \*(lq .netrc \*(rq
309 file can be used to store this password). The
311 switch can be used to select a particular SASL mechanism.
313 If SASL authentication is successful,
315 will attempt to negotiate a security layer for session encryption.
316 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
317 when viewing the POP transaction with the
325 .ta \w'%etcdir%/ExtraBigFileName 'u
326 ^$HOME/\&.mh\(ruprofile~^The user profile
327 ^%etcdir%/mts.conf~^nmh mts configuration file
328 ^%mailspool%/$USER~^Location of mail drop
331 .SH "PROFILE COMPONENTS"
335 .ta \w'ExtraBigProfileName 'u
336 ^Path:~^To determine the user's nmh directory
337 ^Alternate\-Mailboxes:~^To determine the user's mailboxes
338 ^Inbox:~^To determine the inbox, default \*(lqinbox\*(rq
339 ^Folder\-Protect:~^To set mode when creating a new folder
340 ^Msg\-Protect:~^To set mode when creating a new message and audit\-file
341 ^Unseen\-Sequence:~^To name sequences denoting unseen messages
345 mhmail(1), scan(1), mh\-mail(5), post(8)
349 .RB ` +folder "' defaulted by \*(lqInbox\*(rq above"
352 .RB ` \-format "' defaulted as described above"
354 .RB ` \-truncate "' if `" \-file " name' not given, `" \-notruncate "' otherwise"
355 .RB ` \-width "' defaulted to the width of the terminal"
362 The folder into which messages are being incorporated will become the
363 current folder. The first message incorporated will become the current
366 option is specified. This leaves the context ready for a
368 of the first new message.
373 switch must be interpreted as a single
374 token by the shell that invokes
376 Therefore, one must usually place the argument to this switch inside