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 ]
35 .RB [ \-apop " | " \-noapop ]
47 incorporates mail from the user's incoming mail drop into
52 You may specify which folder to use with
54 If no folder is specified, then
56 will use either the folder given by a (non\-empty)
58 entry in the user's profile, or the folder named
59 .RI \*(lq inbox \*(rq.
60 If the specified (or default) folder doesn't
61 exist, the user will be queried prior to its creation.
63 When the new messages are incorporated into the folder, they are assigned
64 numbers starting with the next highest number for the folder. As the
65 messages are processed, a
67 listing of the new mail is produced.
69 If the user's profile contains a
70 .RI \*(lq "Msg\-Protect: nnn" \*(rq
72 will be used as the protection on the newly created messages, otherwise
75 default of 0644 will be used. For all subsequent operations
76 on these messages, this initially assigned protection will be preserved.
81 is specified (usually as a default
82 switch in the profile), then
84 will append a header line and a
85 line per message to the end of the specified audit\-file with the format:
90 <scan line for first message>
91 <scan line for second message>
96 This is useful for keeping track of volume and source of incoming mail.
103 may also produce audits to this (or another) file, perhaps with
104 .RI \*(lq Message\-Id \*(rq
105 information to keep an exact correspondence
107 .RI \*(lq Audit\-file \*(rq
108 will be in the user's nmh directory unless a full path is specified.
111 will incorporate even improperly formatted messages into the
112 user's nmh folder, inserting a blank line prior to the offending component
113 and printing a comment identifying the bad message.
115 In all cases, the user's mail drop will be zeroed, unless the
120 .RI \*(lq Unseen\-Sequence \*(rq
121 is present and non\-empty, then
123 will add each of the newly incorporated messages to
124 each sequence named by the profile entry.
126 will not zero each sequence prior to adding messages.
128 The interpretation of the
136 switches is the same as in
142 switch, one can direct
144 to incorporate messages from a file other than the user's maildrop.
145 Note that the name file will NOT be zeroed, unless the
149 If the environment variable
153 uses it as the location of the user's maildrop instead of the default
157 switch still overrides this, however). If this
158 environment variable is not set, then
160 will consult the profile entry
161 .RI \*(lq MailDrop \*(rq
162 for this information. If the value found is
163 not absolute, then it is interpreted relative to the user's
165 directory. If the value is not found, then
167 will look in the standard system location for the user's maildrop.
173 to be quiet and not ask any questions at all. This is useful for putting
175 in the background and going on to other things.
180 will normally check local mail drops for mail, as covered above. But
182 .RI \*(lq pophost \*(rq
184 .RI \*(lq mts.conf \*(rq,
188 switch is given, or if the
190 environment variable is set, then
192 will query this POP service host for mail to incorporate. If
196 is specified as well, the commandline switch will override
197 the environment variable.
201 to assume that your account name on
202 the POP server is the same as your current username. To specify
203 a different username, use the
208 When using POP, you will normally need to type the password for
209 your account on the POP server, in order to retrieve your messages.
210 It is possible to automate this process by creating a
211 .RI \*(lq .netrc \*(rq
212 file containing your login account information for this POP server.
213 For each POP server, this file should have a line of the following
214 form. Replace the words
219 with your own account information.
231 .RI \*(lq .netrc \*(rq
232 file should be owned and readable only by you.
239 switch is considered. If given, then
241 simply uses the POP to
243 the user's maildrop from the POP service host to the named file. This switch
244 is provided for those users who prefer to use
246 to read their maildrops.
248 For debugging purposes, you may give the switch
250 which will allow you to watch the POP transaction take place
251 between you and the POP server.
255 has been compiled with APOP support, the
259 to use APOP rather than standard POP3 authentication. Under APOP, a
260 unique string (generally of the format
261 .RI < pid . timestamp @ hostname >
262 ) is announced by the POP server.
271 where digest is the MD5 hash of the unique string followed by a
272 `secret' shared by client and server, essentially equivalent to the user's
273 password (though an APOP-enabled POP3 server could have separate APOP and plain
274 POP3 passwords for a single user).
276 disables APOP in cases where it'd otherwise be used.
280 has been compiled with KPOP support, the
284 to use Kerberized POP rather than standard POP3 on a given invocation.
285 If POPSERVICE was also #defined to "kpop",
287 will be hardwired to always use KPOP.
291 has been compiled with SASL support, the
294 the use of SASL authentication. Depending on the SASL mechanism used, this
295 may require an additional password prompt from the user (but the
296 .RI \*(lq .netrc \*(rq
297 file can be used to store this password). The
299 switch can be used to select a particular SASL mechanism.
301 If SASL authentication is successful,
303 will attempt to negotiate a security layer for session encryption.
304 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
305 when viewing the POP transaction with the
313 .ta \w'%etcdir%/ExtraBigFileName 'u
314 ^$HOME/\&.mh\(ruprofile~^The user profile
315 ^%etcdir%/mts.conf~^nmh mts configuration file
316 ^%mailspool%/$USER~^Location of mail drop
319 .SH "PROFILE COMPONENTS"
323 .ta \w'ExtraBigProfileName 'u
324 ^Path:~^To determine the user's nmh directory
325 ^Alternate\-Mailboxes:~^To determine the user's mailboxes
326 ^Inbox:~^To determine the inbox, default \*(lqinbox\*(rq
327 ^Folder\-Protect:~^To set mode when creating a new folder
328 ^Msg\-Protect:~^To set mode when creating a new message and audit\-file
329 ^Unseen\-Sequence:~^To name sequences denoting unseen messages
333 mhmail(1), scan(1), mh\-mail(5), post(8)
337 .RB ` +folder "' defaulted by \*(lqInbox\*(rq above"
340 .RB ` \-format "' defaulted as described above"
342 .RB ` \-truncate "' if `" \-file " name' not given, `" \-notruncate "' otherwise"
343 .RB ` \-width "' defaulted to the width of the terminal"
350 The folder into which messages are being incorporated will become the
351 current folder. The first message incorporated will become the current
354 option is specified. This leaves the context ready for a
356 of the first new message.
361 switch must be interpreted as a single
362 token by the shell that invokes
364 Therefore, one must usually place the argument to this switch inside
projects / mmh / blob