[deployment-guide/comm-rel: 413/727] fixed minor issues in the Email chapter
Jaromir Hradilek
jhradile at fedoraproject.org
Tue Oct 19 12:59:29 UTC 2010
commit 494bc53214077bbc2249f08e9251f0d623274041
Author: Martin Prpic <mprpic at redhat.com>
Date: Wed Aug 18 14:57:46 2010 +0200
fixed minor issues in the Email chapter
en-US/Email.xml | 36 ++++++++++++++++++++----------------
1 files changed, 20 insertions(+), 16 deletions(-)
---
diff --git a/en-US/Email.xml b/en-US/Email.xml
index 66623b9..ac5f38d 100644
--- a/en-US/Email.xml
+++ b/en-US/Email.xml
@@ -58,7 +58,7 @@
<tertiary>POP</tertiary>
</indexterm>
<!-- mhlavink: do we realy need paths to executables? -->
- <para>The default POP server under &MAJOROS; is <command>/usr/bin/dovecot</command> and is provided by the <package>dovecot</package> package. When using a POP server, email messages are downloaded by email client applications. By default, most POP email clients are automatically configured to delete the message on the email server after it has been successfully transferred, however this setting usually can be changed.</para>
+ <para>The default POP server under &MAJOROS; is <filename>/usr/bin/dovecot</filename> and is provided by the <package>dovecot</package> package. When using a POP server, email messages are downloaded by email client applications. By default, most POP email clients are automatically configured to delete the message on the email server after it has been successfully transferred, however this setting usually can be changed.</para>
<para>POP is fully compatible with important Internet messaging standards, such as <firstterm>Multipurpose Internet Mail Extensions</firstterm> (<firstterm>MIME</firstterm>), which allow for email attachments.</para>
<para>POP works best for users who have one system on which to read email. It also works well for users who do not have a persistent connection to the Internet or the network containing the mail server. Unfortunately for those with slow network connections, POP requires client programs upon authentication to download the entire content of each message. This can take a long time if any messages have large attachments.</para>
<para>The most current version of the standard POP protocol is POP3.</para>
@@ -89,13 +89,12 @@
<secondary>protocols</secondary>
<tertiary>IMAP</tertiary>
</indexterm>
- <para>The default IMAP server under &MAJOROS; is <command>/usr/bin/dovecot</command> and is provided by the <filename>dovecot</filename> package. When using an IMAP mail server, email messages remain on the server where users can read or delete them. IMAP also allows client applications to create, rename, or delete mail directories on the server to organize and store email.</para>
+ <para>The default IMAP server under &MAJOROS; is <filename>/usr/bin/dovecot</filename> and is provided by the <package>dovecot</package> package. When using an IMAP mail server, email messages remain on the server where users can read or delete them. IMAP also allows client applications to create, rename, or delete mail directories on the server to organize and store email.</para>
<para>IMAP is particularly useful for those who access their email using multiple machines. The protocol is also convenient for users connecting to the mail server via a slow connection, because only the email header information is downloaded for messages until opened, saving bandwidth. The user also has the ability to delete messages without viewing or downloading them.</para>
<para>For convenience, IMAP client applications are capable of caching copies of messages locally, so the user can browse previously read messages when not directly connected to the IMAP server.</para>
<para>IMAP, like POP, is fully compatible with important Internet messaging standards, such as MIME, which allow for email attachments.</para>
- <para>For added security, it is possible to use <firstterm>SSL</firstterm> encryption for client authentication and data transfer sessions. This can be enabled by using the <command>imaps</command> service, or by using the <command>/usr/sbin/stunnel</command> program. Refer to <xref
- linkend="s2-email-security"/> for more information.</para>
- <para>Other free, as well as commercial, IMAP clients and servers are available, many of which extend the IMAP protocol and provide additional functionality. A comprehensive list can be found online at <ulink url="http://en.wikipedia.org/wiki/List_of_mail_servers"/>.</para>
+ <para>For added security, it is possible to use <firstterm>SSL</firstterm> encryption for client authentication and data transfer sessions. This can be enabled by using the <command>imaps</command> service, or by using the <command>/usr/sbin/stunnel</command> program. For more information, refer to <xref linkend="s2-email-security"/>.</para>
+ <para>Other free, as well as commercial, IMAP clients and servers are available, many of which extend the IMAP protocol and provide additional functionality.</para>
</section>
<section
id="s3-email-protocols-dovecot">
@@ -124,23 +123,28 @@
<para>Make that change operational after the next reboot by running the command:</para>
<screen>chkconfig dovecot on
</screen>
- <para>Please note that <filename>dovecot</filename> only reports that it started the IMAP server, but also starts the POP3 server.</para>
+ <note>
+ <title>Note</title>
+ <para>
+ Please note that <command>dovecot</command> only reports that it started the IMAP server, but also starts the POP3 server.
+ </para>
+ </note>
</listitem>
</orderedlist>
<para>Unlike SMTP, both of these protocols require connecting clients to authenticate using a username and password. By default, passwords for both protocols are passed over the network unencrypted.</para>
<para>To configure SSL on dovecot:
<itemizedlist>
<listitem>
- <para>Edit the <filename>dovecot</filename> configuration file <filename>/etc/pki/dovecot/dovecot-openssl.conf</filename> as you prefer. However in a typical installation, this file does not require modification.</para>
+ <para>Edit the <command>dovecot</command> configuration file <filename>/etc/pki/dovecot/dovecot-openssl.conf</filename> as you prefer. However in a typical installation, this file does not require modification.</para>
</listitem>
<listitem>
<para>Rename, move or delete the files <filename>/etc/pki/dovecot/certs/dovecot.pem</filename> and <filename>/etc/pki/dovecot/private/dovecot.pem</filename>.</para>
</listitem>
<listitem>
- <para>Execute the <filename>/usr/libexec/dovecot/mkcert.sh</filename> script which creates the dovecot self signed certificates. The certificates are copied in the <filename>/etc/pki/dovecot/certs</filename> and <filename>/etc/pki/dovecot/private</filename> directories. To implement the changes, restart <filename>dovecot</filename> (<command>/sbin/service dovecot restart</command>).</para>
+ <para>Execute the <filename>/usr/libexec/dovecot/mkcert.sh</filename> script which creates the dovecot self signed certificates. The certificates are copied in the <filename>/etc/pki/dovecot/certs</filename> and <filename>/etc/pki/dovecot/private</filename> directories. To implement the changes, restart <command>dovecot</command> (<command>/sbin/service dovecot restart</command>).</para>
</listitem>
</itemizedlist>
- More details on <filename>dovecot</filename> can be found online at <ulink
+ More details on <command>dovecot</command> can be found online at <ulink
url="http://www.dovecot.org">http://www.dovecot.org</ulink>.</para>
</section>
</section>
@@ -176,7 +180,7 @@
<para>A <firstterm>Mail Transport Agent</firstterm> (<firstterm>MTA</firstterm>) transports email messages between hosts using SMTP. A message may involve several MTAs as it moves to its intended destination.</para>
<para>While the delivery of messages between machines may seem rather straightforward, the entire process of deciding if a particular MTA can or should accept a message for delivery is quite complicated. In addition, due to problems from spam, use of a particular MTA is usually restricted by the MTA's configuration or the access configuration for the network on which the MTA resides.</para>
<para>Many modern email client programs can act as an MTA when sending email. However, this action should not be confused with the role of a true MTA. The sole reason email client programs are capable of sending email like an MTA is because the host running the application does not have its own MTA. This is particularly true for email client programs on non-UNIX-based operating systems. However, these client programs only send outbound messages to an MTA they are authorized to use and do not directly deliver the message to the intended recipient's email server.</para>
- <para>Since &MAJOROS; installs two MTAs—Sendmail and Postfix—email client programs are often not required to act as an MTA. &MAJOROS; also includes a special purpose MTA called Fetchmail.</para>
+ <para>Since &MAJOROS; installs two MTAs—Postfix and Sendmail—email client programs are often not required to act as an MTA. &MAJOROS; also includes a special purpose MTA called Fetchmail.</para>
<para>For more information on Postfix, Sendmail, and Fetchmail, refer to <xref
linkend="s1-email-mta"/>.</para>
</section>
@@ -222,7 +226,7 @@
<see>Mail User Agent</see>
</indexterm>
<para>A <firstterm>Mail User Agent</firstterm> (<firstterm>MUA</firstterm>) is synonymous with an email client application. An MUA is a program that, at the very least, allows a user to read and compose email messages. Many MUAs are capable of retrieving messages via the POP or IMAP protocols, setting up mailboxes to store messages, and sending outbound messages to an MTA.</para>
- <para>MUAs may be graphical, such as Evolution, or have simple text-based interfaces, such as <command>pine</command>.</para>
+ <para>MUAs may be graphical, such as <application>Evolution</application>, or have simple text-based interfaces, such as <application>pine</application>.</para>
</section>
</section>
<section
@@ -596,8 +600,8 @@ FEATURE('ldap_routing')dnl
</listitem>
</itemizedlist>
<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>
+ <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 the <filename>.fetchmailrc</filename> file because it only checks skipped servers when specifically invoked, and does not affect any currently working configurations.</para>
+ <para>The following is a sample example of a <filename>.fetchmailrc</filename> file:</para>
<screen>set postmaster "user1"
set bouncemail
@@ -824,9 +828,8 @@ poll mail.domain2.com
<para>More commands and <filename>.fetchmailrc</filename> options can be found in the <command>fetchmail</command> man page.</para>
</section>
</section>
- </section>
- <section
- id="s1-email-switchmail">
+ <section
+ id="s2-email-switchmail">
<title>Mail Transport Agent (MTA) Configuration</title>
<indexterm
significance="normal">
@@ -922,6 +925,7 @@ poll mail.domain2.com
<para>If you select <guibutton>OK</guibutton> to change the MTA, the selected mail daemon is enabled to start at boot time, and the unselected mail daemons are disabled so that they do not start at boot time. The selected mail daemon is started, and any other mail daemon is stopped; thus making the changes take place immediately.</para>
</section>-->
</section>
+ </section>
<section
id="s1-email-mda">
<title>Mail Delivery Agents</title>
More information about the docs-commits
mailing list