4 .TH INC %manext1% "%nmhdate%" MH.6.8 [%nmhversion%]
6 inc \- incorporate new mail
15 .RB [ \-changecur " | " \-nochangecur ]
22 .RB [ \-silent " | " \-nosilent ]
23 .RB [ \-truncate " | " \-notruncate ]
46 incorporates mail from the user's incoming mail drop into
51 You may specify which folder to use with
53 If no folder is specified, then
55 will use either the folder given by a (non\-empty)
57 entry in the user's profile, or the folder named
58 .RI \*(lq inbox \*(rq.
59 If the specified (or default) folder doesn't
60 exist, the user will be queried prior to its creation.
62 When the new messages are incorporated into the folder, they are assigned
63 numbers starting with the next highest number for the folder. As the
64 messages are processed, a
66 listing of the new mail is produced.
68 If the user's profile contains a
69 .RI \*(lq "Msg\-Protect: nnn" \*(rq
71 will be used as the protection on the newly created messages, otherwise
74 default of 0644 will be used. For all subsequent operations
75 on these messages, this initially assigned protection will be preserved.
80 is specified (usually as a default
81 switch in the profile), then
83 will append a header line and a
84 line per message to the end of the specified audit\-file with the format:
89 <scan line for first message>
90 <scan line for second message>
95 This is useful for keeping track of volume and source of incoming mail.
102 may also produce audits to this (or another) file, perhaps with
103 .RI \*(lq Message\-Id \*(rq
104 information to keep an exact correspondence
106 .RI \*(lq Audit\-file \*(rq
107 will be in the user's nmh directory unless a full path is specified.
110 will incorporate even improperly formatted messages into the
111 user's nmh folder, inserting a blank line prior to the offending component
112 and printing a comment identifying the bad message.
114 In all cases, the user's mail drop will be zeroed, unless the
119 .RI \*(lq Unseen\-Sequence \*(rq
120 is present and non\-empty, then
122 will add each of the newly incorporated messages to
123 each sequence named by the profile entry.
125 will not zero each sequence prior to adding messages.
127 The interpretation of the
135 switches is the same as in
141 switch, one can direct
143 to incorporate messages from a file other than the user's maildrop.
144 Note that the name file will NOT be zeroed, unless the
148 If the environment variable
152 uses it as the location of the user's maildrop instead of the default
156 switch still overrides this, however). If this
157 environment variable is not set, then
159 will consult the profile entry
160 .RI \*(lq MailDrop \*(rq
161 for this information. If the value found is
162 not absolute, then it is interpreted relative to the user's
164 directory. If the value is not found, then
166 will look in the standard system location for the user's maildrop.
172 to be quiet and not ask any questions at all. This is useful for putting
174 in the background and going on to other things.
179 will normally check local mail drops for mail, as covered above. But
181 .RI \*(lq pophost \*(rq
183 .RI \*(lq mts.conf \*(rq,
187 switch is given, or if the
189 environment variable is set, then
191 will query this POP service host for mail to incorporate. If
195 is specified as well, the commandline switch will override
196 the environment variable.
200 to assume that your account name on
201 the POP server is the same as your current username. To specify
202 a different username, use the
207 When using POP, you will normally need to type the password for
208 your account on the POP server, in order to retrieve your messages.
209 It is possible to automate this process by creating a
210 .RI \*(lq .netrc \*(rq
211 file containing your login account information for this POP server.
212 For each POP server, this file should have a line of the following
213 form. Replace the words
218 with your own account information.
230 .RI \*(lq .netrc \*(rq
231 file should be owned and readable only by you.
238 will use the specified command to establish the connection to the POP
241 in the command will be substituted by the hostname to connect to.
248 switch is considered. If given, then
250 simply uses the POP to
252 the user's maildrop from the POP service host to the named file. This switch
253 is provided for those users who prefer to use
255 to read their maildrops.
257 For debugging purposes, you may give the switch
259 which will allow you to watch the POP transaction take place
260 between you and the POP server.
264 has been compiled with SASL support, the
267 the use of SASL authentication. Depending on the SASL mechanism used, this
268 may require an additional password prompt from the user (but the
269 .RI \*(lq .netrc \*(rq
270 file can be used to store this password). The
272 switch can be used to select a particular SASL mechanism.
274 If SASL authentication is successful,
276 will attempt to negotiate a security layer for session encryption.
277 Encrypted traffic is labelled with `(encrypted)' and `(decrypted)'
278 when viewing the POP transaction with the
286 .ta \w'%etcdir%/ExtraBigFileName 'u
287 ^$HOME/\&.mh\(ruprofile~^The user profile
288 ^%etcdir%/mts.conf~^nmh mts configuration file
289 ^%mailspool%/$USER~^Location of mail drop
292 .SH "PROFILE COMPONENTS"
296 .ta \w'ExtraBigProfileName 'u
297 ^Path:~^To determine the user's nmh directory
298 ^Alternate\-Mailboxes:~^To determine the user's mailboxes
299 ^Inbox:~^To determine the inbox, default \*(lqinbox\*(rq
300 ^Folder\-Protect:~^To set mode when creating a new folder
301 ^Msg\-Protect:~^To set mode when creating a new message and audit\-file
302 ^Unseen\-Sequence:~^To name sequences denoting unseen messages
306 mhmail(1), scan(1), mh\-mail(5), post(8)
310 .RB ` +folder "' defaulted by \*(lqInbox\*(rq above"
313 .RB ` \-format "' defaulted as described above"
315 .RB ` \-truncate "' if `" \-file " name' not given, `" \-notruncate "' otherwise"
316 .RB ` \-width "' defaulted to the width of the terminal"
323 The folder into which messages are being incorporated will become the
324 current folder. The first message incorporated will become the current
327 option is specified. This leaves the context ready for a
329 of the first new message.
334 switch must be interpreted as a single
335 token by the shell that invokes
337 Therefore, one must usually place the argument to this switch inside