Fixed number of bytes to fread() in strip_crs() in mhfixmsg.

[nmh] / man / mh-alias.man

diff --git a/man/mh-alias.man b/man/mh-alias.man
index 926fb89e856cdf7c0d3996891c1eb66ecced993f..ca9e0a2c203531f090ad64640f9c0989de575430 100644 (file)
--- a/man/mh-alias.man
+++ b/man/mh-alias.man
@@ -1,7 +1,7 @@
+.TH MH-ALIAS %manext5% "Oct 14, 2012" "%nmhversion%"
 .\"
 .\" %nmhwarning%
 .\"
-.TH MH-ALIAS %manext5% "%nmhdate%" MH.6.8 [%nmhversion%]
 .SH NAME
 mh-alias \- alias file for nmh message system
 .SH SYNOPSIS
@@ -128,17 +128,13 @@ appropriate.  (See example below.)
 .PP
 An approximation of the way aliases are resolved at posting time is
 (it's not really done this way):
-.PP
-.RS 2
-.IP 1) 3
+.IP 1)
 Build a list of all addresses from the message to be delivered,
 eliminating duplicate addresses.
-.PP
-.IP 2) 3
+.IP 2)
 If this draft originated on the local host, then for those addresses in
 the message that have no host specified, perform alias resolution.
-.PP
-.IP 3) 3
+.IP 3)
 For each line in the alias file, compare \*(lqalias\*(rq against all of
 the existing addresses.  If a match, remove the matched \*(lqalias\*(rq
 from the address list, and add each new address in the address\-group to
@@ -148,12 +144,11 @@ output instead.  If \*(lqalias\*(rq is terminated with a `;' instead of
 a `:', then both the \*(lqalias\*(rq and the address are output in the
 correct format (with the alias quoted if necessary and the address
 wrapped in <>).
-
+.PP
 This makes replies possible since
 .B nmh
 aliases
 and personal aliases are unknown to the mail transport system.
-.RE
 .PP
 Since the alias file is read line by line, forward references work, but
 backward references are not recognized, thus, there is no recursion.
@@ -182,7 +177,6 @@ is defined as an alias for \*(lqfrated@UCI\*(rq, and \*(lqsgroup\*(rq
 is defined as an alias for the three names \*(lqfrated@UCI\*(rq,
 \*(rqfear\*(rq, and \*(rqfreida\*(rq.
 .PP
-
 The alias \*(lqb-people\*(rq is a blind list which includes the addresses
 \*(lqbill\*(rq and \*(lqbetty\*(rq; the message will be delivered to those
 addresses, but the message header will show only \*(lqBlind List: ;\*(rq
@@ -223,39 +217,31 @@ message transport system.  In contrast, once the message transport system
 is given a message to deliver to a list of addresses, for each address
 that appears to be local, a system\-wide alias file is consulted.  These
 aliases are
-.B NOT
+.B not
 expanded into the headers of messages delivered.
-
 .SH "HELPFUL HINTS"
 To use aliasing in
 .B nmh
 quickly, do the following:
-.PP
-.RS 2
-.IP 1) 3
+.IP 1)
 In your
 .IR \&.mh\(ruprofile ,
 choose a name for your alias file, say
 .RI \*(lq aliases \*(rq,
 and add the line:
-.PP
-.RS 5
-.nf
+.sp
 Aliasfile: aliases
 .\" ali: \-alias aliases
 .\" send: \-alias aliases
 .\" whom: \-alias aliases
-.fi
 .RE
-.PP
-.IP 2) 3
+.IP 2)
 Create the file
 .RI \*(lq aliases \*(rq
 in your
 .B nmh
 directory.
-.PP
-.IP 3) 3
+.IP 3)
 Start adding aliases to your
 .RI \*(lq aliases \*(rq
 file as appropriate.
@@ -267,28 +253,24 @@ expanded.  There must not be a semicolon at the end of, or within, the
 address group of a blind list.
 .B post
 will append the semicolon to the blind list name.
-
 .SH FILES
-.fc ^ ~
-.nf
-.ta \w'%etcdir%/ExtraBigFileName  'u
-^%etcdir%/MailAliases~^global nmh alias file
-.fi
-
+.TP 20
+%etcdir%/MailAliases
+global nmh alias file
 .SH "PROFILE COMPONENTS"
-.fc ^ ~
-.nf
-.ta 2.4i
-.ta \w'ExtraBigProfileName  'u
-^Aliasfile:~^For a default alias file
-.fi
-
+.TP 20
+Aliasfile:
+Default alias file
 .SH "SEE ALSO"
-ali(1), send(1), whom(1), group(5), passwd(5), conflict(8), post(8)
-
+.IR ali (1),
+.IR send (1),
+.IR whom (1),
+.IR group (5),
+.IR passwd (5),
+.IR conflict (8),
+.IR post (8)
 .SH CONTEXT
 None
-
 .SH BUGS
 Although the forward-referencing semantics of
 .B mh\-alias