1.1 --- a/discussion.roff	Sun Jul 15 18:42:08 2012 +0200
     1.2 +++ b/discussion.roff	Sun Jul 15 19:16:35 2012 +0200
     1.3 @@ -75,19 +75,8 @@
     1.4  Instead, the aspects of email should be covered by multiple projects,
     1.5  which then can be combined to form a complete system.
     1.6  Excellent implementations for the various aspects of email already exist.
     1.7 -Just to name three examples: Postfix
     1.8 -.[
     1.9 -postfix website
    1.10 -.]
    1.11 -is a specialized MTA, Procmail
    1.12 -.[
    1.13 -procmail website
    1.14 -.]
    1.15 -is a specialized MDA, and Fetchmail
    1.16 -.[
    1.17 -fetchmail website
    1.18 -.]
    1.19 -is a specialized MRA.
    1.20 +Just to name three examples: Postfix is a specialized MTA, Procmail
    1.21 +is a specialized MDA, and Fetchmail is a specialized MRA.
    1.22  I believe that it is best to use such specialized tools instead of
    1.23  providing the same function once more as a side component.
    1.24  .P
    1.25 @@ -126,9 +115,6 @@
    1.26  Focusing on one mail agent role only, is motivated by Eric Allman's
    1.27  experience with Sendmail.
    1.28  He identified the limitation of Sendmail
    1.29 -.[
    1.30 -sendmail website
    1.31 -.]
    1.32  to the MTA task as one reason for its success:
    1.33  .[ [
    1.34  costales sendmail
    1.35 @@ -164,11 +150,7 @@
    1.36  It must read the message from the standard input, extract the
    1.37  recipient addresses from the message header, and hand the message
    1.38  over to the MSA.
    1.39 -For example, a wrapper script for qmail
    1.40 -.[
    1.41 -qmail website
    1.42 -.]
    1.43 -would be:
    1.44 +For example, a wrapper script for qmail would be:
    1.45  .VS
    1.46  #!/bin/sh
    1.47  exec qmail-inject  # ignore command line arguments
    1.48 @@ -312,39 +294,11 @@
    1.49  Also, the popular MSAs and MRAs have large communities and a lot
    1.50  of available documentation.
    1.51  
    1.52 -Choices for MSAs range from small forwarders such as
    1.53 -.[
    1.54 -ssmtp website
    1.55 -.]
    1.56 -and,
    1.57 -.[
    1.58 -nullmailer website
    1.59 -.]
    1.60 -over mid-size MTAs including
    1.61 -.[
    1.62 -masqmail website
    1.63 -.]
    1.64 -and,
    1.65 -.[
    1.66 -dma dragonfly mail agent website
    1.67 -.]
    1.68 -up to full-featured MTAs as for instance.
    1.69 -.[
    1.70 -postfix website
    1.71 -.]
    1.72 -MRAs are provided for example by
    1.73 -.[ [
    1.74 -fetchmail website
    1.75 -.]
    1.76 -.[
    1.77 -getmail website
    1.78 -.]
    1.79 -.[
    1.80 -mpop website
    1.81 -.]
    1.82 -.[
    1.83 -fdm website
    1.84 -.]].
    1.85 +Choices for MSAs range from small forwarders such as \fIssmtp\fP and
    1.86 +\fInullmailer\fP, over mid-size MTAs including \fImasqmail\fP and
    1.87 +\fIdma\fP, up to full-featured MTAs as for instance \fIPostfix\fP.
    1.88 +MRAs are provided for example by \fIfetchmail\fP, \fIgetmail\fP,
    1.89 +\fImpop\fP, and \fIfdm\fP.
    1.90  
    1.91  
    1.92  .H2 "Non-MUA Tools
    1.93 @@ -904,9 +858,6 @@
    1.94  .Sw --disable-mhe
    1.95  was removed when the MH-E support was reworked. 
    1.96  MH-E is the Emacs front-end to MH.
    1.97 -.[
    1.98 -mh-e emacs website
    1.99 -.]
   1.100  It requires MH to provide minor additional functions.
   1.101  The
   1.102  .Sw --disable-mhe
   1.103 @@ -2414,10 +2365,7 @@
   1.104  .Pn mhsign
   1.105  handles the signing and encrypting part.
   1.106  It comprises about 250 lines of shell code and interfaces between
   1.107 -.Pn gnupg "
   1.108 -.[
   1.109 -gnupg website
   1.110 -.]
   1.111 +.Pn gnupg
   1.112  and the MH system.
   1.113  It was meant to be invoked manually at the WhatNow prompt, but in mmh,
   1.114  .Pn send