Date: Fri, 9 May 2014 17:02:55 +0000 (UTC) From: Dru Lavigne <dru@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44799 - head/en_US.ISO8859-1/books/handbook/mail Message-ID: <201405091702.s49H2tjM066279@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: dru Date: Fri May 9 17:02:54 2014 New Revision: 44799 URL: http://svnweb.freebsd.org/changeset/doc/44799 Log: White space fix only. Translators can ignore. Sponsored by: iXsystems Modified: head/en_US.ISO8859-1/books/handbook/mail/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/mail/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/mail/chapter.xml Fri May 9 16:17:58 2014 (r44798) +++ head/en_US.ISO8859-1/books/handbook/mail/chapter.xml Fri May 9 17:02:54 2014 (r44799) @@ -5,30 +5,31 @@ $FreeBSD$ --> <chapter xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:id="mail"> - <info><title>Electronic Mail</title> + <info> + <title>Electronic Mail</title> + <authorgroup> - <author><personname><firstname>Bill</firstname><surname>Lloyd</surname></personname><contrib>Original work by </contrib></author> + <author><personname><firstname>Bill</firstname><surname>Lloyd</surname></personname><contrib>Original + work by </contrib></author> </authorgroup> <authorgroup> - <author><personname><firstname>Jim</firstname><surname>Mock</surname></personname><contrib>Rewritten by </contrib></author> + <author><personname><firstname>Jim</firstname><surname>Mock</surname></personname><contrib>Rewritten + by </contrib></author> </authorgroup> </info> - - <sect1 xml:id="mail-synopsis"> <title>Synopsis</title> <indexterm><primary>email</primary></indexterm> <para><quote>Electronic Mail</quote>, better known as email, is - one of the most widely used forms of communication today. - This chapter provides a basic introduction to running a mail - server on &os;, as well as an introduction to sending and - receiving email using &os;. - For more complete coverage of this subject, - refer to the books listed in - <xref linkend="bibliography"/>.</para> + one of the most widely used forms of communication today. This + chapter provides a basic introduction to running a mail server + on &os;, as well as an introduction to sending and receiving + email using &os;. For more complete coverage of this subject, + refer to the books listed in <xref + linkend="bibliography"/>.</para> <para>After reading this chapter, you will know:</para> @@ -49,8 +50,8 @@ </listitem> <listitem> - <para>How to block spammers from illegally using a mail - server as a relay.</para> + <para>How to block spammers from illegally using a mail server + as a relay.</para> </listitem> <listitem> @@ -98,7 +99,8 @@ <itemizedlist> <listitem> - <para>Properly set up a network connection (<xref linkend="advanced-networking"/>).</para> + <para>Properly set up a network connection (<xref + linkend="advanced-networking"/>).</para> </listitem> <listitem> @@ -135,7 +137,7 @@ <primary>mail server daemons</primary> <secondary><application>Exim</application></secondary> </indexterm> - <indexterm> + <indexterm> <primary>email</primary> <secondary>receiving</secondary> </indexterm> @@ -144,139 +146,149 @@ <para>There are five major parts involved in an email exchange: the Mail User Agent (<acronym>MUA</acronym>), the Mail Transfer - Agent (<acronym>MTA</acronym>), a mail host, a remote - or local mailbox, and <acronym>DNS</acronym>. This section provides an + Agent (<acronym>MTA</acronym>), a mail host, a remote or local + mailbox, and <acronym>DNS</acronym>. This section provides an overview of these components.</para> - + <variablelist> <varlistentry> <term>Mail User Agent (<acronym>MUA</acronym>)</term> <listitem> <para>The Mail User Agent (<acronym>MUA</acronym>) is an - application which is used to compose, send, and receive - emails. This application can be a command line program, such as - the built-in <command>mail</command> utility or a third-party - application from the Ports Collection, such as - <application>mutt</application>, - <application>alpine</application>, or - <application>elm</application>. - Dozens of graphical programs are also available in the Ports Collection, including - <application>Claws Mail</application>, <application>Evolution</application>, and - <application>Thunderbird</application>. Some organizations provide a web mail program - which can be accessed through a web browser. More information - about installing and using a <acronym>MUA</acronym> on &os; can be - found in <xref linkend="mail-agents"/>.</para> -</listitem> -</varlistentry> + application which is used to compose, send, and receive + emails. This application can be a command line program, + such as the built-in <command>mail</command> utility or a + third-party application from the Ports Collection, such as + <application>mutt</application>, + <application>alpine</application>, or + <application>elm</application>. Dozens of graphical + programs are also available in the Ports Collection, + including <application>Claws Mail</application>, + <application>Evolution</application>, and + <application>Thunderbird</application>. Some + organizations provide a web mail program which can be + accessed through a web browser. More information about + installing and using a <acronym>MUA</acronym> on &os; can + be found in <xref linkend="mail-agents"/>.</para> + </listitem> + </varlistentry> -<varlistentry> + <varlistentry> <term>Mail Transfer Agent (<acronym>MTA</acronym>)</term> <listitem> - <para>The Mail Transfer Agent (<acronym>MTA</acronym>) is - responsible for receiving incoming mail and delivering - outgoing mail. &os; ships with <application>Sendmail</application> as the - default <acronym>MTA</acronym>, but it also supports numerous - other mail server daemons, including <application>Exim</application>, - <application>Postfix</application>, and - <application>qmail</application>. - <application>Sendmail</application> configuration is described - in <xref linkend="sendmail"/>. If another - <acronym>MTA</acronym> is installed using the Ports - Collection, refer to its post-installation message for - &os;-specific configuration details and the application's - website for more general configuration instructions.</para> -</listitem> -</varlistentry> + <para>The Mail Transfer Agent (<acronym>MTA</acronym>) is + responsible for receiving incoming mail and delivering + outgoing mail. &os; ships with + <application>Sendmail</application> as the default + <acronym>MTA</acronym>, but it also supports numerous + other mail server daemons, including + <application>Exim</application>, + <application>Postfix</application>, and + <application>qmail</application>. + <application>Sendmail</application> configuration is + described in <xref linkend="sendmail"/>. If another + <acronym>MTA</acronym> is installed using the Ports + Collection, refer to its post-installation message for + &os;-specific configuration details and the application's + website for more general configuration + instructions.</para> + </listitem> + </varlistentry> -<varlistentry> + <varlistentry> <term>Mail Host and Mailboxes</term> <listitem> - <para>The mail host is a server that is responsible for - delivering and receiving mail for a host or a network. The - mail host collects all mail sent to the domain and stores it - either in the default <filename>mbox</filename> or the - alternative Maildir format, depending on the configuration. - Once mail has been stored, it may either be read locally using - a <acronym>MUA</acronym> or remotely accessed and collected - using protocols such as <acronym>POP</acronym> or - <acronym>IMAP</acronym>. If mail is read locally, - a <acronym>POP</acronym> or <acronym>IMAP</acronym> server - does not need to be installed.</para> - - <para>To access mailboxes remotely, a - <acronym>POP</acronym> or <acronym>IMAP</acronym> server is - required as these protocols allow users to connect to their - mailboxes from remote locations. <acronym>IMAP</acronym> offers - several advantages over <acronym>POP</acronym>. These - include the ability to store a copy of messages on a - remote server after they are downloaded and concurrent - updates. <acronym>IMAP</acronym> can be useful over - low-speed links as it allows users to fetch the - structure of messages without downloading them. It can - also perform tasks such as searching on the server in - order to minimize data transfer between clients and - servers.</para> - - <para>Several <acronym>POP</acronym> and - <acronym>IMAP</acronym> servers are available in the Ports - Collection. These include <package>mail/qpopper</package>, - <package>mail/imap-uw</package>, - <package>mail/courier-imap</package>, and - <package>mail/dovecot2</package>.</para> - - <warning> - <para>It should be noted that both <acronym>POP</acronym> - and <acronym>IMAP</acronym> transmit information, - including username and password credentials, in - clear-text. To secure the transmission of information - across these protocols, consider tunneling sessions over - &man.ssh.1; (<xref linkend="security-ssh-tunneling"/>) or - using <acronym>SSL</acronym> (<xref linkend="openssl"/>).</para> - </warning> -</listitem> -</varlistentry> + <para>The mail host is a server that is responsible for + delivering and receiving mail for a host or a network. + The mail host collects all mail sent to the domain and + stores it either in the default <filename>mbox</filename> + or the alternative Maildir format, depending on the + configuration. Once mail has been stored, it may either + be read locally using a <acronym>MUA</acronym> or remotely + accessed and collected using protocols such as + <acronym>POP</acronym> or <acronym>IMAP</acronym>. If + mail is read locally, a <acronym>POP</acronym> or + <acronym>IMAP</acronym> server does not need to be + installed.</para> + + <para>To access mailboxes remotely, a <acronym>POP</acronym> + or <acronym>IMAP</acronym> server is required as these + protocols allow users to connect to their mailboxes from + remote locations. <acronym>IMAP</acronym> offers several + advantages over <acronym>POP</acronym>. These include the + ability to store a copy of messages on a remote server + after they are downloaded and concurrent updates. + <acronym>IMAP</acronym> can be useful over low-speed links + as it allows users to fetch the structure of messages + without downloading them. It can also perform tasks such + as searching on the server in order to minimize data + transfer between clients and servers.</para> + + <para>Several <acronym>POP</acronym> and + <acronym>IMAP</acronym> servers are available in the Ports + Collection. These include + <package>mail/qpopper</package>, + <package>mail/imap-uw</package>, + <package>mail/courier-imap</package>, and + <package>mail/dovecot2</package>.</para> + + <warning> + <para>It should be noted that both <acronym>POP</acronym> + and <acronym>IMAP</acronym> transmit information, + including username and password credentials, in + clear-text. To secure the transmission of information + across these protocols, consider tunneling sessions over + &man.ssh.1; (<xref linkend="security-ssh-tunneling"/>) + or using <acronym>SSL</acronym> (<xref + linkend="openssl"/>).</para> + </warning> + </listitem> + </varlistentry> -<varlistentry> + <varlistentry> <term>Domain Name System (<acronym>DNS</acronym>)</term> <listitem> - <para>The Domain Name System (<acronym>DNS</acronym>) and its - daemon <command>named</command> play a large role in the - delivery of email. In order to deliver mail from one site to - another, the <acronym>MTA</acronym> will look up the remote - site in <acronym>DNS</acronym> to determine which host will - receive mail for the destination. This process also occurs - when mail is sent from a remote host to the - <acronym>MTA</acronym>.</para> - - <para>In addition to mapping hostnames to <acronym>IP</acronym> - addresses, <acronym>DNS</acronym> is responsible for storing information - specific to mail delivery, known as Mail eXchanger - <acronym>MX</acronym> records. The <acronym>MX</acronym> - record specifies which hosts will receive mail for a - particular domain.</para> - - <para>To view the <acronym>MX</acronym> records for a domain, - specify the type of record. Refer to &man.host.1;, for more - details about this command:</para> + <para>The Domain Name System (<acronym>DNS</acronym>) and + its daemon <command>named</command> play a large role in + the delivery of email. In order to deliver mail from one + site to another, the <acronym>MTA</acronym> will look up + the remote site in <acronym>DNS</acronym> to determine + which host will receive mail for the destination. This + process also occurs when mail is sent from a remote host + to the <acronym>MTA</acronym>.</para> + + <para>In addition to mapping hostnames to + <acronym>IP</acronym> addresses, <acronym>DNS</acronym> is + responsible for storing information specific to mail + delivery, known as Mail eXchanger + <acronym>MX</acronym> records. The <acronym>MX</acronym> + record specifies which hosts will receive mail for a + particular domain.</para> + + <para>To view the <acronym>MX</acronym> records for a + domain, specify the type of record. Refer to + &man.host.1;, for more details about this command:</para> - <screen>&prompt.user; <userinput>host -t mx FreeBSD.org</userinput> + <screen>&prompt.user; <userinput>host -t mx FreeBSD.org</userinput> FreeBSD.org mail is handled by 10 mx1.FreeBSD.org</screen> - <para>Refer to <xref linkend="network-dns"/> for more - information about <acronym>DNS</acronym> and its - configuration.</para> -</listitem> -</varlistentry> -</variablelist> + <para>Refer to <xref linkend="network-dns"/> for more + information about <acronym>DNS</acronym> and its + configuration.</para> + </listitem> + </varlistentry> + </variablelist> </sect1> <sect1 xml:id="sendmail"> - <info><title><application>Sendmail</application> Configuration</title> + <info> + <title><application>Sendmail</application> Configuration</title> + <authorgroup> - <author><personname><firstname>Christopher</firstname><surname>Shumway</surname></personname><contrib>Contributed by </contrib></author> + <author><personname><firstname>Christopher</firstname><surname>Shumway</surname></personname><contrib>Contributed + by </contrib></author> </authorgroup> </info> - <indexterm> <primary><application>Sendmail</application></primary> @@ -408,17 +420,19 @@ okay.cyberspammer.com OK routine. The message is sent to the remote host when a mail matches the left side of the table. The third entry rejects mail from a specific host on the Internet, - <systemitem>another.source.of.spam</systemitem>. The fourth entry - accepts mail connections from <systemitem class="fqdomainname">okay.cyberspammer.com</systemitem>, which is - more specific than the <systemitem class="fqdomainname">cyberspammer.com</systemitem> line above. - More specific matches override less exact matches. The last - entry allows relaying of email from hosts with an IP address - that begins with <systemitem>128.32</systemitem>. These hosts can - send mail through this mail server that is destined for other - mail servers.</para> + <systemitem>another.source.of.spam</systemitem>. The fourth + entry accepts mail connections from <systemitem + class="fqdomainname">okay.cyberspammer.com</systemitem>, + which is more specific than the <systemitem + class="fqdomainname">cyberspammer.com</systemitem> line + above. More specific matches override less exact matches. + The last entry allows relaying of email from hosts with an IP + address that begins with <systemitem>128.32</systemitem>. + These hosts can send mail through this mail server that is + destined for other mail servers.</para> - <para>Whenever this file is updated, run - <command>make</command> in <filename>/etc/mail/</filename> to update the + <para>Whenever this file is updated, run <command>make</command> + in <filename>/etc/mail/</filename> to update the database.</para> </sect2> @@ -441,24 +455,27 @@ procmail: "|/usr/local/bin/procmail"</pr <para>The mailbox name on the left side of the colon is expanded to the target(s) on the right. The first entry expands the - mailbox <systemitem class="username">root</systemitem> to the mailbox - <systemitem class="username">localuser</systemitem>, which is then looked up again - in the <filename>aliases</filename> database. If no match is - found, the message is delivered to - <systemitem class="username">localuser</systemitem>. The second entry shows a - mail list. Mail to the mailbox <systemitem class="username">ftp-bugs</systemitem> - is expanded to the three local mailboxes - <systemitem class="username">joe</systemitem>, <systemitem class="username">eric</systemitem>, and - <systemitem class="username">paul</systemitem>. A remote mailbox could be - specified as <email>user@example.com</email>. The third + mailbox <systemitem class="username">root</systemitem> to the + mailbox <systemitem class="username">localuser</systemitem>, + which is then looked up again in the + <filename>aliases</filename> database. If no match is found, + the message is delivered to <systemitem + class="username">localuser</systemitem>. The second entry + shows a mail list. Mail to the mailbox <systemitem + class="username">ftp-bugs</systemitem> is expanded to the + three local mailboxes <systemitem + class="username">joe</systemitem>, <systemitem + class="username">eric</systemitem>, and <systemitem + class="username">paul</systemitem>. A remote mailbox could + be specified as <email>user@example.com</email>. The third entry shows how to write mail to a file, in this case <filename>/dev/null</filename>. The last entry demonstrates how to send mail to a program, <filename>/usr/local/bin/procmail</filename>, through a &unix; pipe.</para> - <para>Whenever this file is updated, run - <command>make</command> in <filename>/etc/mail/</filename> to update the + <para>Whenever this file is updated, run <command>make</command> + in <filename>/etc/mail/</filename> to update the database.</para> </sect2> <sect2> @@ -466,11 +483,13 @@ procmail: "|/usr/local/bin/procmail"</pr <para>This is a list of hostnames &man.sendmail.8; is to accept as the local host name. Place any domains or hosts that - <application>Sendmail</application> will receive mail - for. For example, to configure a mail server to accept mail - for the domain <systemitem class="fqdomainname">example.com</systemitem> - and the host <systemitem class="fqdomainname">mail.example.com</systemitem>, - add these entries to + <application>Sendmail</application> will receive mail for. + For example, to configure a mail server to accept mail for the + domain <systemitem + class="fqdomainname">example.com</systemitem> and the host + <systemitem + class="fqdomainname">mail.example.com</systemitem>, add + these entries to <filename>local-host-names</filename>:</para> <programlisting>example.com @@ -478,7 +497,6 @@ mail.example.com</programlisting> <para>Whenever this file is updated, &man.sendmail.8; needs to be restarted so that it will read the changes.</para> - </sect2> <sect2> @@ -521,32 +539,38 @@ postmaster@example.com postmast </example> <para>The above example contains a mapping for the domain - <systemitem class="fqdomainname">example.com</systemitem>. This file - is processed in a first match order. The first item maps - <email>root@example.com</email> to the local mailbox - <systemitem class="username">root</systemitem>. The second entry maps - <email>postmaster@example.com</email> to the mailbox - <systemitem class="username">postmaster</systemitem> on the host <systemitem class="fqdomainname">noc.example.net</systemitem>. Finally, if - nothing from <systemitem class="fqdomainname">example.com</systemitem> - has matched so far, it will match the last mapping, which - matches every other mail message addressed to someone at - <systemitem class="fqdomainname">example.com</systemitem> to the local + <systemitem class="fqdomainname">example.com</systemitem>. + This file is processed in a first match order. The first item + maps <email>root@example.com</email> to the local mailbox + <systemitem class="username">root</systemitem>. The second + entry maps <email>postmaster@example.com</email> to the + mailbox <systemitem class="username">postmaster</systemitem> + on the host <systemitem + class="fqdomainname">noc.example.net</systemitem>. Finally, + if nothing from <systemitem + class="fqdomainname">example.com</systemitem> has matched so + far, it will match the last mapping, which matches every other + mail message addressed to someone at <systemitem + class="fqdomainname">example.com</systemitem> to the local mailbox <systemitem class="username">joe</systemitem>.</para> </sect2> </sect1> <sect1 xml:id="mail-changingmta"> - <info><title>Changing the Mail Transfer Agent</title> + <info> + <title>Changing the Mail Transfer Agent</title> + <authorgroup> - <author><personname><firstname>Andrew</firstname><surname>Boothman</surname></personname><contrib>Written by </contrib></author> + <author><personname><firstname>Andrew</firstname><surname>Boothman</surname></personname><contrib>Written + by </contrib></author> </authorgroup> <authorgroup> - <author><personname><firstname>Gregory</firstname><surname>Neil Shapiro</surname></personname><contrib>Information taken from emails written - by</contrib></author> + <author><personname><firstname>Gregory</firstname><surname>Neil + Shapiro</surname></personname><contrib>Information taken + from emails written by</contrib></author> </authorgroup> </info> - <indexterm> <primary>email</primary> @@ -568,7 +592,8 @@ postmaster@example.com postmast <title>Install a New <acronym>MTA</acronym></title> <para>A wide choice of <acronym>MTA</acronym>s is available - from the <literal>mail</literal> category of the <link linkend="ports">&os; Ports Collection</link>.</para> + from the <literal>mail</literal> category of the <link + linkend="ports">&os; Ports Collection</link>.</para> <para>Once a new <acronym>MTA</acronym> is installed, configure the new software and decide if it really fulfills your needs @@ -681,7 +706,6 @@ mailq /usr/local/supermailer/bin/mailq- newaliases /usr/local/supermailer/bin/newaliases-compat hoststat /usr/local/supermailer/bin/hoststat-compat purgestat /usr/local/supermailer/bin/purgestat-compat</programlisting> - </sect2> <sect2> @@ -693,7 +717,6 @@ purgestat /usr/local/supermailer/bin/pur reboot. Rebooting provides the opportunity to ensure that the system is correctly configured to start the new <acronym>MTA</acronym> automatically on boot.</para> - </sect2> </sect1> @@ -714,10 +737,15 @@ purgestat /usr/local/supermailer/bin/pur <answer> <para>The host may actually be in a different domain. - For example, in order for a host in <systemitem class="fqdomainname">foo.bar.edu</systemitem> to reach a host - called <systemitem>mumble</systemitem> in the <systemitem class="fqdomainname">bar.edu</systemitem> domain, refer to - it by the Fully-Qualified Domain Name - <acronym>FQDN</acronym>, <systemitem class="fqdomainname">mumble.bar.edu</systemitem>, instead of just + For example, in order for a host in <systemitem + class="fqdomainname">foo.bar.edu</systemitem> to + reach a host called <systemitem>mumble</systemitem> in + the <systemitem + class="fqdomainname">bar.edu</systemitem> domain, + refer to it by the Fully-Qualified Domain Name + <acronym>FQDN</acronym>, <systemitem + class="fqdomainname">mumble.bar.edu</systemitem>, + instead of just <systemitem>mumble</systemitem>.</para> <para>This is because the version of @@ -726,14 +754,17 @@ purgestat /usr/local/supermailer/bin/pur &os; no longer provides default abbreviations for non-FQDNs other than the local domain. An unqualified host such as - <systemitem>mumble</systemitem> must either be found as - <systemitem class="fqdomainname">mumble.foo.bar.edu</systemitem>, + <systemitem>mumble</systemitem> must either be found + as <systemitem + class="fqdomainname">mumble.foo.bar.edu</systemitem>, or it will be searched for in the root domain.</para> <para>In older versions of - <application>BIND</application>, - the search continued across <systemitem class="fqdomainname">mumble.bar.edu</systemitem>, and - <systemitem class="fqdomainname">mumble.edu</systemitem>. RFC + <application>BIND</application>, the search continued + across <systemitem + class="fqdomainname">mumble.bar.edu</systemitem>, + and <systemitem + class="fqdomainname">mumble.edu</systemitem>. RFC 1535 details why this is considered bad practice or even a security hole.</para> @@ -759,7 +790,8 @@ purgestat /usr/local/supermailer/bin/pur </question> <answer> - <para>This is answered in the <link xlink:href="http://www.sendmail.org/faq/">Sendmail + <para>This is answered in the <link + xlink:href="http://www.sendmail.org/faq/">Sendmail FAQ</link> as follows. This FAQ is recommended reading when <quote>tweaking</quote> the mail setup.</para> @@ -794,8 +826,10 @@ to /etc/mail/sendmail.cf.</programlistin <para>One way to do this is to get a full-time Internet server to provide secondary <acronym>MX</acronym><indexterm> <primary>MX record</primary></indexterm> services for the - domain. In this example, the domain is <systemitem class="fqdomainname">example.com</systemitem> and the ISP has - configured <systemitem class="fqdomainname">example.net</systemitem> to provide + domain. In this example, the domain is <systemitem + class="fqdomainname">example.com</systemitem> and the ISP + has configured <systemitem + class="fqdomainname">example.net</systemitem> to provide secondary <acronym>MX</acronym> services to the domain:</para> @@ -805,21 +839,23 @@ to /etc/mail/sendmail.cf.</programlistin <para>Only one host should be specified as the final recipient. For <application>Sendmail</application>, add <literal>Cw example.com</literal> in - <filename>/etc/mail/sendmail.cf</filename> on - <systemitem class="fqdomainname">example.com</systemitem>.</para> + <filename>/etc/mail/sendmail.cf</filename> on <systemitem + class="fqdomainname">example.com</systemitem>.</para> <para>When the sending <acronym>MTA</acronym> attempts to deliver mail, it will try to connect to the system, - <systemitem class="fqdomainname">example.com</systemitem>, over the PPP - link. This will time out if the destination is offline. - The <acronym>MTA</acronym> will automatically deliver it to - the secondary <acronym>MX</acronym> site at the Internet - Service Provider (<acronym>ISP</acronym>), <systemitem class="fqdomainname">example.net</systemitem>. The secondary - <acronym>MX</acronym> site will periodically try to connect - to the primary <acronym>MX</acronym> host, <systemitem class="fqdomainname">example.com</systemitem>.</para> + <systemitem class="fqdomainname">example.com</systemitem>, + over the PPP link. This will time out if the destination is + offline. The <acronym>MTA</acronym> will automatically + deliver it to the secondary <acronym>MX</acronym> site at + the Internet Service Provider (<acronym>ISP</acronym>), + <systemitem class="fqdomainname">example.net</systemitem>. + The secondary <acronym>MX</acronym> site will periodically + try to connect to the primary <acronym>MX</acronym> host, + <systemitem + class="fqdomainname">example.com</systemitem>.</para> - <para>Use something like this as a login - script:</para> + <para>Use something like this as a login script:</para> <programlisting>#!/bin/sh # Put me in /usr/local/bin/pppmyisp @@ -828,8 +864,9 @@ to /etc/mail/sendmail.cf.</programlistin <para>When creating a separate login script for users, instead use <command>sendmail -qRexample.com</command> in the script - above. This will force all mail in the queue for <systemitem class="fqdomainname">example.com</systemitem> to be processed - immediately.</para> + above. This will force all mail in the queue for + <systemitem class="fqdomainname">example.com</systemitem> to + be processed immediately.</para> <para>A further refinement of the situation can be seen from this example from the &a.isp;:</para> @@ -956,7 +993,8 @@ www.example.org</programlisting> <itemizedlist> <listitem> <para>Make sure that the lowest-numbered - <acronym>MX</acronym><indexterm><primary>MX record</primary></indexterm> record in + <acronym>MX</acronym><indexterm><primary>MX + record</primary></indexterm> record in <acronym>DNS</acronym> points to the host's static IP address.</para> </listitem> @@ -977,10 +1015,12 @@ example.FreeBSD.org &prompt.root; <userinput>host example.FreeBSD.org</userinput> example.FreeBSD.org has address 204.216.27.XX</screen> - <para>In this example, mail sent directly to <email role="nolink">yourlogin@example.FreeBSD.org</email> - should work without problems, assuming + <para>In this example, mail sent directly to <email + role="nolink">yourlogin@example.FreeBSD.org</email> should + work without problems, assuming <application>Sendmail</application> is running correctly on - <systemitem class="fqdomainname">example.FreeBSD.org</systemitem>.</para> + <systemitem + class="fqdomainname">example.FreeBSD.org</systemitem>.</para> <para>For this example:</para> @@ -988,9 +1028,10 @@ example.FreeBSD.org has address 204.216. example.FreeBSD.org has address 204.216.27.XX example.FreeBSD.org mail is handled (pri=10) by hub.FreeBSD.org</screen> - <para>All mail sent to <systemitem class="fqdomainname">example.FreeBSD.org</systemitem> will be - collected on <systemitem>hub</systemitem> under the same username - instead of being sent directly to your host.</para> + <para>All mail sent to <systemitem + class="fqdomainname">example.FreeBSD.org</systemitem> will + be collected on <systemitem>hub</systemitem> under the same + username instead of being sent directly to your host.</para> <para>The above information is handled by the <acronym>DNS</acronym> server. The <acronym>DNS</acronym> @@ -999,20 +1040,22 @@ example.FreeBSD.org mail is handled (pri record exists, mail will be delivered directly to the host by way of its IP address.</para> - <para>The <acronym>MX</acronym> entry for <systemitem class="fqdomainname">freefall.FreeBSD.org</systemitem> at one time looked - like this:</para> + <para>The <acronym>MX</acronym> entry for <systemitem + class="fqdomainname">freefall.FreeBSD.org</systemitem> at + one time looked like this:</para> <programlisting>freefall MX 30 mail.crl.net freefall MX 40 agora.rdrop.com freefall MX 10 freefall.FreeBSD.org freefall MX 20 who.cdrom.com</programlisting> - <para><systemitem>freefall</systemitem> had many <acronym>MX</acronym> - entries. The lowest <acronym>MX</acronym> number is the host - that receives mail directly, if available. If it is not - accessible for some reason, the next lower-numbered host will - accept messages temporarily, and pass it along when a - lower-numbered host becomes available.</para> + <para><systemitem>freefall</systemitem> had many + <acronym>MX</acronym> entries. The lowest + <acronym>MX</acronym> number is the host that receives mail + directly, if available. If it is not accessible for some + reason, the next lower-numbered host will accept messages + temporarily, and pass it along when a lower-numbered host + becomes available.</para> <para>Alternate <acronym>MX</acronym> sites should have separate Internet connections in order to be most useful. Your @@ -1053,18 +1096,24 @@ freefall MX 20 who.cdrom.com</programli provider.</para> <para>The following is an example of virtual email hosting. - Consider a customer with the domain <systemitem class="fqdomainname">customer1.org</systemitem>, where all the mail - for <systemitem class="fqdomainname">customer1.org</systemitem> should be - sent to <systemitem class="fqdomainname">mail.myhost.com</systemitem>. The + Consider a customer with the domain <systemitem + class="fqdomainname">customer1.org</systemitem>, where all + the mail for <systemitem + class="fqdomainname">customer1.org</systemitem> should be + sent to <systemitem + class="fqdomainname">mail.myhost.com</systemitem>. The <acronym>DNS</acronym> entry should look like this:</para> <programlisting>customer1.org MX 10 mail.myhost.com</programlisting> <para>An <literal>A</literal>> record is - <emphasis>not</emphasis> needed for <systemitem class="fqdomainname">customer1.org</systemitem> in order to only - handle email for that domain. However, running - <command>ping</command> against <systemitem class="fqdomainname">customer1.org</systemitem> will not work - unless an <literal>A</literal> record exists for it.</para> + <emphasis>not</emphasis> needed for <systemitem + class="fqdomainname">customer1.org</systemitem> in order to + only handle email for that domain. However, running + <command>ping</command> against <systemitem + class="fqdomainname">customer1.org</systemitem> will not + work unless an <literal>A</literal> record exists for + it.</para> <para>Tell the <acronym>MTA</acronym> which domains and/or hostnames it should accept mail for. Either of the following @@ -1074,10 +1123,10 @@ freefall MX 20 who.cdrom.com</programli <listitem> <para>Add the hosts to <filename>/etc/mail/local-host-names</filename> when - using the <literal>FEATURE(use_cw_file)</literal>. - For versions of - <application>Sendmail</application> earlier than 8.10, - edit <filename>/etc/sendmail.cw</filename> instead.</para> + using the <literal>FEATURE(use_cw_file)</literal>. For + versions of <application>Sendmail</application> earlier + than 8.10, edit <filename>/etc/sendmail.cw</filename> + instead.</para> </listitem> <listitem> @@ -1092,14 +1141,15 @@ freefall MX 20 who.cdrom.com</programli </sect1> <sect1 xml:id="outgoing-only"> - <info><title>Setting Up to Send Only</title> + <info> + <title>Setting Up to Send Only</title> + <authorgroup> - <author><personname><firstname>Bill</firstname><surname>Moran</surname></personname><contrib>Contributed by </contrib></author> + <author><personname><firstname>Bill</firstname><surname>Moran</surname></personname><contrib>Contributed + by </contrib></author> </authorgroup> </info> - - <para>There are many instances where one may only want to send mail through a relay. Some examples are:</para> @@ -1133,7 +1183,8 @@ freefall MX 20 who.cdrom.com</programli <screen>&prompt.root; <userinput>cd /usr/ports/mail/ssmtp</userinput> &prompt.root; <userinput>make install replace clean</userinput></screen> - <para>Once installed, <package>mail/ssmtp</package> can be configured with + <para>Once installed, <package>mail/ssmtp</package> can be + configured with <filename>/usr/local/etc/ssmtp/ssmtp.conf</filename>:</para> <programlisting>root=yourrealemail@example.com @@ -1141,19 +1192,19 @@ mailhub=mail.example.com rewriteDomain=example.com hostname=_HOSTNAME_</programlisting> - <para>Use the real email address for <systemitem class="username">root</systemitem>. - Enter the <acronym>ISP</acronym>'s outgoing mail relay in place - of <systemitem class="fqdomainname">mail.example.com</systemitem>. Some - <acronym>ISP</acronym>s call this the <quote>outgoing mail + <para>Use the real email address for <systemitem + class="username">root</systemitem>. Enter the + <acronym>ISP</acronym>'s outgoing mail relay in place of + <systemitem class="fqdomainname">mail.example.com</systemitem>. + Some <acronym>ISP</acronym>s call this the <quote>outgoing mail server</quote> or <quote>SMTP server</quote>).</para> - <para>Make sure to disable - <application>Sendmail</application>, including the outgoing mail - service. See <xref linkend="mail-disable-sendmail"/> for - details.</para> + <para>Make sure to disable <application>Sendmail</application>, + including the outgoing mail service. See <xref + linkend="mail-disable-sendmail"/> for details.</para> - <para><package>mail/ssmtp</package> has some - other options available. Refer to the examples in + <para><package>mail/ssmtp</package> has some other options + available. Refer to the examples in <filename>/usr/local/etc/ssmtp</filename> or the manual page of <application>ssmtp</application> for more information.</para> @@ -1175,14 +1226,18 @@ hostname=_HOSTNAME_</programlisting> <para>When using a dynamically assigned IP address and a dialup PPP connection to the Internet, one usually has a mailbox on the <acronym>ISP</acronym>'s mail server. In this example, the - <acronym>ISP</acronym>'s domain is <systemitem class="fqdomainname">example.net</systemitem>, the user name is - <systemitem class="username">user</systemitem>, the hostname is <systemitem class="fqdomainname">bsd.home</systemitem>, and the <acronym>ISP</acronym> - has allowed <systemitem class="fqdomainname">relay.example.net</systemitem> as a mail relay.</para> + <acronym>ISP</acronym>'s domain is <systemitem + class="fqdomainname">example.net</systemitem>, the user name + is <systemitem class="username">user</systemitem>, the hostname + is <systemitem class="fqdomainname">bsd.home</systemitem>, and + the <acronym>ISP</acronym> has allowed <systemitem + class="fqdomainname">relay.example.net</systemitem> as a mail + relay.</para> <para>In order to retrieve mail from the <acronym>ISP</acronym>'s mailbox, install a retrieval agent from the Ports Collection. - <package>mail/fetchmail</package> is a good - choice as it supports many different protocols. Usually, the + <package>mail/fetchmail</package> is a good choice as it + supports many different protocols. Usually, the <acronym>ISP</acronym> will provide <acronym>POP</acronym>. When using user <acronym>PPP</acronym>, email can be automatically fetched when an Internet connection is established @@ -1202,23 +1257,26 @@ hostname=_HOSTNAME_</programlisting> <programlisting> !bg su user -c "sendmail -q"</programlisting> <para>In this example, there is an account for - <systemitem class="username">user</systemitem> on <systemitem class="fqdomainname">bsd.home</systemitem>. In the home directory of - <systemitem class="username">user</systemitem> on <systemitem class="fqdomainname">bsd.home</systemitem>, create a + <systemitem class="username">user</systemitem> on <systemitem + class="fqdomainname">bsd.home</systemitem>. In the home + directory of <systemitem class="username">user</systemitem> on + <systemitem class="fqdomainname">bsd.home</systemitem>, create a <filename>.fetchmailrc</filename> which contains this line:</para> <programlisting>poll example.net protocol pop3 fetchall pass MySecret</programlisting> <para>This file should not be readable by anyone except - <systemitem class="username">user</systemitem> as it contains the password - <literal>MySecret</literal>.</para> + <systemitem class="username">user</systemitem> as it contains + the password <literal>MySecret</literal>.</para> <para>In order to send mail with the correct <literal>from:</literal> header, configure <application>Sendmail</application> to use - <email>user@example.net</email> rather than <email role="nolink">user@bsd.home</email> and to send all mail - via <systemitem class="fqdomainname">relay.example.net</systemitem>, allowing - quicker mail transmission.</para> + <email>user@example.net</email> rather than <email + role="nolink">user@bsd.home</email> and to send all mail via + <systemitem class="fqdomainname">relay.example.net</systemitem>, + allowing quicker mail transmission.</para> <para>The following <filename>.mc</filename> file should suffice:</para> @@ -1241,21 +1299,21 @@ define(`confDOMAIN_NAME',`bsd.home')dnl define(`confDELIVERY_MODE',`deferred')dnl</programlisting> <para>Refer to the previous section for details of how to convert - this file into the - <filename>sendmail.cf</filename> format. Do not forget to - restart <application>Sendmail</application> after updating - <filename>sendmail.cf</filename>.</para> + this file into the <filename>sendmail.cf</filename> format. Do + not forget to restart <application>Sendmail</application> after + updating <filename>sendmail.cf</filename>.</para> </sect1> <sect1 xml:id="SMTP-Auth"> - <info><title>SMTP Authentication</title> + <info> + <title>SMTP Authentication</title> + <authorgroup> - <author><personname><firstname>James</firstname><surname>Gorham</surname></personname><contrib>Written by </contrib></author> + <author><personname><firstname>James</firstname><surname>Gorham</surname></personname><contrib>Written + by </contrib></author> </authorgroup> </info> - - <para>Configuring <acronym>SMTP</acronym> authentication on the <acronym>MTA</acronym> provides a number of benefits. <acronym>SMTP</acronym> authentication adds a layer @@ -1275,8 +1333,8 @@ define(`confDELIVERY_MODE',`deferred')dn <step> - <para>After installing <package>security/cyrus-sasl2</package>, - edit + <para>After installing + <package>security/cyrus-sasl2</package>, edit <filename>/usr/local/lib/sasl2/Sendmail.conf</filename>, or create it if it does not exist, and add the following line:</para> @@ -1285,9 +1343,10 @@ define(`confDELIVERY_MODE',`deferred')dn </step> <step> - <para>Next, install <package>security/cyrus-sasl2-saslauthd</package> - and add the following line to - <filename>/etc/rc.conf</filename>:</para> + <para>Next, install + <package>security/cyrus-sasl2-saslauthd</package> and add + the following line to + <filename>/etc/rc.conf</filename>:</para> <programlisting>saslauthd_enable="YES"</programlisting> @@ -1297,11 +1356,10 @@ define(`confDELIVERY_MODE',`deferred')dn <para>This daemon serves as a broker for <application>sendmail</application> to authenticate against - the &os; &man.passwd.5; database. This - saves the trouble of creating a new set of usernames and - passwords for each user that needs to use - <acronym>SMTP</acronym> authentication, and keeps the login - and mail password the same.</para> + the &os; &man.passwd.5; database. This saves the trouble of + creating a new set of usernames and passwords for each user + that needs to use <acronym>SMTP</acronym> authentication, + and keeps the login and mail password the same.</para> </step> <step> @@ -1312,10 +1370,10 @@ define(`confDELIVERY_MODE',`deferred')dn SENDMAIL_LDFLAGS=-L/usr/local/lib SENDMAIL_LDADD=-lsasl2</programlisting> - <para>These lines provide - <application>Sendmail</application> the proper configuration - options for linking to <package>cyrus-sasl2</package> at compile time. - Make sure that <package>cyrus-sasl2</package> has been installed + <para>These lines provide <application>Sendmail</application> + the proper configuration options for linking to + <package>cyrus-sasl2</package> at compile time. Make sure + that <package>cyrus-sasl2</package> has been installed before recompiling <application>Sendmail</application>.</para> </step> @@ -1332,9 +1390,8 @@ SENDMAIL_LDADD=-lsasl2</programlisting> &prompt.root; <userinput>make cleandir && make obj && make && make install</userinput></screen> <para>This compile should not have any problems if - <filename>/usr/src</filename> has not - changed extensively and the shared libraries it needs are - available.</para> + <filename>/usr/src</filename> has not changed extensively + and the shared libraries it needs are available.</para> </step> <step> @@ -1358,8 +1415,9 @@ define(`confAUTH_MECHANISMS', `GSSAPI DI </step> <step> - <para>Finally, run &man.make.1; while in <filename>/etc/mail</filename>. That will run the - new <filename>.mc</filename> and create a + <para>Finally, run &man.make.1; while in + <filename>/etc/mail</filename>. That will run the new + <filename>.mc</filename> and create a <filename>.cf</filename> named either <filename>freebsd.cf</filename> or the name used for the local <filename>.mc</filename>. Then, run <command>make @@ -1377,17 +1435,20 @@ define(`confAUTH_MECHANISMS', `GSSAPI DI to <literal>13</literal> and watch <filename>/var/log/maillog</filename> for any errors.</para> - <para>For more information, refer to <link xlink:href="http://www.sendmail.org/~ca/email/auth.html">; + <para>For more information, refer to <link + xlink:href="http://www.sendmail.org/~ca/email/auth.html">; <acronym>SMTP</acronym> authentication</link>.</para> </sect1> <sect1 xml:id="mail-agents"> - <info><title>Mail User Agents</title> + <info> + <title>Mail User Agents</title> + <authorgroup> - <author><personname><firstname>Marc</firstname><surname>Silver</surname></personname><contrib>Contributed by </contrib></author> + <author><personname><firstname>Marc</firstname><surname>Silver</surname></personname><contrib>Contributed + by </contrib></author> </authorgroup> </info> - <indexterm> <primary>Mail User Agents</primary> @@ -1427,9 +1488,10 @@ define(`confAUTH_MECHANISMS', `GSSAPI DI <screen>&prompt.user; <userinput>mail</userinput></screen> *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201405091702.s49H2tjM066279>