[deployment-guide/comm-rel: 24/35] Fixed the .fetchmailrc formatting.

[dsilas]

commit e9383fef566b07654c5283c5b1cc44e248223ae6
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Fri Jun 4 16:00:30 2010 +0200

    Fixed the .fetchmailrc formatting.

 en-US/Email.xml |   12 +++++++++---
 1 files changed, 9 insertions(+), 3 deletions(-)
---
diff --git a/en-US/Email.xml b/en-US/Email.xml
index 993e03c..1a468ad 100644
--- a/en-US/Email.xml
+++ b/en-US/Email.xml
@@ -600,9 +600,15 @@ FEATURE('ldap_routing')dnl
         <para>Global options appear at the top of the <filename>.fetchmailrc</filename> file, followed by one or more server options, each of which designate a different email server that Fetchmail should check. User options follow server options for each user account checking that email server. Like server options, multiple user options may be specified for use with a particular server as well as to check multiple email accounts on the same server.</para>
         <para>Server options are called into service in the <filename>.fetchmailrc</filename> file by the use of a special option verb, <command>poll</command> or <command>skip</command>, that precedes any of the server information. The <command>poll</command> action tells Fetchmail to use this server option when it is run, which checks for email using the specified user options. Any server options after a <command>skip</command> action, however, are not checked unless this server's hostname is specified when Fetchmail is invoked. The <command>skip</command> option is useful when testing configurations in <filename>.fetchmailrc</filename> because it only checks skipped servers when specifically invoked, and does not affect any currently working configurations.</para>
         <para>A sample <filename>.fetchmailrc</filename> file looks similar to the following example:</para>
-        <screen>
-<command>set postmaster "user1" set bouncemail poll pop.domain.com proto pop3 user 'user1' there with password 'secret' is user1 here poll mail.domain2.com user 'user5' there with password 'secret2' is user1 here user 'user7' there with password 'secret3' is user1 here</command>
-        </screen>
+        <screen>set postmaster "user1"
+set bouncemail
+
+poll pop.domain.com proto pop3
+     user 'user1' there with password 'secret' is user1 here
+
+poll mail.domain2.com
+    user 'user5' there with password 'secret2' is user1 here
+    user 'user7' there with password 'secret3' is user1 here</screen>
         <para>In this example, the global options specify that the user is sent email as a last resort (<command>postmaster</command> option) and all email errors are sent to the postmaster instead of the sender (<command>bouncemail</command> option). The <command>set</command> action tells Fetchmail that this line contains a global option. Then, two email servers are specified, one set to check using POP3, the other for trying various protocols to find one that works. Two users are checked using the second server option, but all email found for any user is sent to <command>user1</command>'s mail spool. This allows multiple mailboxes to be checked on multiple servers, while appearing in a single MUA inbox. Each user's specific information begins with the <command>user</command> action.</para>
         <note>
           <title>Note</title>