Whitespace cleanup for last commit, and a few other areas with very long
lines. No content change.
This commit is contained in:
parent
f8e2c388ef
commit
9a9ef91ab4
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=18486
1 changed files with 215 additions and 174 deletions
|
|
@ -36,41 +36,46 @@
|
||||||
</legalnotice>
|
</legalnotice>
|
||||||
|
|
||||||
<abstract>
|
<abstract>
|
||||||
<para>This document contains an introduction to using <application>MH</application> on
|
<para>This document contains an introduction to using
|
||||||
FreeBSD</para>
|
<application>MH</application> on FreeBSD</para>
|
||||||
</abstract>
|
</abstract>
|
||||||
</articleinfo>
|
</articleinfo>
|
||||||
|
|
||||||
<sect1 id="mhintro">
|
<sect1 id="mhintro">
|
||||||
<title>Introduction</title>
|
<title>Introduction</title>
|
||||||
|
|
||||||
<para><application>MH</application> started back in 1977 at the RAND Corporation, where the
|
<para><application>MH</application> started back in 1977 at the
|
||||||
initial philosophies behind <application>MH</application> were developed. <application>MH</application> is not so much
|
RAND Corporation, where the initial philosophies behind
|
||||||
a monolithic email program but a philosophy about how best to
|
<application>MH</application> were
|
||||||
develop tools for reading email. The <application>MH</application> developers have done a
|
developed. <application>MH</application> is not so much a
|
||||||
great job adhering to the <acronym>KISS</acronym> principle: Keep It
|
monolithic email program but a philosophy about how best to
|
||||||
|
develop tools for reading email. The
|
||||||
|
<application>MH</application> developers have done a great job
|
||||||
|
adhering to the <acronym>KISS</acronym> principle: Keep It
|
||||||
Simple Stupid. Rather than have one large program for reading,
|
Simple Stupid. Rather than have one large program for reading,
|
||||||
sending and handling email they have written specialized
|
sending and handling email they have written specialized
|
||||||
programs for each part of your email life. One might liken <application>MH</application> to
|
programs for each part of your email life. One might liken
|
||||||
the specialization that one finds in insects and nature. Each
|
<application>MH</application> to the specialization that one
|
||||||
tool in <application>MH</application> does one thing, and does it very well.</para>
|
finds in insects and nature. Each tool in
|
||||||
|
<application>MH</application> does one thing, and does it very
|
||||||
|
well.</para>
|
||||||
|
|
||||||
<para>Beyond just the various tools that one uses to handle their
|
<para>Beyond just the various tools that one uses to handle their
|
||||||
email <application>MH</application> has done an excellent job keeping the configuration of
|
email <application>MH</application> has done an excellent job
|
||||||
each of these tools consistent and uniform. In fact, if you are
|
keeping the configuration of each of these tools consistent and
|
||||||
not quite sure how something is supposed to work or what the
|
uniform. In fact, if you are not quite sure how something is
|
||||||
arguments for some command are supposed to be, then you can
|
supposed to work or what the arguments for some command are
|
||||||
generally guess and be right. Each <application>MH</application> command is consistent
|
supposed to be, then you can generally guess and be right. Each
|
||||||
about how it handles reading the configuration files and how it
|
<application>MH</application> command is consistent about how it
|
||||||
takes arguments on the command line. One useful thing to
|
handles reading the configuration files and how it takes
|
||||||
remember is that you can always add a <option>-help</option> to
|
arguments on the command line. One useful thing to remember is
|
||||||
the command to have it display the options for that
|
that you can always add a <option>-help</option> to the command
|
||||||
command.</para>
|
to have it display the options for that command.</para>
|
||||||
|
|
||||||
<para>The first thing that you need to do is to make sure that you
|
<para>The first thing that you need to do is to make sure that you
|
||||||
have installed the <application>MH</application> package on your FreeBSD machine. If you
|
have installed the <application>MH</application> package on your
|
||||||
installed from CDROM you should be able to execute the following
|
FreeBSD machine. If you installed from CDROM you should be able
|
||||||
to load <application>MH</application>:
|
to execute the following to load <application>MH</application>:
|
||||||
|
|
||||||
<informalexample>
|
<informalexample>
|
||||||
<screen>&prompt.root; <userinput>pkg_add /cdrom/packages/mh-6.8.3.tgz</userinput></screen>
|
<screen>&prompt.root; <userinput>pkg_add /cdrom/packages/mh-6.8.3.tgz</userinput></screen>
|
||||||
|
|
@ -84,50 +89,60 @@
|
||||||
URL="ftp://louie.udel.edu/">louie.udel.edu</ulink>.</para>
|
URL="ftp://louie.udel.edu/">louie.udel.edu</ulink>.</para>
|
||||||
|
|
||||||
<para>This primer is not a full comprehensive explanation of how
|
<para>This primer is not a full comprehensive explanation of how
|
||||||
<application>MH</application> works. This is just intended to get you started on the road
|
<application>MH</application> works. This is just intended to
|
||||||
to happier, faster mail reading. You should read the manual pages
|
get you started on the road to happier, faster mail reading. You
|
||||||
for the various commands. You might also want to read the <ulink
|
should read the manual pages for the various commands. You might
|
||||||
URL="news:comp.mail.mh">comp.mail.mh</ulink> newsgroup. Also
|
also want to read the <ulink
|
||||||
you can read the <ulink
|
URL="news:comp.mail.mh">comp.mail.mh</ulink> newsgroup. Also you
|
||||||
URL="http://www.faqs.org/faqs/mail/mh-faq/">FAQ for <application>MH</application></ulink>.
|
can read the <ulink
|
||||||
The best resource for <application>MH</application> is <ulink
|
URL="http://www.faqs.org/faqs/mail/mh-faq/">FAQ for
|
||||||
URL="http://www.ics.uci.edu/~mh/book/">Jerry Peek's <application>MH</application> &
|
<application>MH</application></ulink>. The best resource for
|
||||||
nmh: Email for Users & Programmers</ulink>.</para>
|
<application>MH</application> is <ulink
|
||||||
|
URL="http://www.ics.uci.edu/~mh/book/">Jerry Peek's
|
||||||
|
<application>MH</application> & nmh: Email for Users &
|
||||||
|
Programmers</ulink>.</para>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
<sect1>
|
<sect1>
|
||||||
<title>Reading Mail</title>
|
<title>Reading Mail</title>
|
||||||
|
|
||||||
<para>This section covers how to use <command>inc</command>,
|
<para>This section covers how to use <command>inc</command>,
|
||||||
<command>show</command>, <command>scan</command>, <command>next</command>,
|
<command>show</command>, <command>scan</command>,
|
||||||
<command>prev</command>, <command>rmm</command>, <command>rmf</command>, and
|
<command>next</command>, <command>prev</command>,
|
||||||
<command>msgchk</command>. One of the best things about <application>MH</application> is the
|
<command>rmm</command>, <command>rmf</command>, and
|
||||||
consistent interface between programs. One thing to keep in
|
<command>msgchk</command>. One of the best things about
|
||||||
mind when using these commands is how to specify message lists.
|
<application>MH</application> is the consistent interface
|
||||||
In the case of <command>inc</command> this does not really make any
|
between programs. One thing to keep in mind when using these
|
||||||
sense but with commands like <command>show</command> it is useful to
|
commands is how to specify message lists. In the case of
|
||||||
|
<command>inc</command> this does not really make any sense but
|
||||||
|
with commands like <command>show</command> it is useful to
|
||||||
know. </para>
|
know. </para>
|
||||||
|
|
||||||
<para>A message list can consist of something like <parameter>23
|
<para>A message list can consist of something like <parameter>23
|
||||||
20 16</parameter> which will act on messages 23, 20 and 16. This is
|
20 16</parameter> which will act on messages 23, 20 and
|
||||||
fairly simple but you can do more useful things like
|
16. This is fairly simple but you can do more useful things
|
||||||
<parameter>23-30</parameter> which will act on all the messages between
|
like <parameter>23-30</parameter> which will act on all the
|
||||||
23 and 30. You can also specify something like
|
messages between 23 and 30. You can also specify something
|
||||||
<parameter>cur:10</parameter> which will act on the current message and
|
like <parameter>cur:10</parameter> which will act on the
|
||||||
the next 9 messages. The <parameter>cur</parameter>, <parameter>last</parameter>,
|
current message and the next 9 messages. The
|
||||||
and <parameter>first</parameter> messages are special messages that refer
|
<parameter>cur</parameter>, <parameter>last</parameter>, and
|
||||||
to the current, last or first message in the folder.</para>
|
<parameter>first</parameter> messages are special messages
|
||||||
|
that refer to the current, last or first message in the
|
||||||
|
folder.</para>
|
||||||
|
|
||||||
<sect2 id="inc">
|
<sect2 id="inc">
|
||||||
<title><command>inc</command>, <command>msgchk</command>—read in your
|
<title><command>inc</command>,
|
||||||
new email or check it</title>
|
<command>msgchk</command>—read in your new email or
|
||||||
|
check it</title>
|
||||||
|
|
||||||
<para>If you just type in <userinput>inc</userinput> and hit
|
<para>If you just type in <userinput>inc</userinput> and hit
|
||||||
<keycap>return</keycap> you will be well on your way to getting
|
<keycap>return</keycap> you will be well on your way to
|
||||||
started with <application>MH</application>. The first time you run <command>inc</command> it
|
getting started with <application>MH</application>. The first
|
||||||
will setup your account to use all the <application>MH</application> defaults and ask you
|
time you run <command>inc</command> it will setup your account
|
||||||
about creating a <filename>Mail</filename> directory under your HOME directory. If you have mail waiting to
|
to use all the <application>MH</application> defaults and ask
|
||||||
be downloaded you will see something that looks like:</para>
|
you about creating a <filename>Mail</filename> directory under
|
||||||
|
your HOME directory. If you have mail waiting to be downloaded
|
||||||
|
you will see something that looks like:</para>
|
||||||
|
|
||||||
<informalexample>
|
<informalexample>
|
||||||
<screen> 29 01/15 Doug White Re: Another Failed to boot problem<<On Mon, 15 J
|
<screen> 29 01/15 Doug White Re: Another Failed to boot problem<<On Mon, 15 J
|
||||||
|
|
@ -144,22 +159,25 @@
|
||||||
you.</para>
|
you.</para>
|
||||||
|
|
||||||
<para>A lot of people like to use POP for grabbing their email.
|
<para>A lot of people like to use POP for grabbing their email.
|
||||||
<application>MH</application> can do POP to grab your email. You will need to give
|
<application>MH</application> can do POP to grab your
|
||||||
<command>inc</command> a few command line arguments.</para>
|
email. You will need to give <command>inc</command> a few
|
||||||
|
command line arguments.</para>
|
||||||
|
|
||||||
<informalexample>
|
<informalexample>
|
||||||
<screen>&prompt.user; <userinput>inc -host mail.pop.org -user <replaceable>username</replaceable> -norpop</userinput></screen>
|
<screen>&prompt.user; <userinput>inc -host mail.pop.org -user <replaceable>username</replaceable> -norpop</userinput></screen>
|
||||||
</informalexample>
|
</informalexample>
|
||||||
|
|
||||||
<para>That tells <command>inc</command> to go to
|
<para>That tells <command>inc</command> to go to
|
||||||
<parameter>mail.pop.org</parameter> to download your email, and that
|
<parameter>mail.pop.org</parameter> to download your email,
|
||||||
your username on their system is <replaceable>username</replaceable>. The
|
and that your username on their system is
|
||||||
<option>-norpop</option> option tells <command>inc</command> to use
|
<replaceable>username</replaceable>. The
|
||||||
plain POP3 for downloading your email. <application>MH</application> has support for a
|
<option>-norpop</option> option tells <command>inc</command>
|
||||||
few different dialects of POP. More than likely you will never
|
to use plain POP3 for downloading your
|
||||||
|
email. <application>MH</application> has support for a few
|
||||||
|
different dialects of POP. More than likely you will never
|
||||||
ever need to use them though. While you can do more complex
|
ever need to use them though. While you can do more complex
|
||||||
things with <command>inc</command> such as audit files and scan format files this
|
things with <command>inc</command> such as audit files and
|
||||||
will get you going.</para>
|
scan format files this will get you going.</para>
|
||||||
|
|
||||||
<para>The <command>msgchk</command> command is used to get information
|
<para>The <command>msgchk</command> command is used to get information
|
||||||
on whether or not you have new email. <command>msgchk</command> takes
|
on whether or not you have new email. <command>msgchk</command> takes
|
||||||
|
|
@ -233,10 +251,11 @@
|
||||||
<title><command>rmm</command> and <command>rmf</command>—remove the
|
<title><command>rmm</command> and <command>rmf</command>—remove the
|
||||||
current message or folder</title>
|
current message or folder</title>
|
||||||
|
|
||||||
<para><command>rmm</command> is used to remove a mail message. The
|
<para><command>rmm</command> is used to remove a mail
|
||||||
default is typically to not actually remove the message but to
|
message. The default is typically to not actually remove the
|
||||||
rename the file to one that is ignored by the <application>MH</application> commands. You
|
message but to rename the file to one that is ignored by the
|
||||||
will periodically need to go through and physically delete the
|
<application>MH</application> commands. You will periodically
|
||||||
|
need to go through and physically delete the
|
||||||
<quote>removed</quote> messages.</para>
|
<quote>removed</quote> messages.</para>
|
||||||
|
|
||||||
<para>The <command>rmf</command> command is used to remove folders.
|
<para>The <command>rmf</command> command is used to remove folders.
|
||||||
|
|
@ -326,10 +345,11 @@ which I am probably the guilty party).</screen>
|
||||||
</informalexample>
|
</informalexample>
|
||||||
|
|
||||||
<para>Then if I wanted to read message number 27 I would do a
|
<para>Then if I wanted to read message number 27 I would do a
|
||||||
<userinput>show 27</userinput> and it would be displayed. As you can
|
<userinput>show 27</userinput> and it would be displayed. As
|
||||||
probably tell from this sample session <application>MH</application> is pretty easy to
|
you can probably tell from this sample session
|
||||||
use and looking through emails and displaying them is fairly
|
<application>MH</application> is pretty easy to use and
|
||||||
intuitive and easy.</para>
|
looking through emails and displaying them is fairly intuitive
|
||||||
|
and easy.</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
|
|
@ -338,43 +358,52 @@ which I am probably the guilty party).</screen>
|
||||||
|
|
||||||
<para>Anybody who gets lots of email definitely wants to be able
|
<para>Anybody who gets lots of email definitely wants to be able
|
||||||
to prioritize, stamp, brief, de-brief, and number their emails
|
to prioritize, stamp, brief, de-brief, and number their emails
|
||||||
in a variety of different ways. <application>MH</application> can do this better than just
|
in a variety of different ways. <application>MH</application>
|
||||||
about anything. One thing that we have not really talked about is
|
can do this better than just about anything. One thing that we
|
||||||
the concept of folders. You have undoubtedly come across the
|
have not really talked about is the concept of folders. You have
|
||||||
folders concept using other email programs. <application>MH</application> has folders too.
|
undoubtedly come across the folders concept using other email
|
||||||
<application>MH</application> can even do sub-folders of a folder. One thing you should
|
programs. <application>MH</application> has folders too.
|
||||||
keep in mind with <application>MH</application> is that when you ran <command>inc</command> for
|
<application>MH</application> can even do sub-folders of a
|
||||||
the first time and it asked you if it could create a
|
folder. One thing you should keep in mind with
|
||||||
<filename>Mail</filename> directory it began storing everything in that
|
<application>MH</application> is that when you ran
|
||||||
directory. If you look at that directory you will find a
|
<command>inc</command> for the first time and it asked you if it
|
||||||
directory named <filename>inbox</filename>. The <filename>inbox</filename>
|
could create a <filename>Mail</filename> directory it began
|
||||||
|
storing everything in that directory. If you look at that
|
||||||
|
directory you will find a directory named
|
||||||
|
<filename>inbox</filename>. The <filename>inbox</filename>
|
||||||
directory houses all of your incoming mail that has not been
|
directory houses all of your incoming mail that has not been
|
||||||
thrown anywhere else.</para>
|
thrown anywhere else.</para>
|
||||||
|
|
||||||
<para>Whenever you create a new folder a new directory is going to
|
<para>Whenever you create a new folder a new directory is going to
|
||||||
be created underneath your <application>MH</application> <filename>Mail</filename> directory, and
|
be created underneath your <application>MH</application>
|
||||||
messages in that folder are going to be stored in that
|
<filename>Mail</filename> directory, and messages in that folder
|
||||||
directory. When a new email message comes, it is thrown
|
are going to be stored in that directory. When a new email
|
||||||
into your <filename>inbox</filename> directory with a file name that is
|
message comes, it is thrown into your <filename>inbox</filename>
|
||||||
equivalent to the message number. So even if you did not have
|
directory with a file name that is equivalent to the message
|
||||||
any of the <application>MH</application> tools to read your email you could still use
|
number. So even if you did not have any of the
|
||||||
standard &unix; commands to munge around in those directories and
|
<application>MH</application> tools to read your email you could
|
||||||
just more your files. It is this simplicity that really gives you
|
still use standard &unix; commands to munge around in those
|
||||||
a lot of power with what you can do with your email.</para>
|
directories and just more your files. It is this simplicity that
|
||||||
|
really gives you a lot of power with what you can do with your
|
||||||
|
email.</para>
|
||||||
|
|
||||||
<para>Just as you can use message lists like <parameter>23 16
|
<para>Just as you can use message lists like <parameter>23 16
|
||||||
42</parameter> with most <application>MH</application> commands there is a folder option you can
|
42</parameter> with most <application>MH</application>
|
||||||
specify with just about every <application>MH</application> command. If you do a
|
commands there is a folder option you can specify with just
|
||||||
<command>scan +freebsd</command> it will scan your <filename>freebsd</filename>
|
about every <application>MH</application> command. If you do a
|
||||||
folder, and your current folder will be changed to
|
<command>scan +freebsd</command> it will scan your
|
||||||
<filename>freebsd</filename>. If you do a <command>show +freebsd 23 16
|
<filename>freebsd</filename> folder, and your current folder
|
||||||
42</command>, <command>show</command> is going to switch to your
|
will be changed to <filename>freebsd</filename>. If you do a
|
||||||
<filename>freebsd</filename> folder and display messages 23, 16 and 42.
|
<command>show +freebsd 23 16 42</command>,
|
||||||
So remember that <option>+<replaceable>folder</replaceable></option> syntax. You
|
<command>show</command> is going to switch to your
|
||||||
will need to make sure you use it to make commands process
|
<filename>freebsd</filename> folder and display messages 23,
|
||||||
different folders. Remember you default folder for mail is
|
16 and 42. So remember that
|
||||||
<filename>inbox</filename> so doing a <command>folder +inbox</command> should
|
<option>+<replaceable>folder</replaceable></option>
|
||||||
always get you back to your mail. Of course, in <application>MH</application>'s infinite
|
syntax. You will need to make sure you use it to make commands
|
||||||
|
process different folders. Remember you default folder for
|
||||||
|
mail is <filename>inbox</filename> so doing a <command>folder
|
||||||
|
+inbox</command> should always get you back to your mail. Of
|
||||||
|
course, in <application>MH</application>'s infinite
|
||||||
flexibility this can be changed but most places have probably
|
flexibility this can be changed but most places have probably
|
||||||
left it as <command>inbox</command>.</para>
|
left it as <command>inbox</command>.</para>
|
||||||
|
|
||||||
|
|
@ -414,12 +443,13 @@ which I am probably the guilty party).</screen>
|
||||||
<para>This will show you the same messages you just did not have
|
<para>This will show you the same messages you just did not have
|
||||||
to work as hard to do it. The <option>-seq</option> option is
|
to work as hard to do it. The <option>-seq</option> option is
|
||||||
really an abbreviation of <option>-sequence</option> and
|
really an abbreviation of <option>-sequence</option> and
|
||||||
<command>pick</command> is just a sequence which contains the message
|
<command>pick</command> is just a sequence which contains the
|
||||||
numbers that matched. You can use sequences with just about
|
message numbers that matched. You can use sequences with just
|
||||||
any <application>MH</application> command. So you could have done an <command>rmm pick</command>
|
about any <application>MH</application> command. So you could
|
||||||
and all those messages would be removed instead. You sequence
|
have done an <command>rmm pick</command> and all those
|
||||||
can be named anything. If you run pick again it will overwrite
|
messages would be removed instead. You sequence can be named
|
||||||
the old sequence if you use the same name.</para>
|
anything. If you run pick again it will overwrite the old
|
||||||
|
sequence if you use the same name.</para>
|
||||||
|
|
||||||
<para>Doing a <command>pick -search</command> can be a bit more
|
<para>Doing a <command>pick -search</command> can be a bit more
|
||||||
time consuming than just searching for message from someone,
|
time consuming than just searching for message from someone,
|
||||||
|
|
@ -513,10 +543,11 @@ which I am probably the guilty party).</screen>
|
||||||
<screen>&prompt.user; <userinput>pick -to freebsd-hackers -or -cc freebsd-hackers</userinput></screen>
|
<screen>&prompt.user; <userinput>pick -to freebsd-hackers -or -cc freebsd-hackers</userinput></screen>
|
||||||
</informalexample>
|
</informalexample>
|
||||||
|
|
||||||
<para>That will grab all the email in your <filename role="directory">inbox</filename> that was sent
|
<para>That will grab all the email in your <filename
|
||||||
to freebsd-hackers or cc'd to that list. The brace options
|
role="directory">inbox</filename> that was sent to
|
||||||
allow you to group search criteria together. This is sometimes
|
freebsd-hackers or cc'd to that list. The brace options allow
|
||||||
very necessary as in the following example</para>
|
you to group search criteria together. This is sometimes very
|
||||||
|
necessary as in the following example</para>
|
||||||
|
|
||||||
<informalexample>
|
<informalexample>
|
||||||
<screen>&prompt.user; <userinput>pick -lbrace -to freebsd-hackers -and
|
<screen>&prompt.user; <userinput>pick -lbrace -to freebsd-hackers -and
|
||||||
|
|
@ -531,10 +562,11 @@ which I am probably the guilty party).</screen>
|
||||||
the subject line. Ordinarily you might have to worry about
|
the subject line. Ordinarily you might have to worry about
|
||||||
something called operator precedence. Remember in math how you
|
something called operator precedence. Remember in math how you
|
||||||
evaluate from left to right and you do multiplication and
|
evaluate from left to right and you do multiplication and
|
||||||
division first and addition and subtraction second? <application>MH</application> has the
|
division first and addition and subtraction second?
|
||||||
same type of rules for <command>pick</command>. It is fairly complex
|
<application>MH</application> has the same type of rules for
|
||||||
so you might want to study the manual page. This document is just
|
<command>pick</command>. It is fairly complex so you might
|
||||||
to help you get acquainted with <application>MH</application>.</para>
|
want to study the manual page. This document is just to help
|
||||||
|
you get acquainted with <application>MH</application>.</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2>
|
<sect2>
|
||||||
|
|
@ -543,14 +575,15 @@ which I am probably the guilty party).</screen>
|
||||||
maintenance</title>
|
maintenance</title>
|
||||||
|
|
||||||
<para>There are three programs which are primarily just for
|
<para>There are three programs which are primarily just for
|
||||||
manipulating your folders. The <command>folder</command> program is
|
manipulating your folders. The <command>folder</command>
|
||||||
used to switch between folders, pack them, and list them. At
|
program is used to switch between folders, pack them, and list
|
||||||
its simplest level you can do a <command>folder
|
them. At its simplest level you can do a <command>folder
|
||||||
+<replaceable>newfolder</replaceable></command> and you will be switched into
|
+<replaceable>newfolder</replaceable></command> and you will
|
||||||
<replaceable>newfolder</replaceable>. From there on out all your <application>MH</application>
|
be switched into <replaceable>newfolder</replaceable>. From
|
||||||
commands like <command>comp</command>, <command>repl</command>,
|
there on out all your <application>MH</application> commands
|
||||||
<command>scan</command>, and <command>show</command> will act on that
|
like <command>comp</command>, <command>repl</command>,
|
||||||
<command>newfolder</command> folder.</para>
|
<command>scan</command>, and <command>show</command> will act
|
||||||
|
on that <command>newfolder</command> folder.</para>
|
||||||
|
|
||||||
<para>Sometimes when you are reading and deleting messages you
|
<para>Sometimes when you are reading and deleting messages you
|
||||||
will develop <quote>holes</quote> in your folders. If you do a
|
will develop <quote>holes</quote> in your folders. If you do a
|
||||||
|
|
@ -605,22 +638,25 @@ which I am probably the guilty party).</screen>
|
||||||
<title>Sending Mail</title>
|
<title>Sending Mail</title>
|
||||||
|
|
||||||
<para>Email is a two way street for most people so you want to be
|
<para>Email is a two way street for most people so you want to be
|
||||||
able to send something back. The way <application>MH</application> handles sending mail can
|
able to send something back. The way
|
||||||
be a bit difficult to follow at first, but it allows for
|
<application>MH</application> handles sending mail can be a bit
|
||||||
incredible flexibility. The first thing <application>MH</application> does is to copy a
|
difficult to follow at first, but it allows for incredible
|
||||||
components file into your outgoing email. A components file is
|
flexibility. The first thing <application>MH</application> does
|
||||||
basically a skeleton email letter with stuff like the <literal>To:</literal> and
|
is to copy a components file into your outgoing email. A
|
||||||
<literal>Subject:</literal> headers already in it. You are then sent into your
|
components file is basically a skeleton email letter with stuff
|
||||||
editor where you fill in the header information and then type
|
like the <literal>To:</literal> and <literal>Subject:</literal>
|
||||||
the body of your message below the dashed lines in the message.
|
headers already in it. You are then sent into your editor where
|
||||||
When you leave the editor, the <command>whatnow</command> program is run. When you are at the
|
you fill in the header information and then type the body of
|
||||||
<prompt>What now?</prompt> prompt you can tell it to
|
your message below the dashed lines in the message. When you
|
||||||
<command>send</command>, <command>list</command>, <command>edit</command>,
|
leave the editor, the <command>whatnow</command> program is run.
|
||||||
<command>push</command>, and <command>quit</command>. Most
|
When you are at the <prompt>What now?</prompt> prompt you can
|
||||||
of these commands are self-explanatory. So the message sending
|
tell it to <command>send</command>, <command>list</command>,
|
||||||
process involves copying a component file, editing your email,
|
<command>edit</command>, <command>push</command>, and
|
||||||
and then telling the <command>whatnow</command> program what to do with
|
<command>quit</command>. Most of these commands are
|
||||||
your email.</para>
|
self-explanatory. So the message sending process involves
|
||||||
|
copying a component file, editing your email, and then telling
|
||||||
|
the <command>whatnow</command> program what to do with your
|
||||||
|
email.</para>
|
||||||
|
|
||||||
<sect2>
|
<sect2>
|
||||||
<title><command>comp</command>, <command>forw</command>,
|
<title><command>comp</command>, <command>forw</command>,
|
||||||
|
|
@ -686,19 +722,22 @@ Subject:<userinput>And on the 8th day God created the FreeBSD core team</userinp
|
||||||
|
|
||||||
<para>The <command>repl</command> command will reply to the
|
<para>The <command>repl</command> command will reply to the
|
||||||
current message, unless you give it a different message to
|
current message, unless you give it a different message to
|
||||||
reply to. <command>repl</command> will do its best to go ahead and
|
reply to. <command>repl</command> will do its best to go ahead
|
||||||
fill in some of the email headers already. So you will notice
|
and fill in some of the email headers already. So you will
|
||||||
that the <literal>To:</literal> header already has the address of the
|
notice that the <literal>To:</literal> header already has the
|
||||||
recipient in there. Also the <literal>Subject:</literal> line will
|
address of the recipient in there. Also the
|
||||||
already be filled in. You then go about the normal message
|
<literal>Subject:</literal> line will already be filled in.
|
||||||
composition process and you are done. One useful command line
|
You then go about the normal message composition process and
|
||||||
option to know here is the <option>-cc</option> option. You
|
you are done. One useful command line option to know here is
|
||||||
can use <parameter>all</parameter>, <parameter>to</parameter>, <parameter>cc</parameter>,
|
the <option>-cc</option> option. You can use
|
||||||
<parameter>me</parameter> after the <option>-cc</option> option to have
|
<parameter>all</parameter>, <parameter>to</parameter>,
|
||||||
<command>repl</command> automatically add the various addresses to
|
<parameter>cc</parameter>, <parameter>me</parameter> after the
|
||||||
the <literal>Cc:</literal> list in the message. You have probably noticed that the
|
<option>-cc</option> option to have <command>repl</command>
|
||||||
original message is not included. This is because most <application>MH</application>
|
automatically add the various addresses to the
|
||||||
setups are configured to do this from the start.</para>
|
<literal>Cc:</literal> list in the message. You have probably
|
||||||
|
noticed that the original message is not included. This is
|
||||||
|
because most <application>MH</application> setups are
|
||||||
|
configured to do this from the start.</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
|
|
||||||
<sect2>
|
<sect2>
|
||||||
|
|
@ -708,14 +747,14 @@ Subject:<userinput>And on the 8th day God created the FreeBSD core team</userinp
|
||||||
|
|
||||||
<para>The <filename>components</filename> file is usually in
|
<para>The <filename>components</filename> file is usually in
|
||||||
<filename>/usr/local/lib/mh</filename>. You can copy that file
|
<filename>/usr/local/lib/mh</filename>. You can copy that file
|
||||||
into your <application>MH</application> Mail directory and edit to contain what you want
|
into your <application>MH</application> Mail directory and
|
||||||
it to contain. It is a fairly basic file. You have various
|
edit to contain what you want it to contain. It is a fairly
|
||||||
email headers at the top, a dashed line and then nothing. The
|
basic file. You have various email headers at the top, a
|
||||||
<command>comp</command> command just copies this
|
dashed line and then nothing. The <command>comp</command>
|
||||||
<filename>components</filename> file and then edits it. You can add
|
command just copies this <filename>components</filename> file
|
||||||
any kind of valid RFC822 header you want. For instance you
|
and then edits it. You can add any kind of valid RFC822 header
|
||||||
could have something like this in your <filename>components</filename>
|
you want. For instance you could have something like this in
|
||||||
file:</para>
|
your <filename>components</filename> file:</para>
|
||||||
|
|
||||||
<informalexample>
|
<informalexample>
|
||||||
<screen>To:
|
<screen>To:
|
||||||
|
|
@ -726,11 +765,12 @@ X-Home-Page: http://www.FreeBSD.org/
|
||||||
-------</screen>
|
-------</screen>
|
||||||
</informalexample>
|
</informalexample>
|
||||||
|
|
||||||
<para><application>MH</application> would then copy this components file and throw you into
|
<para><application>MH</application> would then copy this
|
||||||
your editor. The <filename>components</filename> file is fairly
|
components file and throw you into your editor. The
|
||||||
simple. If you wanted to have a signature on those messages
|
<filename>components</filename> file is fairly simple. If you
|
||||||
you would just put your signature in that
|
wanted to have a signature on those messages you would just
|
||||||
<filename>components</filename> file.</para>
|
put your signature in that <filename>components</filename>
|
||||||
|
file.</para>
|
||||||
|
|
||||||
<para>The <filename>replcomps</filename> file is a bit more complex. The
|
<para>The <filename>replcomps</filename> file is a bit more complex. The
|
||||||
default <filename>replcomps</filename> looks like this:</para>
|
default <filename>replcomps</filename> looks like this:</para>
|
||||||
|
|
@ -765,14 +805,15 @@ from address</emphasis>, %? <emphasis remap=bf>else</emphasis> {sender} <emphasi
|
||||||
message</emphasis>, %> <emphasis remap=bf>endif</emphasis>.</screen>
|
message</emphasis>, %> <emphasis remap=bf>endif</emphasis>.</screen>
|
||||||
</informalexample>
|
</informalexample>
|
||||||
|
|
||||||
<para>As you can tell <application>MH</application> formatting can get rather involved. You
|
<para>As you can tell <application>MH</application> formatting
|
||||||
can probably decipher what most of the other functions and
|
can get rather involved. You can probably decipher what most
|
||||||
variables mean. All of the information on writing these format
|
of the other functions and variables mean. All of the
|
||||||
strings is in the MH-Format manual page. The really nice thing is
|
information on writing these format strings is in the
|
||||||
that once you have built your customized
|
MH-Format manual page. The really nice thing is that once you
|
||||||
<filename>replcomps</filename> file you will not need to touch it again.
|
have built your customized <filename>replcomps</filename> file
|
||||||
No other email program really gives you the power and
|
you will not need to touch it again. No other email program
|
||||||
flexibility that <application>MH</application> gives you.</para>
|
really gives you the power and flexibility that
|
||||||
|
<application>MH</application> gives you.</para>
|
||||||
</sect2>
|
</sect2>
|
||||||
</sect1>
|
</sect1>
|
||||||
</article>
|
</article>
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue