[deployment-guide/comm-rel: 585/727] modified Using Postfix with LDAP section

[Jaromir Hradilek]

commit 0af16f96e0ecd0c6ffb8d5d643748fd596457c48
Author: Martin Prpic <mprpic at redhat.com>
Date:   Mon Sep 6 13:34:30 2010 +0200

    modified Using Postfix with LDAP section

 en-US/Email.xml |    9 ++++++---
 1 files changed, 6 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Email.xml b/en-US/Email.xml
index bc92ca8..0c4a57c 100644
--- a/en-US/Email.xml
+++ b/en-US/Email.xml
@@ -361,7 +361,7 @@
       <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.
+          Postfix can use an <systemitem class="protocol">LDAP</systemitem> directory as a source for various lookup tables (e.g.: <filename>aliases</filename>, <filename>virtual</filename>, <filename>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>The /etc/aliases</filename> lookup example</title>
@@ -374,9 +374,12 @@ alias_maps = hash:/etc/aliases, ldap:/etc/postfix/ldap-aliases.cf
             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
+server_host = <replaceable>ldap.example.com</replaceable>
+search_base = dc=<replaceable>example</replaceable>, dc=<replaceable>com</replaceable>
           </screen>
+          <para>
+            where <parameter>ldap.example.com</parameter>, <parameter>example</parameter>, and <parameter>com</parameter> are parameters that need to be replaced with specification of an existing available <systemitem class="protocol">LDAP</systemitem> server.
+          </para>
           <note>
             <title>Note</title>
               <para>