5 The Rand MH Message Handling System:
16 Wed May 21 21:04:08 PDT 1986
23 This document introduces the UCI version of the Rand MH
25 system to novice users. In particular, this tutorial discusses
27 how to read, send, reply to, and review mail; aspects of the
29 MH user profile affecting these activities; and other reference
34 Although this document is based on the standard MH
36 user manual[MRose85a], this document is meant to supple-
38 ment, not supersede, that lengthier work.
41 Comments concerning this documentation should be ad-
43 dressed to the Internet mailbox Bug-MH@ICS.UCI.EDU.
47 _____________________________________
48 Computer Mail: y MRose@NRTC.NORTHROP.COM, z JSweet@ICS.UCI.EDU.
51 The Rand MH Message Handling System:
61 The MH system described herein is based on the original Rand MH system.
63 It has been extensively developed (perhaps too much so) by Marshall Rose and
65 John Romine at the University of California, Irvine. Einar Stefferud, Jerry Sweet,
67 and Terry Domae provided numerous suggestions to improve the UCI version of
72 Parts of this document are taken from a Rand tutorial [SPayn85] by Sue
80 The Regents of the University of California issue the following disclaimer
82 concerning the UCI version of MH:
86 "Although each program has been tested by its contributor, no warranty, express or
87 implied, is made by the contributor or the University of California, as to the accuracy
88 and functioning of the program and related program material, nor shall the fact of
89 distribution constitute any such warranty, and no responsibility is assumed by the
90 contributor or the University of California in connection herewith."
96 This document assumes that you have no knowledge of MH. However, to use
98 MH you should have some familiarity with the UNIX1 operating system, particularly
100 with the way commands are given, how files are named, the jargon (e.g. shell,
102 argument, home directory, pathname), and how to use a text editor (such as ex, vi,
107 This tutorial covers only basic material. For additional information about
109 MH, consult the User's Manual [MRose85a]. Other documents of possible interest
111 to you include The UCI BBoards Facility [MRose84] and the MH Administrator's
117 _____________________________________
118 1 UNIX is a trademark of AT&T Bell Laboratories.
126 How To Use This Tutorial
128 Different typefaces and symbols are used in this document to denote the
130 kinds of things you (the user) must type on your keyboard.
133 1. The names of programs are given in text italics:
139 2. Arguments to programs are given in typewriter style, delimited by
147 3. UNIX pathnames are given in slanted roman:
153 4. Text giving a full example is presented in typewriter style:
159 The " " glyph is used to indicate an explicit space (the kind you make
161 with the space bar on your keyboard).
167 With MH you can send messages to other people on your system and read
169 messages that other people send to you. Depending on how things have been
171 set up on your system, it may be possible for you to send messages to people on
173 remote systems. You can also reply to messages that you have received, review
175 them, organize them in folders, and delete them.
178 MH differs from other mail programs in that it is composed of many small
180 programs instead of just one very large program. Among new users this sometimes
182 causes some confusion along the lines of "what program do I run?" With MH, you
184 use the shell to invoke one program at a time. This means that when you handle
186 mail, the entire power of the shell is at your disposal in addition to the facilities
188 that MH provides. In the beginning, this may not make much sense or may not
190 seem important. However, we have found that as new users of MH gain experience,
192 they find this style of interface to be very useful.
198 The most minimal list of MH commands that you can get by with is:
201 inc - incorporate mail (get new mail)
204 show - show the first message
207 next - show the next message
210 prev - show the previous message
213 comp - compose a new message to send
216 repl - reply to a received message
219 Comp and repl give enough prompting possibly to get you along. However,
221 it is suggested that you take the time to peruse this tutorial before leaping into
229 A message takes the form of a memorandum, and is composed of two
231 major parts: a header, which contains such information as ``To'' and ``From''
233 addresses, ``Subject'' , ``Date'' , etc.; and the body, which is the actual text of
235 the message. Each component in the header starts with a keyword followed by a
237 colon and additional information. For example, in the message:
240 Date: 10 Oct 84 17:41:14 EDT (Wed)
244 Subject: UCI Software Talk
246 From: UCI Portal (agent: Marshall Rose) <uci@udel-dewey>
253 there are four header items, and one line of text in the body. Note that a blank
255 line separates the body from the headers.
258 MH stores a message as an ordinary file in a UNIX directory. This directory is
260 called a folder. If you choose to keep and organize your messages, you may create
262 as many folders as you wish. There is no limit as to the number of messages in a
264 folder. Typically messages are numbered from 1 up. All of your personal folders,
266 along with some other information that MH needs to know, are kept in a special
268 directory called Mail under your home directory. Normally, MH manages these
270 files and directories automatically, so you needn't muck around with them directly
272 unless you really want to.
276 You won't have any folders until somebody sends mail to you, as a rule. If
278 you are anxious to try out MH, but no one has sent you mail yet, try sending mail
280 to yourself to start out with.
286 When you are notified that you have mail (usually when you log in), perhaps
294 then you know that messages are waiting in your maildrop. To read these messages,
296 you first have to incorporate the mail into your "in-box" by typing the command:
302 This incorporates the new mail from your mail drop to your in-box, which is a
304 folder named (naturally enough) `+inbox' . As inc incorporates your new mail, it
306 generates a scan listing of the mail:
308 Incorporating new mail into inbox...
310 2 + 10/10 WESTINE% USC-ISIF RFC 916 Now Available <<A new Request for Co
311 3 10/10 G B Reilly Gosling EMACS manual <<Marshall, I am lookin
312 4 10/11 WESTINE% USC-ISIF Internet Monthly Report
315 Each time inc is invoked, any new messages are added to the end of your
320 To read the first message, use the show command:
326 This displays the current message. To read each subsequent message, use the next
334 If you want to back up, the command prev shows the previous message. Another
336 way to read your messages is to name them all at once:
342 This command displays them all, one after the other. The `all' argument to show
344 above might also be replaced with `next' or `prev' , as in
352 which are respectively equivalent to the next and prev commands.
356 If you have had occasion to type inc more than once, then you will find that
358 ``show all'' is showing not only the new messages, but also the old messages
360 that you've already seen. Therefore, you might find it better to use
366 instead. This command displays messages from the current message (`cur' ) to the
368 last message (`last' ). Each time inc is invoked, it makes the first new message the
370 current message. It should be noted here that the name `all' given in a previous
372 example is equivalent to the message range `first-last' , where `first' is the
374 name of the first message in `+inbox' . Also, ``show'' by itself is equivalent to
381 As mentioned earlier, with the UNIX shell as your interface to MH, it becomes
383 easy to list a message on a line printer or to another file. For example,
389 lists all the messages in the current folder to the line printer.
392 To summarize, the preceding has introduced these important concepts:
394 folders (in particular, the `+inbox' folder), messages, message names (e.g.
396 `prev' , `next' , `cur' , `last' ), and message ranges (e.g. `cur-last' , `all' ).
398 More will be said about folders and messages in succeeding sections.
404 To send a message, you compose a message draft, either by replying to a
406 message that someone sent to you, or by creating a draft from scratch. The send
408 command is used after completing the final draft of a message, in the same way
410 that you mail a paper letter only after you are finished writing it. This is a common
412 source of confusion among new MH users who may have had experience with other
417 This section discusses how to originate messages and how to reply to messages
419 that were previously received, along with a word or two about addresses.
424 To create a message draft from scratch, use the comp program. You will be
426 prompted for the header components and then the body of the message. If you
428 make a mistake, you may correct it later with a text editor. The draft will be sent
430 only if you give an explicit send command, so you do not have to worry about the
432 draft getting away from you prematurely.
435 To start, you simply type:
442 To: First, the prompt `To:' appears. Here you type the address of the person
444 to whom you wish the message sent. If this person is on the same computer system
446 as you, then that person's login ID should serve as the address (e.g. `mrose' or
451 Here we digress briefly to discuss addresses. A full discussion of addresses
453 is beyond the scope of this tutorial, but it should be mentioned that there
455 are other kinds of addresses besides login IDs. To send messages to people
457 on remote systems, the usual way is to type `login-id@host' in the `To:'
459 component, as in `MRose@UCI-ICSA' . Examples of `host' names at UCI include
461 `uci-icsa' , `uci-icse' , and `uci-cip1' . Upper and lower case letters may be
463 used interchangeably. Sometimes a person's last name (e.g. `Rose' , `Sweet' ) can
465 be used instead of a login ID, but this cannot be relied upon in a world without
470 cc: After you have given an address to the `To:' prompt, you are prompted
472 for the `cc:' ("carbon copy"-an archaism) address. It is customary, but not
474 required, to put your own address here so that you get a copy of the message when
479 To put more than one address in the `To:' and `cc:' components, just use
481 a comma (",") between each address on a line.
484 Subject: The third prompt is for the `Subject:' component. Here a line
486 of any descriptive text will do. Once you have typed a line of text, a dashed line
488 is printed, and you are then expected to type the body of the message. End the
490 body with EOT (usually CTRL-D).
493 An example of a complete message draft, as it appears on your screen, might
502 Subject: UCI Software Talk
506 A presentation on the UCI software suite, including
508 the Rand/UCI Mail Handling System (MH), will be given
510 in CS220 on October 31st at 2:30 PM. Refreshments
512 will be served afterward.
521 (The "^D" does not appear in the draft.)
525 At this point, you are asked
531 This is known as being at What now? level. For now, there are probably only four
533 options that will interest you:
536 edit - edit the draft
539 list - list the draft on your screen
542 quit - quit, without sending the draft
545 send - send the draft, then quit
549 All of these options take various arguments, but only edit really needs an argument.
552 Edit: The edit option will let you edit the draft before sending it. If your
554 favorite text editor is vi, then you would use the edit option as:
560 Just specifying edit with no argument will only let you append text to the body
562 of the message draft. Another editor (e.g. vi, ex, emacs ) should really be run to
564 finish the draft up. When you leave the editor, you will come back to the What
566 now? level, where you can re-edit the draft, send it, list it, or simply quit without
568 sending the draft at all.
571 Caution: while in the editor, you should not delete colons in the headers or
573 change the spelling of `To:' , `cc:' , or `Subject:' ; and do not leave blank lines
575 between these lines. Feel free to change the addresses that you typed previously, or
577 to add these lines if they are missing. Do not delete the dashes that separate the
579 header lines from the text of the message. You should not add additional header
581 lines unless you understand precisely what you are doing. This means particularly
583 that you should not type or fill in a `From:' line. When the message is sent, the
585 system automatically adds this line. Also, you should not type a `Date:' line in
587 the header. When the message is sent, the system automatically adds the current
592 Quit: If you quit without sending the draft, the draft is saved in a file called
594 Mail/draft under your home directory. This file can be recalled later using the
596 `-use' argument to comp:
602 The What now? level will permit you to do further editing and to send the final
604 draft when you are ready.
608 Send: When it is time to send the draft on its way, use the send option by
610 itself. If there are any problems with the draft (for example, if one or more of the
612 people whom you specified in the `To:' and `cc:' components do not exist) then
614 you will be notified at this time.
619 To reply to a message, use the repl command. For example,
625 creates a reply to the current message. You may also reply to a specific message
627 (other than the current one) by giving a message number (e.g. `1' , `4' , etc.) or a
629 message name (e.g. `first' , `last' , `prev' ):
635 We haven't really introduced message numbers yet. They will be discussed in the
640 The process of replying to a message is very similar to composing a message
642 from scratch (see the previous section), but repl conveniently constructs and
644 displays the header of the reply draft for you. You need only type in the text of
646 the reply. An EOT (usually CTRL-D) indicates that you are done typing. If you
648 make a mistake, you may correct it later with a text editor. The draft will be sent
650 only if you give an explicit send command, so you do not have to worry about the
652 draft getting away from you prematurely.
655 An example of a complete reply draft, as it appears on your screen might be:
662 Subject: Re: UCI Software Talk
664 In-reply-to: Your message of 10 Oct 84 18:15:08 PDT (Wed).
675 (The "^D" does not appear in the draft.)
678 At this point, you are asked
684 This is known as being at What now? level. Refer to the previous section regarding
686 how to edit, display, or send the draft at this point.
690 As with comp, if you quit without sending the reply draft, the draft is saved
692 in a file called Mail/draft under your home directory. This file can be recalled later
694 using the `-use' argument to comp:
700 The What now? level will permit you to do further editing and to send the final
702 draft when you are ready.
708 The scan listing created by inc shows the message number, the date on which
710 the message was sent, the sender, and the subject of the message. If there is
712 sufficient space remaining on the line, the beginning of the text of the message is
714 displayed as well, preceded by two left angle brackets (" <<"). An example of a
718 1+ 10/10 WESTINE% USC-ISIF RFC 916 Now Available <<A new Request for Co
719 2 10/10 G B Reilly Gosling EMACS manual <<Marshall, I am lookin
720 3 10/11 WESTINE% USC-ISIF Internet Monthly Report
723 Note that all messages have message numbers.
726 To generate your own scan listing, use the scan program. Typing simply
732 will list all the messages in the current folder. To scan a subset of these messages,
734 you can specify the numbers of the messages that you consider interesting, e.g.,
740 Message names may be specified in addition to discrete message numbers. The
742 built-in message names recognized by MH are:
745 all_: all messages in the folder (`first-last' )
748 first_: the first message in the folder
751 last_: the last message in the folder
754 prev__: the message immediately before the current message
757 cur__: the current message
760 next__: the message immediately after the current message
764 Message ranges may be specified in addition to discrete message numbers or
766 names by separating the beginning and final message numbers with a dash ("-").
774 scans messages 5 through 10 inclusive. A range of messages may also be specified
776 by separating a beginning message number and a relative number of messages with
778 a colon (":"). For example,
784 scans the last three messages in the folder. Similarly,
790 scans the first three messages in the folder;
796 scans the next three messages;
802 scans the three messages beginning from the current message;
808 scans four messages beginning from message number 100.
811 To summarize, the important concepts that have been discussed in the
813 section are: message ranges, message numbers, and message names. When an MH
815 command is described as taking a `msg' argument, it accepts either a message
817 name or a message number. Most MH commands are described as taking `msgs'
819 arguments, meaning that more than one message or message range is accepted.
825 To delete a message, use the rmm program. By default, rmm deletes the
827 current message, but you can give rmm a list of messages to be removed as well.
829 There is no corresponding "unrmm" program, but clever users with a need will
831 find out how to change the way rmm works so that it simply moves messages to
833 another folder (say, `+wastebasket' ).
839 The possibility of having folders other than ``+inbox'' has been mentioned
841 previously. The methods for moving messages between folders and manipulating
843 folders are discussed here.
846 The refile command moves messages from a source folder to one or more
848 destination folders. By default, the current message is moved from the current
850 folder (typically `+inbox' ) to another folder specified as an argument to refile.
858 moves the current message from the current folder to the folder ``+todo'' . To
860 move messages from a folder other than the current folder, use the `-src +folder'
865 refile -src +todo last +save +notes
868 which moves the last message in the ``+todo'' folder to the folders ``+save''
870 and ``+notes'' . Note that this operation is a move, not a copy; it removes the
872 message from the source folder. To keep a copy in the source folder as well, use the
877 refile -link -src +todo last +save +notes
881 Whenever a folder argument is given to an MH command, that folder becomes
883 the current folder. To find out which folder is current, use the command
889 The inc command sets the current folder back to `+inbox' by default. To find out
891 about all of a user's folders, use the command
897 Since folders can contain other folders, the command
903 will recursively examine each folder for you.
906 To set the current folder, without doing anything else, use the folder program
908 with a folder argument. Hence,
914 makes ``+inbox'' the current folder.
918 After a using rmm and refile on a folder a number of times, there tend to be
920 gaps in the numbering sequence. To compress the numbers for the all messages in
931 You can customize the MH environment by editing your .mh_profile file.
933 Although there are lots of options, here are the most useful:
936 Editor___: lists the default editor that comp and repl should use. The default is
942 but another editor might be preferred.
945 editor-next____: lists the editor that should be used after the last edit with editor. Hence,
947 if you have a profile entry
953 after editing a draft with prompter, and being at What now? level, you
955 could say ``edit'' (instead of ``edit vi'' ) to continue to edit the
960 Msg-Protect________:Whenever MH creates a message (for example, with inc), this is the
962 octal protection mode that the message is created with. The default is
968 This protection mode permits all other users on the system to read
970 your messages. To maintain privacy, the mode 600 should be used.
972 Note that changing the mode in the profile does not change the modes
974 of messages that have been created already. Use the UNIX command
976 chmod to change the modes of your existing messages.
979 Folder-Protect______________:Whenever MH creates a folder (for example, with refile), this is the
981 octal mode that the folder is created with. The default is
987 This mode permits other users on the system to make access to specific
989 messages in your folders. To maintain stricter privacy, the mode 700
995 program____: Each MH program that reads user's .mh_profile file looks for an entry
997 beginning with its own name to determine its initial defaults. For
999 example, if you want the default editor for repl to be emacs, the line
1005 is sufficient. Command line arguments tend to override profile settings.
1007 Given the profile setting for repl above, if you invoked repl with
1013 repl would use the vi editor instead of emacs.
1016 signature____: When MH posts mail for you, it looks for this profile entry for your
1018 "real world" name. For example,
1021 signature: Marshall Rose
1024 The contents of the ``signature:'' entry in the profile should be a
1026 simple phrase, with no embedded periods (e.g. "Marshall T. Rose").
1030 Note that your profile resembles the header portion of a message. Be sure that it is
1032 properly formatted by placing a colon after each entry name, and keep each entry
1040 Now let's summarize the conventions that MH programs use:
1043 1. Any MH command that deals with messages can be given a `+folder'
1045 argument to say which folder to use. However, only one `+folder'
1047 argument may be given per command in most cases.
1050 2. If an MH command accepts a `msgs' argument, then any number of
1052 messages can be given to the command. The MH command will expand
1054 all the ranges and process each message, starting with the lowest
1056 numbered one and working its way to the message with the highest
1061 3. If an MH command accepts a `msg' argument, then at most one message
1066 4. Switches (options) to MH commands start with a dash. Unlike the
1068 standard UNIX convention, each switch consists of more than one
1070 character, for example `-header' . To minimize typing, only a unique
1072 abbreviation of the switch need be typed; thus for `-header' , `-hea'
1074 is probably sufficient, depending on the other switches accepted by the
1080 5. All MH commands have a `-help' switch, which must be spelled
1082 out fully. When an MH command encounters the `-help' switch, it
1084 prints out the syntax of the command, the switches that it accepts,
1086 and version information. In the list of switches, parentheses indicate
1088 required characters. For example, all `-help' switches will appear as
1090 `-(help)' , indicating that no abbreviation is accepted.
1093 6. Many MH switches have both on and off forms, such as `-format' and
1095 `-noformat' . In these cases, the last occurrence of the switch on the
1097 command line determines the setting of the option.
1100 7. All MH commands that read your MH profile operate the same way:
1102 first_, the profile is consulted for an entry matching the name with which
1104 the command was invoked; second___, if such an entry was found, then the
1106 command immediately uses the arguments listed; third__, any arguments
1108 on the command line are then interpreted. Since most switches have
1110 both on and off forms, it's easy to customize the default options for each
1112 MH command in the .mh_profile , and to override those defaults on the
1118 Online Documentation
1120 Each MH program has its own UNIX manual entry. For example, to get
1122 information about comp, type
1128 The manual entry for mh(1) lists all MH commands, while the manual entry for
1130 mh-chart (1) lists the syntax and switches for all MH commands.
1133 In addition, here are a few other manual entries might be found useful:
1136 mh-alias (5) to find out how aliases in MH work;
1139 mh-mail (5) to find out how MH stores and interprets messages (this manual entry
1141 explains all of the standard header components);
1144 mh-profile(5) to find out about the MH user-environment.
1147 The manual pages for MH are in the standard UNIX format, but contain
1149 additional sections unique to MH. Here's a summary of the sections one might find
1151 in an MH manual entry:
1154 Name command name and one-line description.
1157 Synopsis syntax of the command.
1159 All commands accept a `-help' switch.
1163 Description semantics of the command.
1166 Files files used by the command
1168 Almost always this includes .mh_profile .
1171 Profile entries in the .mh_profile used by the command;
1173 Components these do not include the profile entry for the command itself.
1176 See Also other UNIX manual entries (usually MH programs) that are related to
1181 Defaults default arguments for the command
1183 If the command takes a `+folder' argument, this defaults to the
1185 current folder. If the command takes a `msg' argument, this defaults
1187 to the current message. If the command takes a `msgs' argument, this
1189 defaults to the current message or all messages, depending on which one
1194 Context changes to your MH context made by the command.
1197 Hints Helpful hints discussing the easy way to do things.
1200 History A historical perspective on why MH works the way it does.
1203 Bugs Too embarrassing to mention.
1209 Obviously, not all MH manual entries may have all of these sections.
1215 If problems are encountered with an MH program, the problems should be
1217 reported to the local maintainers of MH. When doing this, the name of the program
1219 should be reported, along with the version information for the program. To find
1221 out what version of an MH program is being run, invoke the program with the
1223 `-help' switch. In addition to listing the syntax of the command, the program
1225 will list information pertaining to its version. This information includes the version
1227 of MH, the host it was generated on, the date the program was loaded, and the
1229 configuration options in effect when MH was generated. For example,
1232 version: MH 6.1 #1[UCI] (gremlin) of Wed Nov 6 01:13:53 PST 1985
1234 options: [BSD42] [MHE] [NETWORK] [SENDMTS] [MMDFII] [SMTP] [POP]
1237 The ``6.1 # 1[UCI]'' indicates that the program is from the UCI mh.6
1239 version of MH. The program was generated on the host ``gremlin'' on
1241 ``Wed Nov 6 01:13:53 PST 1985'' . It's usually a good idea to send the output
1243 of the `-help' switch along with your report.
1247 If there is no local MH maintainer, try the address Bug-MH. If that fails, use
1249 the Internet mailbox Bug-MH@UCI.ARPA.
1255 There are myriad aspects of MH that this tutorial hasn't touched upon. Here
1257 are a few to whet your appetite:
1260 1. user-defined sequences
1262 Define meaningful message names and shorten type-in considerably (see
1264 pick (1) for details).
1269 Maintain a folder of drafts so that more than one draft can be edited
1271 at a time, and allow a draft to be edited over several UNIX sessions
1273 independently of other drafts (see the Advanced Features section of
1275 the MH user's manual for details).
1280 Post a draft in the background and immediately free your terminal for
1282 other activities (see the Advanced Features section of the MH user's
1284 manual for details).
1289 Maintain one or more alias files containing the addresses of the people
1291 frequently (or infrequently) sent to. This lets you shorten type-in of
1293 addressees and saves you from looking up their addresses all the time.
1295 (see mh-alias (5) for details).
1303 [MRose84] M.T. Rose. The Rand MH Message Handling System: The UCI
1305 BBoards Facility. Department of Computer and Information Sciences,
1307 University of Delaware (October, 1984).
1311 [MRose85a] M.T. Rose, J.L. Romine. The Rand MH Message Handling System:
1313 User's Manual. UCI Version. Department of Information and Computer
1315 Science, University of California, Irvine (January, 1985).
1319 [MRose85b] M.T. Rose. The Rand MH Message Handling System: Administrator's
1321 Guide. UCI Version, MH Classic. Northrop Corporation, Research and
1323 Technology Center (July, 1985).
1327 [SPayn85] S. Payne MH5: Electronic Mail. Rand Note #N-2281-RCC. The
1329 Rand Computation Center, Rand, 1700 Main St., Santa Monica, CA
1331 90406-2138 (May, 1985).
1342 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1344 Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1346 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1348 How To Use This Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1350 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1352 Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1354 Messages and Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1356 Reading New Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1358 Sending Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1360 Originating Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1362 Replying to Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1364 Scanning Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1366 Deleting Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1368 Filing Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1370 The Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1372 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1374 Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1376 Reporting Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
1378 More on MH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1380 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1384 _____________________________________
1385 This document (version #2.8) was TEXset April 12, 1990 with DISS.STY v103.
projects / nmh / blob