From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 17 20:20:08 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9596AA17; Wed, 17 Apr 2013 20:20:08 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 87991369; Wed, 17 Apr 2013 20:20:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3HKK7qj040968; Wed, 17 Apr 2013 20:20:07 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3HKK7UM040967; Wed, 17 Apr 2013 20:20:07 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304172020.r3HKK7UM040967@svn.freebsd.org> From: Dru Lavigne Date: Wed, 17 Apr 2013 20:20:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41450 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Apr 2013 20:20:08 -0000 Author: dru Date: Wed Apr 17 20:20:07 2013 New Revision: 41450 URL: http://svnweb.freebsd.org/changeset/doc/41450 Log: White space fix only. Translators can ignore. Approved by: hrs (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Wed Apr 17 20:17:38 2013 (r41449) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Wed Apr 17 20:20:07 2013 (r41450) @@ -54,8 +54,8 @@ - The difference between remote and - local mailboxes. + The difference between remote and local + mailboxes. @@ -108,20 +108,18 @@ - Properly set up a network - connection (). + Properly set up a network connection (). - Properly set up the DNS - information for a mail host (). + Properly set up the DNS information + for a mail host (). - Know how to install additional - third-party software (). + Know how to install additional third-party software + (). @@ -136,7 +134,7 @@ linkend="network-servers"/>). There are five major parts involved in an email exchange: the Mail User Agent MUA>, the - Mail Transfer AgentMTA, MTA, DNS, a remote or local mailbox, and the mail host. @@ -179,11 +177,9 @@ linkend="network-servers"/>). Exim - &os; ships with -Sendmail as the default - MTA, but it also supports numerous other -mail server daemons, - including: + &os; ships with Sendmail as the + default MTA, but it also supports numerous + other mail server daemons, including: @@ -199,15 +195,13 @@ mail server daemons, - The MTA usually has two -functions. It is - responsible for receiving incoming mail as well as delivering - outgoing mail. It is not responsible - for the collection of mail using protocols such as + The MTA usually has two functions. It + is responsible for receiving incoming mail as well as + delivering outgoing mail. It is not + responsible for the collection of mail using protocols such as POP or IMAP, nor does it -allow connecting to local - mbox or Maildir mailboxes. An additional -mbox or Maildir + mailboxes. An additional daemon may be required for these functions. @@ -215,10 +209,10 @@ allow connecting to local Older versions of Sendmail contain serious security issues which may result in an attacker gaining local or remote access to the system. - Run a current version to &os; to avoid - these problems. Optionally, install an alternative - MTA from the &os; - Ports Collection. + Run a current version to &os; to avoid these problems. + Optionally, install an alternative MTA + from the &os; Ports + Collection. @@ -226,14 +220,13 @@ allow connecting to local Email and DNS The Domain Name System (DNS) and its -daemon - named play a large role in the delivery - of email. In order to deliver mail from one site to another, - the MTA will look up the remote site in -DNS - to determine which host will receive mail for the - destination. This process also occurs when mail is sent from - a remote host to the MTA. + daemon named play a large role in the + delivery of email. In order to deliver mail from one site to + another, the MTA will look up the remote + site in DNS to determine which host will + receive mail for the destination. This process also occurs + when mail is sent from a remote host to the + MTA. MX record @@ -243,17 +236,16 @@ daemon hostnames to IP addresses, as well as for storing information specific to mail delivery, known as Mail eXchanger MX records. The MX -record specifies which host, or hosts, will receive - mail for a particular domain. If there is no -MX record - for the hostname or domain, the mail will be delivered + record specifies which host, or hosts, will receive mail for a + particular domain. If there is no MX + record for the hostname or domain, the mail will be delivered directly to the host, provided there is an -A record pointing - the hostname to the IP address. + A record pointing the hostname to the IP + address. To view the MX records for a domain, -specify the type of record using - &man.host.1;, as seen in the example below: + specify the type of record using &man.host.1;, as seen in the + example below: &prompt.user; host -t mx FreeBSD.org FreeBSD.org mail is handled by 10 mx1.FreeBSD.org @@ -270,14 +262,13 @@ FreeBSD.org mail is handled by 10 mx1.Fr Receiving mail for a domain is done by the mail host. It will collect all mail sent to the domain and store it either in the default mbox or the -alternative Maildir format, depending on the - configuration. Once mail has been stored, it may either be - read locally using a - MUA, or remotely accessed and - collected using protocols such as POP or + alternative Maildir format, depending on the configuration. + Once mail has been stored, it may either be read locally using + a MUA, or remotely accessed and collected + using protocols such as POP or IMAP. In order to read mail locally, - a POP or IMAP - server does not need to be installed. + a POP or IMAP server + does not need to be installed. Accessing Remote Mailboxes Using <acronym>POP</acronym> @@ -286,14 +277,12 @@ alternative Maildir format, depending on <indexterm><primary>POP</primary></indexterm> <indexterm><primary>IMAP</primary></indexterm> <para>To access mailboxes remotely, access to a -<acronym>POP</acronym> or - <acronym>IMAP</acronym> server is required. These protocols -allow users - to connect to their mailboxes from remote locations. Though -both <acronym>POP</acronym> and - <acronym>IMAP</acronym> allow users to remotely access - mailboxes, <acronym>IMAP</acronym> offers many advantages, - including:</para> + <acronym>POP</acronym> or <acronym>IMAP</acronym> server is + required. These protocols allow users to connect to their + mailboxes from remote locations. Though both + <acronym>POP</acronym> and <acronym>IMAP</acronym> allow + users to remotely access mailboxes, <acronym>IMAP</acronym> + offers many advantages, including:</para> <itemizedlist> <listitem> @@ -324,9 +313,8 @@ both <acronym>POP</acronym> and <procedure> <step> <para>Use the Ports Collection to install an -<acronym>IMAP</acronym> or - <acronym>POP</acronym> server. The following -<acronym>POP</acronym> and + <acronym>IMAP</acronym> or <acronym>POP</acronym> + server. The following <acronym>POP</acronym> and <acronym>IMAP</acronym> servers are well known:</para> <itemizedlist> @@ -360,12 +348,12 @@ both <acronym>POP</acronym> and <step> <para>Where required, use the startup script that came - with the application to load the - <acronym>POP</acronym> or <acronym>IMAP</acronym> - server. Those programs will also provide a variable - which can be added to <filename>/etc/rc.conf</filename> - to automate the startup of the application's daemon - whenever the system boots.</para> + with the application to load the <acronym>POP</acronym> + or <acronym>IMAP</acronym> server. Those programs will + also provide a variable which can be added to + <filename>/etc/rc.conf</filename> to automate the + startup of the application's daemon whenever the system + boots.</para> </step> </procedure> @@ -373,12 +361,10 @@ both <acronym>POP</acronym> and <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 -SSL (<xref linkend="openssl"/>).</para> + 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 SSL (<xref linkend="openssl"/>).</link>.</para> </warning> </sect3> @@ -388,7 +374,7 @@ SSL (<xref linkend="openssl"/>).</para> <para>Mailboxes may be accessed locally by directly using an <acronym>MUA</acronym> on the server on which the mailbox resides. This can be done using a built-in application -such as &man.mail.1; or by installing a + such as &man.mail.1; or by installing a <acronym>MUA</acronym> from the Ports Collection..</para> </sect3> </sect2> @@ -398,9 +384,8 @@ such as &man.mail.1; or by installing a <indexterm><primary>mail host</primary></indexterm> - <para>The mail host is a server that is - responsible for delivering and receiving mail for a host, - or a network.</para> + <para>The mail host is a server that is responsible for + delivering and receiving mail for a host, or a network.</para> </sect2> </sect1> @@ -422,12 +407,12 @@ such as &man.mail.1; or by installing a <para>&man.sendmail.8; is the default <acronym>MTA</acronym> which is installed with &os;. -<application>Sendmail</application> - accepts mail from <acronym>MUA</acronym>s and - delivers it to the appropriate mailer as defined by its - configuration file. <application>Sendmail</application> can - also accept network connections and deliver mail to local - mailboxes or to another program.</para> + <application>Sendmail</application> accepts mail from + <acronym>MUA</acronym>s and delivers it to the appropriate + mailer as defined by its configuration file. + <application>Sendmail</application> can also accept network + connections and deliver mail to local mailboxes or to another + program.</para> <para><application>Sendmail</application> uses the following configuration files. This section describes these files in more @@ -521,9 +506,8 @@ such as &man.mail.1; or by installing a passed to <application>Sendmail</application>'s error handling routine with a given mailer error. Hosts that are listed as <option>OK</option>, which is the default -option, - are allowed to send mail to this host as long as the mail's - final destination is the local machine. Hosts that are + option, are allowed to send mail to this host as long as the + mail's final destination is the local machine. Hosts that are listed as <option>REJECT</option> are rejected for all mail connections. Hosts that are listed as <option>RELAY</option> are allowed to send mail for any @@ -540,37 +524,37 @@ okay.cyberspammer.com OK 128.32 RELAY</programlisting> </example> - <para>This example shows five entries. Mail senders that - match the left side of the table are affected by the - action on the right side of the table. The first two examples - give an error code to <application>Sendmail</application>'s - error handling 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, <hostid>another.source.of.spam</hostid>. The fourth - entry accepts mail connections from <hostid + <para>This example shows five entries. Mail senders that match + the left side of the table are affected by the action on the + right side of the table. The first two examples give an error + code to <application>Sendmail</application>'s error handling + 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, + <hostid>another.source.of.spam</hostid>. The fourth entry + accepts mail connections from <hostid role="fqdn">okay.cyberspammer.com</hostid>, which is more specific than the <hostid role="domainname">cyberspammer.com</hostid> 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 <hostid>128.32</hostid>. These - hosts can send mail through this mail server - that is destined for other mail servers.</para> + entry allows relaying of email from hosts with an IP address + that begins with <hostid>128.32</hostid>. 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 -class="directory">/etc/mail/</filename> - to update the database.</para> + class="directory">/etc/mail/</filename> to update the + database.</para> </sect2> <sect2> <title><filename>/etc/mail/aliases</filename> - This database contains a list of virtual mailboxes - that are expanded to other user(s), files, programs, or other + This database contains a list of virtual mailboxes that + are expanded to other user(s), files, programs, or other aliases. Here are a few examples to illustrate the -file format: + file format: Mail Aliases @@ -581,20 +565,18 @@ bit.bucket: /dev/null procmail: "|/usr/local/bin/procmail" - 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 - root to the mailbox + 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 root to the mailbox localuser, which is then looked up again in the aliases database. If no match is -found, the - message is delivered to + found, the message is delivered to localuser. The second entry shows a mail list. Mail to the mailbox ftp-bugs is expanded to the three local mailboxes joe, eric, and - paul. A remote mailbox could - be specified as user@example.com. The third + paul. A remote mailbox could be + specified as user@example.com. The third entry shows how to write mail to a file, in this case /dev/null. The last entry demonstrates how to send mail to a program, @@ -603,8 +585,8 @@ found, the Whenever this file is updated, run make in /etc/mail/ - to update the database. + class="directory">/etc/mail/ to update the + database. <filename>/etc/mail/local-host-names</filename> @@ -612,11 +594,10 @@ class="directory">/etc/mail/ This is a list of hostnames &man.sendmail.8; is to accept as the local host name. Place any domains or hosts that Sendmail will receive mail - for. For example, to configure a mail server to accept -mail for - the domain example.com and - the host mail.example.com, add -these entries to + for. For example, to configure a mail server to accept mail + for the domain example.com + and the host mail.example.com, + add these entries to local-host-names: example.com @@ -630,15 +611,13 @@ mail.example.com <filename>/etc/mail/sendmail.cf</filename> - This is the master -configuration file for Sendmail. It -controls the overall + This is the master configuration file for + Sendmail. It controls the overall behavior of Sendmail, including everything from rewriting email addresses to printing rejection messages to remote mail servers. Accordingly, this -configuration file is quite complex. Fortunately, this - file rarely needs to be changed for standard mail - servers. + configuration file is quite complex. Fortunately, this file + rarely needs to be changed for standard mail servers. The master Sendmail configuration file can be built from &man.m4.1; macros that define the @@ -670,18 +649,17 @@ postmaster@example.com postmast The above example contains a mapping for the domain example.com. This file - is processed in a first match order. The first - item maps root@example.com to the local mailbox + is processed in a first match order. The first item maps + root@example.com to the local mailbox root. The second entry maps postmaster@example.com to the mailbox - postmaster on the host - noc.example.net. Finally, if + postmaster on the host noc.example.net. Finally, if nothing from example.com has matched so far, it will match the last mapping, which matches every other mail message addressed to someone at example.com to the local -mailbox - joe. + mailbox joe. @@ -711,56 +689,47 @@ mailbox change mta - &os; comes with - Sendmail already installed as the - MTA which is - in charge of outgoing and incoming mail. - - However, the system - administrator can change the system's MTA. -The - reasons for doing so range from wanting to try out -another MTA to - needing a specific feature or package which relies on another - MTA. Whatever the reason, -&os; makes it + &os; comes with Sendmail already + installed as the MTA which is in charge of + outgoing and incoming mail. + + However, the system administrator can change the system's + MTA. The reasons for doing so range from + wanting to try out another MTA to needing a + specific feature or package which relies on another + MTA. Whatever the reason, &os; makes it easy to make the change. Install a New <acronym>MTA</acronym> A wide choice of MTAs is available -from the mail category of the - &os; Ports Collection. + from the mail category of the &os; Ports Collection. - Once a new MTA is installed, -configure the - new software and decide if it really fulfills your needs + Once a new MTA is installed, configure + the new software and decide if it really fulfills your needs before replacing Sendmail. Refer to the new chosen MTA's -documentation for - information on how to configure the software. + documentation for information on how to configure the + software. Disable <application>Sendmail</application> - If Sendmail's - outgoing mail service is disabled, it is important that it -is replaced + If Sendmail's outgoing mail + service is disabled, it is important that it is replaced with an alternative mail delivery system. Otherwise, system -functions such as - &man.periodic.8; will be unable to deliver their results - by email. Many parts of - the system expect a functional - MTA. If - applications continue to use - Sendmail's binaries to try to - send email they are disabled, mail could go - into an inactive Sendmail queue, - and never be delivered. + functions such as &man.periodic.8; will be unable to deliver + their results by email. Many parts of the system expect a + functional MTA. If applications continue + to use Sendmail's binaries to try + to send email they are disabled, mail could go into an + inactive Sendmail queue, and + never be delivered. In order to completely disable @@ -773,9 +742,8 @@ sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" - To only disable - Sendmail's incoming mail service, - set + To only disable Sendmail's + incoming mail service, set sendmail_enable="NO" @@ -788,9 +756,8 @@ sendmail_msp_queue_enable="NO"Running the New MTA on Boot The new MTA can be started during -boot by adding a - configuration line to /etc/rc.conf. - This example enables the + boot by adding a configuration line to + /etc/rc.conf. This example enables the Postfix MTA: &prompt.root; echo @@ -798,35 +765,33 @@ boot by adding a >> /etc/rc.conf The specified MTA will now be -automatically started during - boot. + automatically started during boot. Replacing <application>Sendmail</application> as the System's Default Mailer - Sendmail is so - ubiquitous as standard software on &unix; systems that some - software assumes it is already installed and configured. - For this reason, many alternative MTAs -provide their own + Sendmail is so ubiquitous as + standard software on &unix; systems that some software assumes + it is already installed and configured. For this reason, many + alternative MTAs provide their own compatible implementations of the Sendmail command-line interface in -order to - facilitate using them as drop-in + order to facilitate using them as drop-in replacements for Sendmail. When using an alternative MTA, - make sure that software trying to execute - standard Sendmail binaries, such as + make sure that software trying to execute standard + Sendmail binaries, such as /usr/bin/sendmail, actually execute - the chosen mailer instead. Fortunately, &os; provides - a system called &man.mailwrapper.8; for this purpose. + the chosen mailer instead. Fortunately, &os; provides a + system called &man.mailwrapper.8; for this purpose. When Sendmail is operating as installed, -/etc/mail/mailer.conf will look like this: + /etc/mail/mailer.conf will look like + this: sendmail /usr/libexec/sendmail/sendmail send-mail /usr/libexec/sendmail/sendmail @@ -835,19 +800,17 @@ newaliases /usr/libexec/sendmail/sendmai hoststat /usr/libexec/sendmail/sendmail purgestat /usr/libexec/sendmail/sendmail - When any of the commands listed on the left - are run, + When any of the commands listed on the left are run, the system actually executes the associated command shown on the right instead. This system makes it easy to change what -binaries - are executed when these default + binaries are executed when these default Sendmail functions are invoked. As an example, to run /usr/local/supermailer/bin/sendmail-compat instead of Sendmail, specify the paths to the installed applications in -/etc/mail/mailer.conf: + /etc/mail/mailer.conf: sendmail /usr/local/supermailer/bin/sendmail-compat send-mail /usr/local/supermailer/bin/sendmail-compat @@ -862,13 +825,11 @@ purgestat /usr/local/supermailer/bin/pur Finishing Once everything is configured, either kill the -unneeded - sendmail processes and start -the processes belonging to the - new software, or reboot. Rebooting provides the -opportunity to ensure that the system is correctly configured to start -the new MTA automatically - on boot. + unneeded sendmail processes and + start the processes belonging to the new software, or + reboot. Rebooting provides the opportunity to ensure that + the system is correctly configured to start the new + MTA automatically on boot. @@ -889,13 +850,12 @@ the new MTA automatic - The host may actually be - in a different domain. For example, in order for a -host in - foo.bar.edu - to reach a host called mumble in the - bar.edu domain, - refer to it by the Fully-Qualified Domain Name + The host may actually be in a different domain. + For example, in order for a host in foo.bar.edu to reach a host + called mumble in the bar.edu domain, refer to + it by the Fully-Qualified Domain Name FQDN, mumble.bar.edu, instead of just mumble. @@ -904,23 +864,21 @@ host in This is because the version of BIND which ships with &os; no longer provides default abbreviations - for non-FQDNs other than the local - domain. An unqualified host such as + for non-FQDNs other than the local domain. An + unqualified host such as mumble must either be found as mumble.foo.bar.edu, - or it will be searched for in the root - domain. + or it will be searched for in the root domain. In older versions of BIND, the search continued across mumble.bar.edu, and mumble.edu. RFC -1535 details why this is considered bad - practice or even a security hole. + 1535 details why this is considered bad practice or + even a security hole. - As a good workaround, place the - line: + As a good workaround, place the line: search foo.bar.edu bar.edu @@ -942,11 +900,9 @@ host in - This is answered in the - This is answered in the Sendmail - FAQ as follows. This FAQ is -recommended reading + FAQ as follows. This FAQ is recommended reading when tweaking the mail setup. I'm getting these error messages: @@ -975,46 +931,41 @@ to /etc/mail/sendmail.cf. Connect to a &os; mail gateway on the LAN. The PPP -connection is non-dedicated. + connection is non-dedicated. MX record One way to do this is to get a full-time Internet server -to - provide secondary MX services for the -domain. In this example, - the domain is MX services for the + domain. In this example, the domain is example.com and the ISP has -configured example.net to provide secondary MX services to the -domain: + domain: example.com. MX 10 example.com. MX 20 example.net. Only one host should be specified as the final -recipient. For Sendmail, - add Cw example.com in + recipient. For Sendmail, add + Cw example.com in /etc/mail/sendmail.cf on example.com. When the sending MTA attempts to deliver mail, it will try to connect to the system, -example.com, over the PPP + example.com, over the PPP link. This will time out if the destination is offline. - The MTA - will automatically deliver it to the secondary -MX site at the Internet Service - Provider (ISP), MTA will automatically deliver it to + the secondary MX site at the Internet + Service Provider (ISP), example.net. The secondary - MX site will periodically try to -connect to - the primary MX host, - example.com. + MX site will periodically try to connect + to the primary MX host, example.com. Use something like this as a login script: @@ -1024,10 +975,9 @@ connect to ( sleep 60 ; /usr/sbin/sendmail -q ) & /usr/sbin/ppp -direct pppmyisp - When creating a separate login script for - users, instead use sendmail - -qRexample.com in the script above. - This will force all mail in the queue for When creating a separate login script for users, instead + use sendmail -qRexample.com in the script + above. This will force all mail in the queue for example.com to be processed immediately. @@ -1075,31 +1025,28 @@ the DNS for customer.com. In a default &os; installation, Sendmail is configured to only send mail from the host it is running on. For example, - if a POP server is available, - users will be able to check mail from remote locations but -they will not be able - to send outgoing emails from outside locations. - Typically, a few moments after the attempt, an email will - be sent from MAILER-DAEMON + if a POP server is available, users + will be able to check mail from remote locations but they + will not be able to send outgoing emails from outside + locations. Typically, a few moments after the attempt, an + email will be sent from MAILER-DAEMON with a 5.7 Relaying Denied. - The most - straightforward solution is to add the ISP's FQDN to - /etc/mail/relay-domains, as -seen in this example: + The most straightforward solution is to add the ISP's + FQDN to /etc/mail/relay-domains, as + seen in this example: &prompt.root; echo "your.isp.example.com" > /etc/mail/relay-domains After creating or editing this file, restart Sendmail. This works great if - the server administrator does not wish to send - mail locally, would like to use a MUA -on a + the server administrator does not wish to send mail + locally, would like to use a MUA on a remote machine, or would like to use another - ISP for remote connections. It - is also useful when there is only one or two email - accounts. If there are a large number of addresses, - add them one per line: + ISP for remote connections. It is also + useful when there is only one or two email accounts. If + there are a large number of addresses, add them one per + line: your.isp.example.com other.isp.example.net @@ -1107,11 +1054,10 @@ users-isp.example.org www.example.org Now any mail sent through the system by any host in - this list, provided the user has an account on the - system, will succeed. This allows - users to send mail from the system remotely without - opening the system up to relaying SPAM from the - Internet. + this list, provided the user has an account on the system, + will succeed. This allows users to send mail from the + system remotely without opening the system up to relaying + SPAM from the Internet. @@ -1121,9 +1067,8 @@ www.example.org Advanced Topics - This section covers more involved topics such as - mail configuration and setting up mail for an entire - domain. + This section covers more involved topics such as mail + configuration and setting up mail for an entire domain. Basic Configuration @@ -1133,13 +1078,11 @@ www.example.org configuration - Out of the box, one can send email to - external hosts as long as - /etc/resolv.conf is configured or the -network has access to a configured + Out of the box, one can send email to external hosts as + long as /etc/resolv.conf is configured or + the network has access to a configured DNS server. If order to have mail - delivered to the MTA on the &os; -host, + delivered to the MTA on the &os; host, do one of the following: @@ -1155,27 +1098,24 @@ host, SMTP - In order - to have mail delivered directly to a host, it must have - a permanent static IP address, not a dynamic IP address. If -the system is behind a - firewall, it must be configured to allow SMTP traffic. - To receive mail directly at a host, one of these two -must be configured: + In order to have mail delivered directly to a host, it + must have a permanent static IP address, not a dynamic IP + address. If the system is behind a firewall, it must be + configured to allow SMTP traffic. To receive mail directly at + a host, one of these two must be configured: MX record Make sure that the lowest-numbered -MX record in + MX record in DNS points to the host's static IP -address. + address. Make sure there is no MX entry in -the DNS for the - host. + the DNS for the host. @@ -1189,8 +1129,8 @@ example.FreeBSD.org &prompt.root; host example.FreeBSD.org example.FreeBSD.org has address 204.216.27.XX - In this example, mail sent directly to - yourlogin@example.FreeBSD.org + In this example, mail sent directly to yourlogin@example.FreeBSD.org should work without problems, assuming Sendmail is running correctly on example.FreeBSD.org. @@ -1206,14 +1146,12 @@ example.FreeBSD.org mail is handled (pri collected on hub under the same username instead of being sent directly to your host. - The above information is handled by -the DNS server. - The DNS record that carries mail routing -information is the - MX entry. - If no MX record exists, mail will be -delivered directly to - the host by way of its IP address. + The above information is handled by the + DNS server. The DNS + record that carries mail routing information is the + MX entry. If no MX + record exists, mail will be delivered directly to the host by + way of its IP address. The MX entry for freefall.FreeBSD.org at one time looked @@ -1226,35 +1164,30 @@ freefall MX 20 who.cdrom.comfreefall had many MX entries. The lowest MX 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. + 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. Alternate MX sites should have separate -Internet - connections in order to be most useful. Your - ISP can provide - this service. + Internet connections in order to be most useful. Your + ISP can provide this service. Mail for a Domain When configuring a MTA for a network, -any mail sent to hosts in its - domain should be diverted to the + any mail sent to hosts in its domain should be diverted to the MTA so that users can receive their mail on -the master - mail server. + the master mail server. DNS To make life easiest, a user account with the same username should exist on both the MTA and the system with the - MUA. - Use &man.adduser.8; to create the user accounts. + MUA. Use &man.adduser.8; to create the + user accounts. The MTA must be the designated mail exchanger for each workstation on the network. This is done @@ -1266,8 +1199,7 @@ the master This will redirect mail for the workstation to the MTA no matter where the A record points. -The mail is - sent to the MX host. + The mail is sent to the MX host. This must be configured on a DNS server. If the network does not run its own @@ -1276,30 +1208,25 @@ The mail is provider. he following is an example of virtual email hosting. -Consider a customer with the domain - customer1.org, where *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***