![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to mh.me CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / share / doc / usd / 08.mh|
Return to mh.me CVS log | Up to [CSRG BSD Unix] / 43BSDReno / share / doc / usd / 08.mh |
1.1 root 1: .\" This file is automatically generated. Do not edit!
2: .if '\*(ZZ'-man' \{\
3: .SC MH 1
4: .NA
5: mh \- Message Handler
6: .SY
7: any \fIMH\fR command
8: .DE
9: \fIMH\fR is the name of a powerful message handling system.
10: Rather then being a single comprehensive program,
11: \fIMH\fR consists of a collection of fairly simple
12: single-purpose programs to send, receive, save,
13: and retrieve messages. The user should refer
14: to the \fIMH User's Manual\fR
15: and the pages for the \fIMH\fR
16: programs in the Unix Programmers Manual.
17:
18: Unlike \fImail\fR, the standard UNIX mail user interface program,
19: \fIMH\fR is not a closed system which must be explicitly run,
20: then exited when you wish to return to the shell.
21: You may freely intersperse \fIMH\fR commands with other shell commands,
22: allowing you to read and answer your mail while you have (for example)
23: a compilation running,
24: or search for a file or run programs as needed to find the answer to
25: someone's question before answering their mail.
26:
27: The rest of this manual entry is a quick tutorial which will teach you the
28: basics of \fIMH\fR.
29: You should read the manual entries for the individual programs for complete
30: documentation.
31:
32: To get started using \fIMH\fR, put the directory
33: \fB/usr/new/mh\fR on your \fB$PATH\fR.
34: This is best done in one of the files:
35: \fB\&.profile\fR, \fB\&.login\fR, or \fB\&.cshrc\fR
36: in your home directory.
37: (Check the manual entry for the shell you use,
38: in case you don't know how to do this.)
39: Run the \fIinc\fR command.
40: If you've never used \fIMH\fR before,
41: it will create the necessary default files and directories after
42: asking you if you wish it to do so.
43:
44: \fIinc\fR moves mail from your system maildrop
45: into your \fIMH\fR `+inbox' folder,
46: breaking it up into separate files
47: and converting it to \fIMH\fR format as it goes.
48: It prints one line for each message it processes,
49: containing the from field, the subject field
50: and as much of the first line of the message as will fit.
51: It leaves the first message it processes as your current message.
52: You'll need to run \fIinc\fR each time you wish to incorporate new mail
53: into your \fIMH\fR file.
54:
55: \fIscan\fR prints a list of the messages in your current folder.
56:
57: The commands:
58: \fIshow\fR, \fInext\fR, and \fIprev\fR
59: are used to read specific messages from the current folder.
60: \fIshow\fR displays the current message,
61: or a specific message, which may be specified by its number,
62: which you pass as an argument to \fIshow\fR.
63: \fInext\fR and \fIprev\fR display, respectively,
64: the message numerically after or before the current message.
65: In all cases, the message displayed becomes the current message.
66: If there is no current message,
67: \fIshow\fR may be called with an argument,
68: or \fInext\fR may be used to advance to the first message.
69:
70: \fIrmm\fR (remove message) deletes the current message.
71: It may be called with message numbers passed as arguments,
72: to delete specific messages.
73:
74: \fIrepl\fR is used to respond to the current message (by default).
75: It places you in the editor with a prototype response form.
76: While you're in the editor,
77: you may peruse the item you're responding to by reading the file \fB@\fR.
78: After completing your response,
79: type \fBl\fR to review it,
80: or \fBs\fR to send it.
81:
82: \fIcomp\fR allows you to compose a message by putting you in the editor on
83: a prototype message form,
84: and then lets you send it.
85:
86: All the \fIMH\fR commands may be run with the single argument: `\-help',
87: which causes them to print a list of the arguments they may be invoked with.
88:
89: Commands which take a message number as an argument
90: (\fIscan\fR, \fIshow\fR, \fIrepl\fR, ...)
91: also take one of the words:
92: \fIfirst\fR, \fIprev\fR, \fIcur\fR, \fInext\fR, or \fIlast\fR
93: to indicate (respectively) the first, previous, current, next, or last
94: message in the current folder (assuming they are defined).
95:
96: Commands which take a range of message numbers
97: (\fIrmm\fR, \fIscan\fR, \fIshow\fR, ...)
98: also take any of the abbreviations:
99: .sp
100: .in +5
101: .ti -3
102: .I <num1>-<num2>
103: - Indicates all messages in the range <num1> to <num2>, inclusive. The range
104: .B must
105: be nonempty.
106: .sp
107: .ti -3
108: .I <num>:+N
109: .ti -3
110: .I <num>:-N
111: - Up to
112: .I N
113: messages beginning with (or ending with) message
114: .I num.
115: .I Num
116: may be any of the pre-defined symbols:
117: .I first, prev, cur, next
118: or
119: .I last.
120: .sp
121: .ti -3
122: .I first:N
123: .ti -3
124: .I prev:N
125: .ti -3
126: .I next:N
127: .ti -3
128: .I last:N
129: - The first, previous, next or last
130: .I N
131: messages, if they exist.
132: .in -5
133:
134: There are many other possibilities such as creating multiple folders for
135: different topics, and automatically refiling messages according to subject,
136: source, destination, or content.
137: These are beyond the scope of this manual entry.
138:
139: Following is a list of all the \fIMH\fR commands:
140: .\}
141:
142: .nf
143: .in .5i
144: .ta 1.5i
145: ^ali (1)~^\- list mail aliases
146: ^anno (1)~^\- annotate messages
147: ^burst (1)~^\- explode digests into messages
148: ^comp (1)~^\- compose a message
149: ^dist (1)~^\- redistribute a message to additional addresses
150: ^folder (1)~^\- set/list current folder/message
151: ^folders (1)~^\- list all folders
152: ^forw (1)~^\- forward messages
153: ^inc (1)~^\- incorporate new mail
154: ^mark (1)~^\- mark messages
155: ^mhl (1)~^\- produce formatted listings of MH messages
156: ^mhmail (1)~^\- send or read mail
157: ^mhook (1)~^\- MH receive\-mail hooks
158: ^mhpath (1)~^\- print full pathnames of MH messages and folders
159: ^msgchk (1)~^\- check for messages
160: ^msh (1)~^\- MH shell (and BBoard reader)
161: ^next (1)~^\- show the next message
162: ^packf (1)~^\- compress a folder into a single file
163: ^pick (1)~^\- select messages by content
164: ^prev (1)~^\- show the previous message
165: ^prompter (1)~^\- prompting editor front end
166: ^rcvstore (1)~^\- incorporate new mail asynchronously
167: ^refile (1)~^\- file messages in other folders
168: ^repl (1)~^\- reply to a message
169: ^rmf (1)~^\- remove folder
170: ^rmm (1)~^\- remove messages
171: ^scan (1)~^\- produce a one line per message scan listing
172: ^send (1)~^\- send a message
173: ^show (1)~^\- show (list) messages
174: ^sortm (1)~^\- sort messages
175: ^vmh (1)~^\- visual front\-end to MH
176: ^whatnow (1)~^\- prompting front\-end for send
177: ^whom (1)~^\- report to whom a message would go
178: .if '\*(ZZ'-man' \{\
179: .sp 1
180: ^mh\-alias (5)~^\- alias file for MH message system
181: ^mh\-format (5)~^\- format file for MH message system
182: ^mh\-mail (5)~^\- message format for MH message system
183: ^mh\-profile (5)~^\- user customization for MH message system
184: .sp 1
185: ^ap (8)~^\- parse addresses 822\-style
186: ^conflict (8)~^\- search for alias/password conflicts
187: ^dp (8)~^\- parse dates 822\-style
188: ^install\-mh (8)~^\- initialize the MH environment
189: ^post (8)~^\- deliver a message
190: .\}
191: .fi
192: .re
193:
194: .if '\*(ZZ'-man' \{\
195: .Fi
196: ^/usr/new/mh~^directory containing \fIMH\fR commands
197: ^/usr/new/lib/mh~^\fIMH\fR library
198: .Sa
199: \fIThe Rand \fIMH\fR Message Handling System: User's Manual\fR,
200: .br
201: \fIThe Rand \fIMH\fR Message Handling System: Tutorial\fR,
202: .br
203: \fIThe Rand \fIMH\fR Message Handling System: The UCI BBoards Facility\fR,
204: .br
205: \fIMH.5: How to process 200 messages a day and still get some real work
206: done\fR
207: .br
208: .En
209: .\}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.