5 .TH INC %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
7 inc \- incorporate new mail
15 .RB [ \-changecur " | " \-nochangecur ]
22 .RB [ \-silent " | " \-nosilent ]
23 .RB [ \-truncate " | " \-notruncate ]
34 .RB [ \-apop " | " \-noapop ]
45 incorporates mail from the user's incoming mail drop into
50 You may specify which folder to use with
52 If no folder is specified, then
54 will use either the folder given by a (non\-empty)
56 entry in the user's profile, or the folder named
57 .RI \*(lq inbox \*(rq.
58 If the specified (or default) folder doesn't
59 exist, the user will be queried prior to its creation.
61 When the new messages are incorporated into the folder, they are assigned
62 numbers starting with the next highest number for the folder. As the
63 messages are processed, a
65 listing of the new mail is produced.
67 If the user's profile contains a
68 .RI \*(lq "Msg\-Protect: nnn" \*(rq
70 will be used as the protection on the newly created messages, otherwise
73 default of 0644 will be used. For all subsequent operations
74 on these messages, this initially assigned protection will be preserved.
79 is specified (usually as a default
80 switch in the profile), then
82 will append a header line and a
83 line per message to the end of the specified audit\-file with the format:
88 <scan line for first message>
89 <scan line for second message>
94 This is useful for keeping track of volume and source of incoming mail.
101 may also produce audits to this (or another) file, perhaps with
102 .RI \*(lq Message\-Id \*(rq
103 information to keep an exact correspondence
105 .RI \*(lq Audit\-file \*(rq
106 will be in the user's nmh directory unless a full path is specified.
109 will incorporate even improperly formatted messages into the
110 user's nmh folder, inserting a blank line prior to the offending component
111 and printing a comment identifying the bad message.
113 In all cases, the user's mail drop will be zeroed, unless the
118 .RI \*(lq Unseen\-Sequence \*(rq
119 is present and non\-empty, then
121 will add each of the newly incorporated messages to
122 each sequence named by the profile entry.
124 will not zero each sequence prior to adding messages.
126 The interpretation of the
134 switches is the same as in
140 switch, one can direct
142 to incorporate messages from a file other than the user's maildrop.
143 Note that the name file will NOT be zeroed, unless the
147 If the environment variable
151 uses it as the location of the user's maildrop instead of the default
155 switch still overrides this, however). If this
156 environment variable is not set, then
158 will consult the profile entry
159 .RI \*(lq MailDrop \*(rq
160 for this information. If the value found is
161 not absolute, then it is interpreted relative to the user's
163 directory. If the value is not found, then
165 will look in the standard system location for the user's maildrop.
171 to be quiet and not ask any questions at all. This is useful for putting
173 in the background and going on to other things.
178 will normally check local mail drops for mail, as covered above. But
180 .RI \*(lq pophost \*(rq
182 .RI \*(lq mts.conf \*(rq,
186 switch is given, or if the
188 environment variable is set, then
190 will query this POP service host for mail to incorporate. If
194 is specified as well, the commandline switch will override
195 the environment variable.
199 to assume that your account name on
200 the POP server is the same as your current username. To specify
201 a different username, use the
206 When using POP, you will normally need to type the password for
207 your account on the POP server, in order to retrieve your messages.
208 It is possible to automate this process by creating a
209 .RI \*(lq .netrc \*(rq
210 file containing your login account information for this POP server.
211 For each POP server, this file should have a line of the following
212 form. Replace the words
217 with your own account information.
229 .RI \*(lq .netrc \*(rq
230 file should be owned and readable only by you.
237 switch is considered. If given, then
239 simply uses the POP to
241 the user's maildrop from the POP service host to the named file. This switch
242 is provided for those users who prefer to use
244 to read their maildrops.
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.
253 has been compiled with APOP support, the
257 to use APOP rather than standard POP3 authentication. Under APOP, a
258 unique string (generally of the format
259 .RI < pid . timestamp @ hostname >
260 ) is announced by the POP server.
269 where digest is the MD5 hash of the unique string followed by a
270 `secret' shared by client and server, essentially equivalent to the user's
271 password (though an APOP-enabled POP3 server could have separate APOP and plain
272 POP3 passwords for a single user).
274 disables APOP in cases where it'd otherwise be used.
278 has been compiled with KPOP support, the
282 to use Kerberized POP rather than standard POP3 on a given invocation.
283 If POPSERVICE was also #defined to "kpop",
285 will be hardwired to always use KPOP.
289 has been compiled with SASL support, the
292 the use of SASL authentication. Depending on the SASL mechanism used, this
293 may require an additional password prompt from the user (but the
294 .RI \*(lq .netrc \*(rq
295 file can be used to store this password). The
297 switch can be used to select a particular SASL mechanism.
299 If SASL authentication is successful,
301 will attempt to negotiate a security layer for session encryption.
302 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
303 when viewing the POP transaction with the
311 .ta \w'/usr/local/nmh/etc/ExtraBigFileName 'u
312 ^$HOME/\&.mh\(ruprofile~^The user profile
313 ^%etcdir%/mts.conf~^nmh mts configuration file
314 ^%mailspool%/$USER~^Location of mail drop
317 .SH "PROFILE COMPONENTS"
321 .ta \w'ExtraBigProfileName 'u
322 ^Path:~^To determine the user's nmh directory
323 ^Alternate\-Mailboxes:~^To determine the user's mailboxes
324 ^Inbox:~^To determine the inbox, default \*(lqinbox\*(rq
325 ^Folder\-Protect:~^To set mode when creating a new folder
326 ^Msg\-Protect:~^To set mode when creating a new message and audit\-file
327 ^Unseen\-Sequence:~^To name sequences denoting unseen messages
331 mhmail(1), scan(1), mh\-mail(5), post(8)
335 .RB ` +folder "' defaulted by \*(lqInbox\*(rq above"
338 .RB ` \-format "' defaulted as described above"
340 .RB ` \-truncate "' if `" \-file " name' not given, `" \-notruncate "' otherwise"
341 .RB ` \-width "' defaulted to the width of the terminal"
348 The folder into which messages are being incorporated will become the
349 current folder. The first message incorporated will become the current
352 option is specified. This leaves the context ready for a
354 of the first new message.
359 switch must be interpreted as a single
360 token by the shell that invokes
362 Therefore, one must usually place the argument to this switch inside
projects / mmh / blob