[deployment-guide/comm-rel: 531/727] added section "using LDAP with Postfix"

Tue Oct 19 13:09:35 UTC 2010

commit ea0630a82150f155503f57557cc50054955a75b0
Author: Martin Prpic <mprpic at redhat.com>
Date:   Tue Aug 31 16:57:10 2010 +0200

    added section "using LDAP with Postfix"

 en-US/Email.xml |   38 +++++++++++++++++++++++++++++++++-----
 1 files changed, 33 insertions(+), 5 deletions(-)
---

diff --git a/en-US/Email.xml b/en-US/Email.xml
index eb8b881..a6f4823 100644
--- a/en-US/Email.xml
+++ b/en-US/Email.xml
@@ -356,8 +356,36 @@
           </listitem>
         </itemizedlist>
         <para>Once these steps are complete, the host accepts outside emails for delivery.</para>
-        <para>Postfix has a large assortment of configuration options. One of the best ways to learn how to configure Postfix is to read the comments within the <filename>/etc/postfix/main.cf</filename> configuration file. Additional resources including information about <systemitem class="protocol">LDAP</systemitem> and SpamAssassin integration are available online at <ulink
-            url="http://www.postfix.org/">http://www.postfix.org/</ulink>.</para>
+        <para>Postfix has a large assortment of configuration options. One of the best ways to learn how to configure Postfix is to read the comments within the <filename>/etc/postfix/main.cf</filename> configuration file. Additional resources including information about Postfix configuration, SpamAssassin integration, or detailed descriptions of the <filename>/etc/postfix/main.cf</filename> parameters are available online at <ulink url="http://www.postfix.org/">http://www.postfix.org/</ulink>.</para>
+      </section>
+      <section id="using-postfix-with-ldap">
+        <title>Using Postfix with LDAP</title>
+        <para>
+          Postfix can use an <systemitem class="protocol">LDAP</systemitem> directory as a source for various lookup files (e.g.: <filename>/etc/aliases</filename> <filename>/etc/postfix/virtual</filename>, <filename>/etc/postfix/canonical</filename>, etc.). This allows <systemitem class="protocol">LDAP</systemitem> to store hierarchical user information and Postfix to only be given the result of <systemitem class="protocol">LDAP</systemitem> queries when needed. By not storing this information locally, administrators can easily maintain it.
+        </para>
+        <section id="aliases-example">
+          <title><filename>/etc/aliases</filename> lookup example</title>
+          <para>The following is a basic example for using <systemitem class="protocol">LDAP</systemitem> to look up the <filename>/etc/aliases</filename> file. Make sure your <filename>/etc/postfix/main.cf</filename> contains the following: 
+          </para>
+          <screen>
+alias_maps = hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases.cf
+          </screen>
+          <para>
+            Create a <filename>/etc/postfix/ldap-aliases.cf</filename> file if you do not have one created already and make sure it contains the following:
+          </para>
+          <screen>
+server_host = ldap.example.com
+search_base = dc=example, dc=com
+          </screen>
+          <note>
+            <title>Note</title>
+              <para>
+                The /<filename>etc/postfix/ldap-aliases.cf</filename> file can specify various parameters, including parameters that enable <systemitem class="protocol">LDAP</systemitem> <systemitem class="protocol">SSL</systemitem> and <systemitem class="protocol">STARTTLS</systemitem>. For more information, refer to the <command>ldap_table(5)</command> man page.
+              </para>
+          </note>
+          <para>For more information on <systemitem class="protocol">LDAP</systemitem>, refer to <xref linkend="ch-Lightweight_Directory_Access_Protocol_LDAP"/>.
+          </para>
+        </section>
       </section>
     </section>
     <section
@@ -575,7 +603,7 @@ FEATURE('ldap_routing')dnl
           <para>This is only for a very basic configuration of Sendmail with <systemitem class="protocol">LDAP</systemitem>. The configuration can differ greatly from this depending on the implementation of <systemitem class="protocol">LDAP</systemitem>, especially when configuring several Sendmail machines to use a common <systemitem class="protocol">LDAP</systemitem> server.</para>
           <para>Consult <filename>/usr/share/sendmail-cf/README</filename> for detailed <systemitem class="protocol">LDAP</systemitem> routing configuration instructions and examples.</para>
         </note>
-        <para>Next, recreate the <filename>/etc/mail/sendmail.cf</filename> file by running <command>m4</command> and again restarting Sendmail. Refer to <xref
+        <para>Next, recreate the <filename>/etc/mail/sendmail.cf</filename> file by running the <command>m4</command> macro processor and again restarting Sendmail. Refer to <xref
             linkend="s3-email-mta-sendmail-changes"/> for instructions.</para>
         <para>For more information on <systemitem class="protocol">LDAP</systemitem>, refer to <xref
             linkend="ch-Lightweight_Directory_Access_Protocol_LDAP"/>.</para>
@@ -1333,7 +1361,7 @@ poll mail.domain2.com
           <tertiary>clients</tertiary>
         </indexterm>
         <para>Most Linux MUAs designed to check email on remote servers support SSL encryption. To use SSL when retrieving email, it must be enabled on both the email client and the server.</para>
-        <para>SSL is easy to enable on the client-side, often done with the click of a button in the MUA's configuration window or via an option in the MUA's configuration file. Secure <systemitem class="protocol">IMAP</systemitem> and <systemitem class="protocol">POP</systemitem> have known port numbers (993 and 995, respectively) that the MUA uses to authenticate and download messages.</para>
+        <para>SSL is easy to enable on the client-side, often done with the click of a button in the MUA's configuration window or via an option in the MUA's configuration file. Secure <systemitem class="protocol">IMAP</systemitem> and <systemitem class="protocol">POP</systemitem> have known port numbers (<constant>993</constant> and <constant>995</constant>, respectively) that the MUA uses to authenticate and download messages.</para>
       </section>
       <section
         id="s3-email-security-servers">
@@ -1435,7 +1463,7 @@ connect = 143
           <itemizedlist>
             <listitem>
               <para>
-                <filename>/usr/share/sendmail-cf/README</filename> — Contains information on <command>m4</command>, file locations for Sendmail, supported mailers, how to access enhanced features, and more.</para>
+                <filename>/usr/share/sendmail-cf/README</filename> — Contains information on the <command>m4</command> macro processor, file locations for Sendmail, supported mailers, how to access enhanced features, and more.</para>
             </listitem>
           </itemizedlist>
           <para>In addition, the <filename>sendmail</filename> and <filename>aliases</filename> man pages contain helpful information covering various Sendmail options and the proper configuration of the Sendmail <filename>/etc/mail/aliases</filename> file.</para>
