Changeset e540c04


Ignore:
Timestamp:
07/22/2005 06:00:22 PM (19 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
ba0deaad
Parents:
9e4bed20
Message:

Fixed typos in Courier instructions

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4760 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • server/mail/courier.xml

    r9e4bed20 re540c04  
    8484
    8585    <note>
    86       <para><application>Courier</application>'s tarball must be extacted
    87       as an unprivileged user or the configure script will fail.</para>
     86      <para><application>Courier</application>'s tarball must be extracted
     87      as an unprivileged user or the <command>configure</command> script will
     88      fail.</para>
    8889    </note>
    8990
    9091    <para>Before you compile the program, you need to create the
    9192    <systemitem class="username">courier</systemitem> user and group
    92     that is expected to be in place when the install script executes.
     93    that is expected to be in place during installation.
    9394    As the <systemitem class="username">root</systemitem> user, add
    9495    the <systemitem class="username">courier</systemitem> user and
     
    102103    class="username">bin</systemitem> user. If you already have a
    103104    user named <systemitem class="username">bin</systemitem>, this
    104     step can be safely ignored.</para>
     105    step can be safely ignored. If necessary, create the user by
     106    issuing the following command as the
     107    <systemitem class="username">root</systemitem> user:</para>
    105108
    106109<screen role="root"><userinput>useradd -c 'bin' -d /dev/null -g bin -u 1 bin</userinput></screen>
     
    108111    <para><application>Courierfilter</application> requires the directory
    109112    <filename class="directory">/var/run/courier</filename> to store
    110     all the <application>Courier</application> pid and lockfiles.
     113    all the <application>Courier</application> PID and lock files.
    111114    <filename class="directory">/var/lock/subsys</filename> also must exist
    112115    for the master lock file for <application>Courier</application>. Issue
    113     the following commands to create these directories:</para>
     116    the following commands as the
     117    <systemitem class="username">root</systemitem> user to create these
     118    directories:</para>
    114119
    115120<screen role="root"><userinput>install -v -d /var/run/courier -o courier -g courier -m755 &amp;&amp;
     
    139144
    140145    <para><parameter>--libexecdir=/usr/lib/courier</parameter>: Specifies
    141     the directory which contains programs and libraries that cannot be
     146    the directory which contains programs and libraries that should not be
    142147    directly executed from the command-line.</para>
    143148
     
    153158    <para><parameter>--with-piddir=/var/run/courier</parameter>: Specifies
    154159    the directory where <application>Courier</application>'s
    155     <filename>PID</filename> files are stored when
     160    PID files are stored when
    156161    <application>Courier</application> is active.</para>
    157162
     
    162167    result in the event that someone else uses the same name to implement
    163168    some other extension. If this option is specified,
    164     <application>Courier's</application> ESMTP server will also advertise a
     169    <application>Courier</application>'s ESMTP server will also advertise a
    165170    dummy ESMTP capability called XCOURIEREXTENSIONS, and will not recognize
    166171    any Courier-specific extensions unless the remote mail server also
     
    176181    those buggy IMAP clients. NOTE: <command>make check</command> will fail if
    177182    this option is used. You should first configure without this option, and
    178     if all post-configuration tests succeed, rerun configure with this option
    179     and recompile.</para>
     183    if all post-configuration tests succeed, rerun <command>configure</command>
     184    with this option and recompile.</para>
    180185
    181186    <para><parameter>--with-db=gdbm</parameter>:
     
    194199    checking, if <command>configure</command> finds
    195200    <application>ispell</application> or if you explicitly set the location
    196     of <application>aspell</application>.</para>
     201    of <application>Aspell</application>.</para>
    197202
    198203    <para><option>--enable-mimetypes=<replaceable>[location of mime.types
     
    260265      <filename>/etc/courier/smtpaccess/default</filename> file.</para>
    261266
    262       <para>If you wish to host mail for non local domains including virtual
     267      <para>If you wish to host mail for non-local domains including virtual
    263268      domains, you must add them to
    264269      <filename>/etc/courier/hosteddomains</filename>. This file should exist
     
    283288      <para>If you wish to use SSL with <application>Courier</application>,
    284289      you should obtain certificates and store them in
    285       <filename>/usr/share/courier</filename>.  You can optionally create
    286       self-signed, test certificates with the following commands:</para>
     290      <filename class='directory'>/usr/share/courier</filename>.  You can
     291      optionally create self-signed, test certificates with the following
     292      commands:</para>
    287293
    288294<screen role="root"><userinput>mkesmtpdcert &amp;&amp;
     
    450456);</userinput></screen>
    451457
    452       <para>Grant all priveledges to the <systemitem
     458      <para>Grant all privileges to the <systemitem
    453459      class="username">courier</systemitem> user created earlier:</para>
    454460
     
    465471
    466472<screen role="root"><userinput>cd /home/vmailman &amp;&amp;
    467 mkdir <replaceable>[virtual_user]</replaceable> &amp;&amp;
     473mkdir -v <replaceable>[virtual_user]</replaceable> &amp;&amp;
    468474cd <replaceable>[virtual_user]</replaceable> &amp;&amp;
    469475maildirmake Maildir &amp;&amp;
    470 chown vmailman.vmailman Maildir -R</userinput></screen>
    471 
    472       <para>Now, connect the the <application>MySQL</application> database as
     476chown -v vmailman.vmailman Maildir -R</userinput></screen>
     477
     478      <para>Now, connect to the <application>MySQL</application> database as
    473479      the <systemitem class="username">courier</systemitem> user:</para>
    474480
     
    476482
    477483      <para>To add the virtual user you need to enter at least one version of the
    478       password either clear text or encrypted.</para>
     484      password; either clear text or encrypted.</para>
    479485
    480486      <para>Add the first virtual user with the following commands:</para>
Note: See TracChangeset for help on using the changeset viewer.