From owner-svn-doc-projects@FreeBSD.ORG Mon Apr 15 15:03:48 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 4CAFF710; Mon, 15 Apr 2013 15:03:48 +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 3ECCA78C; Mon, 15 Apr 2013 15:03:48 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3FF3m0t060117; Mon, 15 Apr 2013 15:03:48 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3FF3m3X060116; Mon, 15 Apr 2013 15:03:48 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304151503.r3FF3m3X060116@svn.freebsd.org> From: Dru Lavigne Date: Mon, 15 Apr 2013 15:03:48 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41433 - 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: Mon, 15 Apr 2013 15:03:48 -0000 Author: dru Date: Mon Apr 15 15:03:47 2013 New Revision: 41433 URL: http://svnweb.freebsd.org/changeset/doc/41433 Log: Initial patch which fixes the following. Subsequent patches will follow. - fixes &os;, e-mail, and directory tags - fixes acronyms - reworded to remove you, please, simply - inetd reference removed - modernized the host output - grammo fixes - remove non-existing ports (devel) - remove UUCP section Reviewed by: gjb (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 Mon Apr 15 15:00:34 2013 (r41432) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Mon Apr 15 15:03:47 2013 (r41433) @@ -35,23 +35,22 @@ 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;; however, it is not a complete - reference and in fact many important considerations are omitted. - For more complete coverage of the subject, the reader is - referred to the many excellent books listed in + receiving email using &os;. + For more complete coverage of this subject, + refer to the books listed in . After reading this chapter, you will know: - What software components are involved in sending and + Which software components are involved in sending and receiving electronic mail. Where basic sendmail - configuration files are located in FreeBSD. + configuration files are located in &os;. @@ -60,13 +59,13 @@ - How to block spammers from illegally using your mail + How to block spammers from illegally using a mail server as a relay. How to install and configure an alternate Mail Transfer - Agent on your system, replacing + Agent, replacing sendmail. @@ -75,10 +74,6 @@ - How to use SMTP with UUCP. - - - How to set up the system to send mail only. @@ -87,18 +82,18 @@ - How to configure SMTP Authentication for added + How to configure SMTP authentication for added security. How to install and use a Mail User Agent, such as - mutt to send and receive + mutt, to send and receive email. - How to download your mail from a remote + How to download mail from a remote POP or IMAP server. @@ -113,18 +108,20 @@ - Properly set up your network connection - (). + Properly set up a network + connection. - Properly set up the DNS information for your 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,41 +133,42 @@ IMAP DNS - There are five major parts involved in an email exchange. - They are: the user program, - the server daemon, DNS, a - remote or local mailbox, and of course, the mailhost itself. + There are five major parts involved in an email exchange: + the Mail User Agent + MUA>, the + Mail Transfer AgentMTA, DNS, a remote or local mailbox, and + the mail host. - The User Program + The Mail User Agent This includes command line programs such as mutt, alpine, elm, and - mail, and GUI - programs such as balsa, - xfmail to name a few, and something - more sophisticated like a WWW browser. These - programs simply pass off the email transactions to the local - mailhost, - either by calling one of the server - daemons available, or delivering it over - TCP. + mail, GUI programs such + as balsa or + xfmail, and web mail programs + which can be accessed from a web browser. User programs pass + the email transactions to the local mail host, either + by a MTA, or by + delivering it over TCP. - Mailhost Server Daemon + The Mail Transfer Agent mail server daemons - sendmail + Sendmail mail server daemons - postfix + Postfix mail server daemons @@ -178,20 +176,22 @@ mail server daemons - exim + Exim - &os; ships with sendmail by - default, but also support numerous other mail server daemons, - just some of which include: + &os; ships with +Sendmail as the default + MTA, but it also supports numerous other +mail server daemons, + including: - exim; + Exim; - postfix; + Postfix; @@ -199,21 +199,23 @@ - The server daemon usually has two functions—it is + 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 to read - your email, nor does it allow connecting to local - mbox or Maildir mailboxes. You may - require an additional daemon for that. + POP or IMAP, nor does it +allow connecting to local + mbox or Maildir mailboxes. An additional +daemon may be required for + these functions. - Older versions of sendmail - have some serious security issues which may result in an - attacker gaining local and/or remote access to your machine. - Make sure that you are running a current version to avoid + 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. @@ -223,13 +225,15 @@ Email and DNS - The Domain Name System (DNS) and its daemon + The Domain Name System (DNS) and its +daemon named play a large role in the delivery - of email. In order to deliver mail from your site to another, - the server daemon will look up the remote site in the DNS - to determine the host that will receive mail for the + 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 your mail server. + a remote host to the MTA. MX record @@ -237,18 +241,22 @@ DNS is responsible for mapping hostnames to IP addresses, as well as for storing information - specific to mail delivery, known as MX records. The MX (Mail - eXchanger) record specifies which host, or hosts, will receive - mail for a particular domain. If you do not have an MX record - for your hostname or domain, the mail will be delivered - directly to your host provided you have an A record pointing - your hostname to your IP address. - - You may view the MX records for any domain by using the - &man.host.1; command, as seen in the example below: + 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 + directly to the host, provided there is an +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: &prompt.user; host -t mx FreeBSD.org -FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org +FreeBSD.org mail is handled by 10 mx1.FreeBSD.org @@ -259,33 +267,33 @@ FreeBSD.org mail is handled (pri=10) by receiving - Receiving mail for your domain is done by the mail host. - It will collect all mail sent to your domain and store it - either in mbox (the default method for - storing mail) or Maildir format, depending on your + 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 applications such as &man.mail.1; or - mutt, or remotely accessed and + read locally using a + MUA, or remotely accessed and collected using protocols such as POP or - IMAP. This means that should you only - wish to read mail locally, you are not required to install + IMAP. In order to read mail locally, a POP or IMAP - server. + server does not need to be installed. - Accessing remote mailboxes using <acronym>POP</acronym> + <title>Accessing Remote Mailboxes Using <acronym>POP</acronym> and <acronym>IMAP</acronym> POP IMAP - In order to access mailboxes remotely, you are required - to have access to a POP or - IMAP server. These protocols allow users - to connect to their mailboxes from remote locations with - ease. Though both POP and + To access mailboxes remotely, access to a +POP or + IMAP server is required. These protocols +allow users + to connect to their mailboxes from remote locations. Though +both POP and IMAP allow users to remotely access mailboxes, IMAP offers many advantages, - some of which are: + including: @@ -299,9 +307,9 @@ FreeBSD.org mail is handled (pri=10) by - IMAP can be extremely useful over + IMAP can be useful over low-speed links as it allows users to fetch the - structure of messages without downloading them; it can + 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. @@ -315,70 +323,74 @@ FreeBSD.org mail is handled (pri=10) by - Choose an IMAP or - POP server that best suits your - needs. The following POP and - IMAP servers are well known and serve - as some good examples: + Use the Ports Collection to install an +IMAP or + POP server. The following +POP and + IMAP servers are well known: - qpopper; + mail/qpopper - teapop; + mail/teapop - imap-uw; + mail/imap-uw - courier-imap; + mail/courier-imap - dovecot; + mail/dovecot2 - Install the POP or - IMAP daemon of your choosing from - the ports collection. - - - - Where required, modify - /etc/inetd.conf to load the + Where required, use the startup script that came + with the application to load the POP or IMAP - server. + server. Those programs will also provide a variable + which can be added to /etc/rc.conf + to automate the startup of the application's daemon + whenever the system boots. It should be noted that both POP and IMAP transmit information, - including username and password credentials in clear-text. - This means that if you wish to secure the transmission - of information across these protocols, you should consider - tunneling sessions over &man.ssh.1; or using SSL. - Tunneling sessions is described in - and SSL is - described in . + including username and password credentials, in +clear-text. + To secure the transmission + of information across these protocols, consider + tunneling sessions over +&man.ssh.1; or using SSL.. Accessing Local Mailboxes - Mailboxes may be accessed locally by directly utilizing - MUAs on the server on which the mailbox - resides. This can be done using applications such as - mutt or &man.mail.1;. + Mailboxes may be accessed locally by directly using an + MUA 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 + MUA from the Ports Collection.. @@ -387,9 +399,9 @@ FreeBSD.org mail is handled (pri=10) by mail host - The mail host is the name given to a server that is - responsible for delivering and receiving mail for your host, - and possibly your network. + The mail host is a server that is + responsible for delivering and receiving mail for a host, + or a network. @@ -403,22 +415,24 @@ FreeBSD.org mail is handled (pri=10) by - <application>sendmail</application> Configuration + <application>Sendmail</application> Configuration - sendmail + Sendmail - &man.sendmail.8; is the default Mail Transfer Agent (MTA) - in FreeBSD. sendmail's job is to - accept mail from Mail User Agents (MUA) and - deliver it to the appropriate mailer as defined by its - configuration file. sendmail can + &man.sendmail.8; is the default MTA + which is installed with &os;. +Sendmail + accepts mail from MUAs and + delivers it to the appropriate mailer as defined by its + configuration file. Sendmail can also accept network connections and deliver mail to local - mailboxes or deliver it to another program. + mailboxes or to another program. - sendmail uses the following - configuration files: + Sendmail uses the following + configuration files. This section describes these files in more + detail. /etc/mail/access @@ -453,8 +467,8 @@ FreeBSD.org mail is handled (pri=10) by /etc/mail/access - sendmail access database - file + Sendmail access database + file. @@ -466,33 +480,33 @@ FreeBSD.org mail is handled (pri=10) by /etc/mail/local-host-names - Lists of hosts sendmail - accepts mail for + Lists of hosts Sendmail + accepts mail for. /etc/mail/mailer.conf - Mailer program configuration + Mailer program configuration. /etc/mail/mailertable - Mailer delivery table + Mailer delivery table. /etc/mail/sendmail.cf - sendmail master - configuration file + Sendmail master + configuration file. /etc/mail/virtusertable - Virtual users and domain tables + Virtual users and domain tables. @@ -501,22 +515,23 @@ FreeBSD.org mail is handled (pri=10) by <filename>/etc/mail/access</filename> - The access database defines what host(s) or IP addresses + This database defines which host(s) or IP addresses have access to the local mail server and what kind of access they have. Hosts can be listed as , - , or simply - passed to sendmail's error + , or , or can be + passed to Sendmail's error handling routine with a given mailer error. Hosts that - are listed as , which is the default, + are listed as , 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 listed as are rejected for all mail - connections. Hosts that have the - option for their hostname are allowed to send mail for any - destination through this mail server. + connections. Hosts that are listed as + are allowed to send mail for any + destination using this mail server. - Configuring the <application>sendmail</application> + <title>Configuring the <application>Sendmail</application> Access Database cyberspammer.com 550 We do not accept mail from spammers @@ -526,36 +541,37 @@ okay.cyberspammer.com OK 128.32 RELAY - In this example we have five entries. Mail senders that - match the left hand side of the table are affected by the + 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 sendmail's - error handling routine. The message is printed to the remote - host when a mail matches the left hand side of the table. - The next entry rejects mail from a specific host on the - Internet, another.source.of.spam. The next - entry accepts mail connections from a host Sendmail'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, another.source.of.spam. The fourth + entry accepts mail connections from okay.cyberspammer.com, which is - more exact than the cyberspammer.com line above. More specific matches override less exact matches. The last - entry allows relaying of electronic mail from hosts with an + entry allows relaying of email from hosts with an IP address that begins with 128.32. These - hosts would be able to send mail through this mail server - that are destined for other mail servers. + hosts can send mail through this mail server + that is destined for other mail servers. - When this file is updated, you need to run - make in /etc/mail/ + Whenever this file is updated, run + make in /etc/mail/ to update the database. <filename>/etc/mail/aliases</filename> - The aliases database contains a list of virtual mailboxes - that are expanded to other user(s), files, programs or other - aliases. Here are a few examples that can be used in - /etc/mail/aliases: + 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: Mail Aliases @@ -566,28 +582,29 @@ bit.bucket: /dev/null procmail: "|/usr/local/bin/procmail" - The file format is simple; the mailbox name on the left + The mailbox name on the left side of the colon is expanded to the target(s) on the right. - The first example expands the mailbox + 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, then the - message is delivered to the local user - localuser. The next example shows a + in the aliases database. If no match is +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. Note that a remote mailbox could - be specified as user@example.com. The next - example shows writing mail to a file, in this case - /dev/null. The last example shows - sending mail to a program, in this case the mail message is - written to the standard input of - /usr/local/bin/procmail through a &unix; + 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, + /usr/local/bin/procmail, through a &unix; pipe. - When this file is updated, you need to run - make in /etc/mail/ + Whenever this file is updated, run + make in /etc/mail/ to update the database. @@ -595,43 +612,44 @@ procmail: "|/usr/local/bin/procmail"This is a list of hostnames &man.sendmail.8; is to accept as the local host name. Place any domains or hosts that - sendmail is to be receiving mail - for. For example, if this mail server was to accept mail for + 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, its - local-host-names might look something - like this: + the host mail.example.com, add +these entries to + local-host-names: example.com mail.example.com - When this file is updated, &man.sendmail.8; needs to be - restarted to read the changes. + Whenever this file is updated, &man.sendmail.8; needs to be + restarted so that it will read the changes. <filename>/etc/mail/sendmail.cf</filename> - sendmail's master configuration - file, sendmail.cf controls the overall - behavior of sendmail, including - everything from rewriting e-mail addresses to printing rejection - messages to remote mail servers. Naturally, with such a diverse - role, this configuration file is quite complex and its details - are a bit out of the scope of this section. Fortunately, this + 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. - The master sendmail configuration + The master Sendmail configuration file can be built from &man.m4.1; macros that define the - features and behavior of sendmail. - Please see + features and behavior of Sendmail. + Refer to /usr/src/contrib/sendmail/cf/README for some of the details. - When changes to this file are made, - sendmail needs to be restarted for + Whenever changes to this file are made, + Sendmail needs to be restarted for the changes to take effect. @@ -641,7 +659,7 @@ mail.example.com The virtusertable maps mail addresses for virtual domains and mailboxes to real mailboxes. These mailboxes can be local, remote, aliases defined in - /etc/mail/aliases or files. + /etc/mail/aliases, or files. Example Virtual Domain Mail Map @@ -651,19 +669,19 @@ postmaster@example.com postmast @example.com joe - In the above example, we have a mapping for a domain + The above example contains a mapping for the domain example.com. This file - is processed in a first match order down the file. The first + is processed in a first match order. The first item maps root@example.com to the local mailbox - root. The next entry maps + root. The second entry maps postmaster@example.com to the mailbox 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. This will - be mapped to the local mailbox + example.com to the local +mailbox joe. @@ -682,137 +700,134 @@ postmaster@example.com postmast Gregory Neil Shapiro - Information taken from e-mails written + Information taken from emails written by - Changing Your Mail Transfer Agent + Changing the Mail Transfer Agent email change mta - As already mentioned, FreeBSD comes with - sendmail already installed as your - MTA (Mail Transfer Agent). Therefore by default it is - in charge of your outgoing and incoming mail. - - However, for a variety of reasons, some system - administrators want to change their system's MTA. These - reasons range from merely wanting to try out another MTA to + &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 - mailer. Fortunately, whatever the reason, FreeBSD makes it + MTA. Whatever the reason, +&os; makes it easy to make the change. - Install a New MTA + Install a New <acronym>MTA</acronym> - You have a wide choice of MTAs available. A good - starting point is the - FreeBSD Ports Collection where - you will be able to find many. Of course you are free to use - any MTA you want from any location, as long as you can make - it run under FreeBSD. - - Start by installing your new MTA. Once it is installed - it gives you a chance to decide if it really fulfills your - needs, and also gives you the opportunity to configure your - new software before getting it to take over from - sendmail. When doing this, you - should be sure that installing the new software will not - attempt to overwrite system binaries such as - /usr/bin/sendmail. Otherwise, your new - mail software has essentially been put into service before - you have configured it. - - Please refer to your chosen MTA's documentation for - information on how to configure the software you have - chosen. + A wide choice of MTAs is available +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 + before replacing Sendmail. + + Refer to the new chosen MTA's +documentation for + information on how to configure the software. - Disable <application>sendmail</application> + Disable <application>Sendmail</application> - If you disable sendmail's - outgoing mail service, it is important that you replace it - with an alternative mail delivery system. If - you choose not to, system functions such as + 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 e-mail as they would normally expect to. Many parts of - your system may expect to have a functional - sendmail-compatible system. If + by email. Many parts of + the system expect a functional + MTA. If applications continue to use - sendmail's binaries to try to - send e-mail after you have disabled them, mail could go - into an inactive sendmail queue, + 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 - sendmail, including the outgoing - mail service, you must use + Sendmail, including the outgoing + mail service, add or edit the following lines in + /etc/rc.conf: sendmail_enable="NO" sendmail_submit_enable="NO" sendmail_outbound_enable="NO" sendmail_msp_queue_enable="NO" - in /etc/rc.conf. - - If you only want to disable - sendmail's incoming mail service, - you should set + To only disable + Sendmail's incoming mail service, + set sendmail_enable="NO" in /etc/rc.conf. More information - on sendmail's startup options - is available from the &man.rc.sendmail.8; manual - page. + on Sendmail's startup options + is available in &man.rc.sendmail.8;. - Running Your New MTA on Boot + Running the New <acronym>MTA</acronym> on Boot - The new MTA can be started during boot by adding a - configuration line to /etc/rc.conf - like the following example for postfix: + The new MTA can be started during +boot by adding a + configuration line to /etc/rc.conf. + This example enables the + Postfix MTA: &prompt.root; echo 'postfix_enable=YES' >> /etc/rc.conf - The MTA will now be automatically started during + The specified MTA will now be +automatically started during boot. - Replacing <application>sendmail</application> as + <title>Replacing <application>Sendmail</application> as the System's Default Mailer - The program sendmail is so + Sendmail is so ubiquitous as standard software on &unix; systems that some - software just assumes it is already installed and configured. - For this reason, many alternative MTA's provide their own + 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; - this facilitates using them as drop-in - replacements for sendmail. - - Therefore, if you are using an alternative mailer, - you will need to make sure that software trying to execute - standard sendmail binaries such as - /usr/bin/sendmail actually executes - your chosen mailer instead. Fortunately, FreeBSD provides - a system called &man.mailwrapper.8; that does this job for - you. - - When sendmail is operating - as installed, you will find something like the following - in /etc/mail/mailer.conf: + Sendmail command-line interface 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 + /usr/bin/sendmail, actually execute + 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: sendmail /usr/libexec/sendmail/sendmail send-mail /usr/libexec/sendmail/sendmail @@ -821,21 +836,19 @@ newaliases /usr/libexec/sendmail/sendmai hoststat /usr/libexec/sendmail/sendmail purgestat /usr/libexec/sendmail/sendmail *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Tue Apr 16 11:10:11 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 75459A11; Tue, 16 Apr 2013 11:10:11 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-ea0-x22c.google.com (mail-ea0-x22c.google.com [IPv6:2a00:1450:4013:c01::22c]) by mx1.freebsd.org (Postfix) with ESMTP id B972022D; Tue, 16 Apr 2013 11:10:10 +0000 (UTC) Received: by mail-ea0-f172.google.com with SMTP id z7so177584eaf.31 for ; Tue, 16 Apr 2013 04:10:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type; bh=DQnXYSKk/A4UcoLTYxAxNAbhNBvCHKdg9efnduVpg+4=; b=tF4u7rZP+1g87AtbdQEYRJzjPlYzUX6U4jzh//Qh3U8khthU/gykJjHB22+mS7WLQW 6CPk+fO+zDgh7UamCsUhQqIqivDTx2Nhr3sa7I1BwEmpBnsVcF3oawADHRR5kEar2/rC IvTMqq1mrkxC8bL2mG61UzvhkraCVQctiPCnm5BnxZOsQ35M3rURQrsCVdbGPXKKfe4g UlCPRUqUBz9n0KMDiMgdjUQZMQEeXtqD4Y7ZAfqK5wQP/SMOMjKQbKTgw9f7LIf7Eg2B XmTgfC/eV00viW2EiXgyQTs1/0vdQMfs7n9Kbm/AtaeY3xFiuAsiG/2gP0ma7r1MoQDo MWLw== X-Received: by 10.14.39.5 with SMTP id c5mr5324013eeb.27.1366110609950; Tue, 16 Apr 2013 04:10:09 -0700 (PDT) Received: from ?IPv6:2001:980:d7ed:1:b9d6:a228:737:db6a? ([2001:980:d7ed:1:b9d6:a228:737:db6a]) by mx.google.com with ESMTPS id bj2sm2288307eeb.1.2013.04.16.04.10.07 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 16 Apr 2013 04:10:08 -0700 (PDT) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <516D318E.1090807@freebsd.org> Date: Tue, 16 Apr 2013 13:10:06 +0200 From: =?UTF-8?B?UmVuw6kgTGFkYW4=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130403 Thunderbird/17.0.5 MIME-Version: 1.0 To: Dru Lavigne Subject: Re: svn commit: r41433 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail References: <201304151503.r3FF3m3X060116@svn.freebsd.org> In-Reply-To: <201304151503.r3FF3m3X060116@svn.freebsd.org> X-Enigmail-Version: 1.5.1 Content-Type: multipart/mixed; boundary="------------090606050808030309080401" Cc: svn-doc-projects@freebsd.org, doc-committers@freebsd.org 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: Tue, 16 Apr 2013 11:10:11 -0000 This is a multi-part message in MIME format. --------------090606050808030309080401 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit On 15-04-2013 17:03, Dru Lavigne wrote: > Author: dru > Date: Mon Apr 15 15:03:47 2013 > New Revision: 41433 > URL: http://svnweb.freebsd.org/changeset/doc/41433 > > Log: > Initial patch which fixes the following. Subsequent patches will follow. > > - fixes &os;, e-mail, and directory tags > - fixes acronyms > - reworded to remove you, please, simply > - inetd reference removed > - modernized the host output > - grammo fixes > - remove non-existing ports (devel) > - remove UUCP section > > Reviewed by: gjb (mentor) > This breaks my local build (no local differences): /usr/local/bin/jade:/usr/home/rene/freebsd/doc/projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml:339:13:E: document type does not allow element "para" here; missing one of "footnote", "itemizedlist", "orderedlist", "variablelist", "caution", "important", "note", "tip", "warning", "blockquote", "informalexample" start-tag /usr/local/bin/jade:/usr/home/rene/freebsd/doc/projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml:341:17:E: end tag for "para" omitted, but OMITTAG NO was specified /usr/local/bin/jade:/usr/home/rene/freebsd/doc/projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml:339:2: start tag was here *** [index.html] Error code 1 The attached patch fixes it. > Modified: > projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml > Regards, RenĂ© --------------090606050808030309080401 Content-Type: text/plain; charset=UTF-8; name="isbn-handbook-mail.diff" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="isbn-handbook-mail.diff" SW5kZXg6IGVuX1VTLklTTzg4NTktMS9ib29rcy9oYW5kYm9vay9tYWlsL2NoYXB0ZXIueG1s Cj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT0KLS0tIGVuX1VTLklTTzg4NTktMS9ib29rcy9oYW5kYm9vay9tYWls L2NoYXB0ZXIueG1sCShyZXZpc2lvbiA0MTQzOSkKKysrIGVuX1VTLklTTzg4NTktMS9ib29r cy9oYW5kYm9vay9tYWlsL2NoYXB0ZXIueG1sCSh3b3JraW5nIGNvcHkpCkBAIC0zMzYsNyAr MzM2LDcgQEAKIAkgICAgICA8L2xpc3RpdGVtPgogCiAJICAgICAgPGxpc3RpdGVtPgotCQk8 cGFyYT48cGFyYT48ZmlsZW5hbWUKKwkJPHBhcmE+PGZpbGVuYW1lCiAJCSAgICByb2xlPSJw YWNrYWdlIj5tYWlsL3RlYXBvcDwvZmlsZW5hbWU+PC9wYXJhPgogCSAgICAgIDwvbGlzdGl0 ZW0+CiAK --------------090606050808030309080401-- From owner-svn-doc-projects@FreeBSD.ORG Tue Apr 16 13:38:17 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 57E9C366; Tue, 16 Apr 2013 13:38:17 +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 4A250B0A; Tue, 16 Apr 2013 13:38:17 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3GDcGh3061907; Tue, 16 Apr 2013 13:38:16 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3GDcGnJ061906; Tue, 16 Apr 2013 13:38:16 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304161338.r3GDcGnJ061906@svn.freebsd.org> From: Dru Lavigne Date: Tue, 16 Apr 2013 13:38:16 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41440 - 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: Tue, 16 Apr 2013 13:38:17 -0000 Author: dru Date: Tue Apr 16 13:38:16 2013 New Revision: 41440 URL: http://svnweb.freebsd.org/changeset/doc/41440 Log: Fix broken build Submitted by: rene Approved by: bcr (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 Tue Apr 16 09:28:25 2013 (r41439) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Tue Apr 16 13:38:16 2013 (r41440) @@ -336,7 +336,7 @@ both POP and - mail/teapop From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 17 14:56:26 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3FCA0F7C; Wed, 17 Apr 2013 14:56:26 +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 18EF4E0D; Wed, 17 Apr 2013 14:56:26 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3HEuPYU038637; Wed, 17 Apr 2013 14:56:25 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3HEuPHv038636; Wed, 17 Apr 2013 14:56:25 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304171456.r3HEuPHv038636@svn.freebsd.org> From: Dru Lavigne Date: Wed, 17 Apr 2013 14:56:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41446 - 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 14:56:26 -0000 Author: dru Date: Wed Apr 17 14:56:25 2013 New Revision: 41446 URL: http://svnweb.freebsd.org/changeset/doc/41446 Log: Revert xref changes so that section numbers show in print version. Pre-existing link tags still need to be fixed. Next patch will fix white space. Approved by: gjb (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 Tue Apr 16 23:10:07 2013 (r41445) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Wed Apr 17 14:56:25 2013 (r41446) @@ -108,20 +108,20 @@ - 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 (). @@ -376,10 +376,9 @@ both POP and clear-text. To secure the transmission of information across these protocols, consider - tunneling sessions over -&man.ssh.1; or using SSL.. +tunneling sessions over +&man.ssh.1; () or using +SSL ().. @@ -1389,9 +1388,10 @@ outgoing mail relay server or SMTP server). - Make sure to disable - Sendmail, including the - outgoing mail service. + Make sure to disable + Sendmail, including the + outgoing mail service. See +< for details. mail/ssmtp has some other options available. Refer to the examples From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 17 15:21:38 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4E587284; Wed, 17 Apr 2013 15:21:38 +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 41713F0D; Wed, 17 Apr 2013 15:21:38 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3HFLcL0047650; Wed, 17 Apr 2013 15:21:38 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3HFLcGt047649; Wed, 17 Apr 2013 15:21:38 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304171521.r3HFLcGt047649@svn.freebsd.org> From: Dru Lavigne Date: Wed, 17 Apr 2013 15:21:38 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41447 - 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 15:21:38 -0000 Author: dru Date: Wed Apr 17 15:21:37 2013 New Revision: 41447 URL: http://svnweb.freebsd.org/changeset/doc/41447 Log: Fix stray < Approved by: gjb (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 14:56:25 2013 (r41446) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Wed Apr 17 15:21:37 2013 (r41447) @@ -1391,7 +1391,7 @@ server Make sure to disable Sendmail, including the outgoing mail service. See -< for details. + for details. mail/ssmtp has some other options available. Refer to the examples From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 17 16:42:42 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3149452E; Wed, 17 Apr 2013 16:42:42 +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 23850603; Wed, 17 Apr 2013 16:42:42 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3HGggH2073284; Wed, 17 Apr 2013 16:42:42 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3HGggKN073283; Wed, 17 Apr 2013 16:42:42 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304171642.r3HGggKN073283@svn.freebsd.org> From: Dru Lavigne Date: Wed, 17 Apr 2013 16:42:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41448 - 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 16:42:42 -0000 Author: dru Date: Wed Apr 17 16:42:41 2013 New Revision: 41448 URL: http://svnweb.freebsd.org/changeset/doc/41448 Log: Fix extraneous + Approved by: gjb (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 15:21:37 2013 (r41447) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Wed Apr 17 16:42:41 2013 (r41448) @@ -242,7 +242,7 @@ daemon DNS is responsible for mapping hostnames to IP addresses, as well as for storing information specific to mail delivery, known as Mail eXchanger -+ MX records. The MX + MX records. The MX record specifies which host, or hosts, will receive mail for a particular domain. If there is no MX record @@ -846,7 +846,7 @@ binaries As an example, to run /usr/local/supermailer/bin/sendmail-compat instead of Sendmail, specify the -+ paths to the installed applications in + paths to the installed applications in /etc/mail/mailer.conf: sendmail /usr/local/supermailer/bin/sendmail-compat @@ -1032,7 +1032,7 @@ connect to immediately. A further refinement of the situation can be seen from -+ this example from the &a.isp;: + this example from the &a.isp;: > we provide the secondary MX for a customer. The customer connects to > our services several times a day automatically to get the mails to From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 17 20:17:39 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 70F6E651; Wed, 17 Apr 2013 20:17:39 +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 63D8C32F; Wed, 17 Apr 2013 20:17:39 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3HKHd6a040529; Wed, 17 Apr 2013 20:17:39 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3HKHdbl040528; Wed, 17 Apr 2013 20:17:39 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304172017.r3HKHdbl040528@svn.freebsd.org> From: Dru Lavigne Date: Wed, 17 Apr 2013 20:17:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41449 - 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:17:39 -0000 Author: dru Date: Wed Apr 17 20:17:38 2013 New Revision: 41449 URL: http://svnweb.freebsd.org/changeset/doc/41449 Log: Unbreak build. Submitted by: hrs 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 16:42:41 2013 (r41448) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Wed Apr 17 20:17:38 2013 (r41449) @@ -378,7 +378,7 @@ clear-text. of information across these protocols, consider tunneling sessions over &man.ssh.1; () or using -SSL ().. +SSL (). 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 *** From owner-svn-doc-projects@FreeBSD.ORG Wed Apr 17 20:59:56 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 54DAF53F; Wed, 17 Apr 2013 20:59:56 +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 4721576A; Wed, 17 Apr 2013 20:59:56 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3HKxuR8053241; Wed, 17 Apr 2013 20:59:56 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3HKxuLH053240; Wed, 17 Apr 2013 20:59:56 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304172059.r3HKxuLH053240@svn.freebsd.org> From: Dru Lavigne Date: Wed, 17 Apr 2013 20:59:56 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41451 - 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:59:56 -0000 Author: dru Date: Wed Apr 17 20:59:55 2013 New Revision: 41451 URL: http://svnweb.freebsd.org/changeset/doc/41451 Log: Fix some small errors introduced by initial content patch. 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:20:07 2013 (r41450) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/mail/chapter.xml Wed Apr 17 20:59:55 2013 (r41451) @@ -364,7 +364,7 @@ FreeBSD.org mail is handled by 10 mx1.Fr clear-text. To secure the transmission of information across these protocols, consider tunneling sessions over &man.ssh.1; () or - using SSL ().. + using SSL (). @@ -1207,7 +1207,7 @@ freefall MX 20 who.cdrom.comISP or DNS provider. - he following is an example of virtual email hosting. + The following is an example of virtual email hosting. Consider a customer with the domain customer1.org, where all the mail for customer1.org should be @@ -1305,8 +1305,8 @@ rewriteDomain=example.com hostname=_HOSTNAME_ Use the real email address for root. - Enter the 's outgoing mail relay in place of mail.example.com. Some + Enter the ISP's outgoing mail relay in place + of mail.example.com. Some ISPs call this the outgoing mail server or SMTP server). @@ -1556,7 +1556,7 @@ define(`confAUTH_MECHANISMS', `GSSAPI DI to 13 and watch /var/log/maillog for any errors. - For more information, refer to refer to For more information, refer to SMTP authentication. @@ -1627,7 +1627,7 @@ define(`confAUTH_MECHANISMS', `GSSAPI DI N 3 root@localhost Mon Mar 8 14:05 14/509 "sample" Messages can now be read by typing t - followed by the message number. This example read the first + followed by the message number. This example reads the first email: & t 1 @@ -2003,8 +2003,8 @@ user "john", with password "XXXXX", is " fetchmail can be run in daemon mode by running it with , followed by the interval (in seconds) that fetchmail - should poll servers listed in .fetchmailrc - file. The following example configures + should poll servers listed in .fetchmailrc. + The following example configures fetchmail to poll every 600 seconds: From owner-svn-doc-projects@FreeBSD.ORG Thu Apr 18 20:48:00 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 E07D354C; Thu, 18 Apr 2013 20:48:00 +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 D230A1ED9; Thu, 18 Apr 2013 20:48:00 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r3IKm01J002024; Thu, 18 Apr 2013 20:48:00 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r3IKm0Ql002020; Thu, 18 Apr 2013 20:48:00 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201304182048.r3IKm0Ql002020@svn.freebsd.org> From: Dru Lavigne Date: Thu, 18 Apr 2013 20:48:00 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41456 - in projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook: advanced-networking ppp-and-slip 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: Thu, 18 Apr 2013 20:48:00 -0000 Author: dru Date: Thu Apr 18 20:47:59 2013 New Revision: 41456 URL: http://svnweb.freebsd.org/changeset/doc/41456 Log: Remove slip, pppd, and 7.x from PPP chapter. This chapter needs to be renamed. Remove reference to pppd in Advanced Networking chapter. Approved by: hrs (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Thu Apr 18 13:58:37 2013 (r41455) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Thu Apr 18 20:47:59 2013 (r41456) @@ -4815,10 +4815,9 @@ Received 264951 bytes in 0.1 secondsA TA will operate basically the same as a modem except connection and throughput speeds will be much faster than your - old modem. You will need to configure - PPP exactly the same as for a modem - setup. Make sure you set your serial speed as high as - possible. + old modem. You will need to configure PPP exactly the same as + for a modem setup. Make sure you set your serial speed as + high as possible. PPP The main advantage of using a TA to connect to an Internet @@ -4835,10 +4834,6 @@ Received 264951 bytes in 0.1 seconds - If you want maximum stability, use the kernel - PPP option, not the - userland PPP. - The following TA's are known to work with FreeBSD: Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Thu Apr 18 13:58:37 2013 (r41455) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml Thu Apr 18 20:47:59 2013 (r41456) @@ -32,7 +32,7 @@ FreeBSD has a number of ways to link one computer to another. To establish a network or Internet connection through a dial-up modem, or to allow others to do so through you, - requires the use of PPP or SLIP. This chapter describes setting + requires the use of PPP. This chapter describes setting up these modem-based communication services in detail. After reading this chapter, you will know: @@ -42,9 +42,6 @@ How to set up user PPP. - How to set up kernel PPP (&os; 7.X only). - - How to set up PPPoE (PPP over Ethernet). @@ -52,10 +49,6 @@ How to set up PPPoA (PPP over ATM). - - How to configure and set up a SLIP client and - server (&os; 7.X only). - @@ -79,29 +72,9 @@ Understand the basics and purpose of a dialup connection - and PPP and/or SLIP. + and PPP. - - You may be wondering what the main difference is between - user PPP and kernel PPP. The answer is simple: user PPP - processes the inbound and outbound data in userland rather than - in the kernel. This is expensive in terms of copying the data - between the kernel and userland, but allows a far more - feature-rich PPP implementation. User PPP uses the - tun device to communicate with the - outside world whereas kernel PPP uses the - ppp device. - - - Throughout in this chapter, user PPP will simply be - referred to as ppp unless a - distinction needs to be made between it and any other PPP - software such as pppd - (&os; 7.X only). Unless otherwise stated, all of the - commands explained in this chapter should be executed as - root. - @@ -264,11 +237,9 @@ configuration - Both ppp and pppd - (the kernel level implementation of PPP, &os; 7.X only) - use the configuration files located in the /etc/ppp directory. - Examples for user ppp can be found in ppp uses the configuration files + located in /etc/ppp. + Examples can be found in /usr/share/examples/ppp/. Configuring ppp requires that you @@ -1352,505 +1323,6 @@ ifconfig_tun0= - - - - - Gennady B. - Sorokopud - Parts originally contributed by - - - Robert - Huff - - - - - Using Kernel PPP - - - This section applies and is valid only for - &os; 7.X. - - - - Setting Up Kernel PPP - - - PPP - kernel PPP - - - Before you start setting up PPP on your machine, make sure - that pppd is located in - /usr/sbin and the - directory /etc/ppp - exists. - - pppd can work in two modes: - - - - As a client — you want to connect - your machine to the outside world via a PPP serial - connection or modem line. - - - - - PPP - server - - - As a server — your machine is - located on the network, and is used to connect other - computers using PPP. - - - - In both cases you will need to set up an options file - (/etc/ppp/options or - ~/.ppprc if you have more than one user - on your machine that uses PPP). - - You will also need some modem/serial software (preferably - comms/kermit), so you - can dial and establish a connection with the remote - host. - - - - - - - Trev - Roydhouse - Based on information provided by - - - - - - Using <command>pppd</command> as a Client - - - PPP - client - - - - Cisco - - - The following /etc/ppp/options might - be used to connect to a Cisco terminal server PPP line. - - crtscts # enable hardware flow control -modem # modem control line -noipdefault # remote PPP server must supply your IP address - # if the remote host does not send your IP during IPCP - # negotiation, remove this option -passive # wait for LCP packets -domain ppp.foo.com # put your domain name here - -:remote_ip # put the IP of remote PPP host here - # it will be used to route packets via PPP link - # if you didn't specified the noipdefault option - # change this line to local_ip:remote_ip - -defaultroute # put this if you want that PPP server will be your - # default router - - To connect: - - Kermit - modem - - - Dial to the remote host using - Kermit (or some other modem - program), and enter your user name and password (or - whatever is needed to enable PPP on the remote - host). - - - - Exit Kermit (without - hanging up the line). - - - - Enter the following: - - &prompt.root; /usr/sbin/pppd /dev/tty01 19200 - - Be sure to use the appropriate speed and device - name. - - - - Now your computer is connected with PPP. If the - connection fails, you can add the - option to the /etc/ppp/options file, - and check console messages to track the problem. - - Following /etc/ppp/pppup script will - make all 3 stages automatic: - - #!/bin/sh -pgrep -l pppd -pid=`pgrep pppd` -if [ "X${pid}" != "X" ] ; then - echo 'killing pppd, PID=' ${pid} - kill ${pid} -fi -pgrep -l kermit -pid=`pgrep kermit` -if [ "X${pid}" != "X" ] ; then - echo 'killing kermit, PID=' ${pid} - kill -9 ${pid} -fi - -ifconfig ppp0 down -ifconfig ppp0 delete - -kermit -y /etc/ppp/kermit.dial -pppd /dev/tty01 19200 - - - Kermit - - - /etc/ppp/kermit.dial is a - Kermit script that dials and makes - all necessary authorization on the remote host (an example - of such a script is attached to the end of this - document). - - Use the following /etc/ppp/pppdown - script to disconnect the PPP line: - - #!/bin/sh -pid=`pgrep pppd` -if [ X${pid} != "X" ] ; then - echo 'killing pppd, PID=' ${pid} - kill -TERM ${pid} -fi - -pgrep -l kermit -pid=`pgrep kermit` -if [ "X${pid}" != "X" ] ; then - echo 'killing kermit, PID=' ${pid} - kill -9 ${pid} -fi - -/sbin/ifconfig ppp0 down -/sbin/ifconfig ppp0 delete -kermit -y /etc/ppp/kermit.hup -/etc/ppp/ppptest - - Check to see if pppd is still running - by executing /usr/etc/ppp/ppptest, which - should look like this: - - #!/bin/sh -pid=`pgrep pppd` -if [ X${pid} != "X" ] ; then - echo 'pppd running: PID=' ${pid-NONE} -else - echo 'No pppd running.' -fi -set -x -netstat -n -I ppp0 -ifconfig ppp0 - - To hang up the modem, execute - /etc/ppp/kermit.hup, which should - contain: - - set line /dev/tty01 ; put your modem device here -set speed 19200 -set file type binary -set file names literal -set win 8 -set rec pack 1024 -set send pack 1024 -set block 3 -set term bytesize 8 -set command bytesize 8 -set flow none - -pau 1 -out +++ -inp 5 OK -out ATH0\13 -echo \13 -exit - - Here is an alternate method using chat - instead of kermit: - - The following two files are sufficient to accomplish a - pppd connection. - - /etc/ppp/options: - - /dev/cuad1 115200 - -crtscts # enable hardware flow control -modem # modem control line -connect "/usr/bin/chat -f /etc/ppp/login.chat.script" -noipdefault # remote PPP serve must supply your IP address - # if the remote host doesn't send your IP during - # IPCP negotiation, remove this option -passive # wait for LCP packets -domain your.domain # put your domain name here - -: # put the IP of remote PPP host here - # it will be used to route packets via PPP link - # if you didn't specified the noipdefault option - # change this line to local_ip:remote_ip - -defaultroute # put this if you want that PPP server will be - # your default router - - /etc/ppp/login.chat.script: - - - The following should go on a single line. - - - ABORT BUSY ABORT 'NO CARRIER' "" AT OK ATDTphone.number - CONNECT "" TIMEOUT 10 ogin:-\\r-ogin: login-id - TIMEOUT 5 sword: password - - Once these are installed and modified correctly, all - you need to do is run pppd, like so: - - &prompt.root; pppd - - - - Using <command>pppd</command> as a Server - - /etc/ppp/options should contain - something similar to the following: - - crtscts # Hardware flow control -netmask 255.255.255.0 # netmask (not required) -192.114.208.20:192.114.208.165 # IP's of local and remote hosts - # local ip must be different from one - # you assigned to the Ethernet (or other) - # interface on your machine. - # remote IP is IP address that will be - # assigned to the remote machine -domain ppp.foo.com # your domain -passive # wait for LCP -modem # modem line - - The following /etc/ppp/pppserv script - will tell pppd to behave as a - server: - - #!/bin/sh -pgrep -l pppd -pid=`pgrep pppd` -if [ "X${pid}" != "X" ] ; then - echo 'killing pppd, PID=' ${pid} - kill ${pid} -fi -pgrep -l kermit -pid=`pgrep kermit` -if [ "X${pid}" != "X" ] ; then - echo 'killing kermit, PID=' ${pid} - kill -9 ${pid} -fi - -# reset ppp interface -ifconfig ppp0 down -ifconfig ppp0 delete - -# enable autoanswer mode -kermit -y /etc/ppp/kermit.ans - -# run ppp -pppd /dev/tty01 19200 - - Use this /etc/ppp/pppservdown script - to stop the server: - - #!/bin/sh -pgrep -l pppd -pid=`pgrep pppd` -if [ "X${pid}" != "X" ] ; then - echo 'killing pppd, PID=' ${pid} - kill ${pid} -fi -pgrep -l kermit -pid=`pgrep kermit` -if [ "X${pid}" != "X" ] ; then - echo 'killing kermit, PID=' ${pid} - kill -9 ${pid} -fi -ifconfig ppp0 down -ifconfig ppp0 delete - -kermit -y /etc/ppp/kermit.noans - - The following Kermit script - (/etc/ppp/kermit.ans) will enable/disable - autoanswer mode on your modem. It should look like - this: - - set line /dev/tty01 -set speed 19200 -set file type binary -set file names literal -set win 8 -set rec pack 1024 -set send pack 1024 -set block 3 -set term bytesize 8 -set command bytesize 8 -set flow none - -pau 1 -out +++ -inp 5 OK -out ATH0\13 -inp 5 OK -echo \13 -out ATS0=1\13 ; change this to out ATS0=0\13 if you want to disable - ; autoanswer mode -inp 5 OK -echo \13 -exit - - A script named /etc/ppp/kermit.dial - is used for dialing and authenticating on the remote host. - You will need to customize it for your needs. Put your login - and password in this script; you will also need to change the - input statement depending on responses from your modem and - remote host. - - ; -; put the com line attached to the modem here: -; -set line /dev/tty01 -; -; put the modem speed here: -; -set speed 19200 -set file type binary ; full 8 bit file xfer -set file names literal -set win 8 -set rec pack 1024 -set send pack 1024 -set block 3 -set term bytesize 8 -set command bytesize 8 -set flow none -set modem hayes -set dial hangup off -set carrier auto ; Then SET CARRIER if necessary, -set dial display on ; Then SET DIAL if necessary, -set input echo on -set input timeout proceed -set input case ignore -def \%x 0 ; login prompt counter -goto slhup - -:slcmd ; put the modem in command mode -echo Put the modem in command mode. -clear ; Clear unread characters from input buffer -pause 1 -output +++ ; hayes escape sequence -input 1 OK\13\10 ; wait for OK -if success goto slhup -output \13 -pause 1 -output at\13 -input 1 OK\13\10 -if fail goto slcmd ; if modem doesn't answer OK, try again - -:slhup ; hang up the phone -clear ; Clear unread characters from input buffer -pause 1 -echo Hanging up the phone. -output ath0\13 ; hayes command for on hook -input 2 OK\13\10 -if fail goto slcmd ; if no OK answer, put modem in command mode - -:sldial ; dial the number -pause 1 -echo Dialing. -output atdt9,550311\13\10 ; put phone number here -assign \%x 0 ; zero the time counter - -:look -clear ; Clear unread characters from input buffer -increment \%x ; Count the seconds -input 1 {CONNECT } -if success goto sllogin -reinput 1 {NO CARRIER\13\10} -if success goto sldial -reinput 1 {NO DIALTONE\13\10} -if success goto slnodial -reinput 1 {\255} -if success goto slhup -reinput 1 {\127} -if success goto slhup -if < \%x 60 goto look -else goto slhup - -:sllogin ; login -assign \%x 0 ; zero the time counter -pause 1 -echo Looking for login prompt. - -:slloop -increment \%x ; Count the seconds -clear ; Clear unread characters from input buffer -output \13 -; -; put your expected login prompt here: -; -input 1 {Username: } -if success goto sluid -reinput 1 {\255} -if success goto slhup -reinput 1 {\127} -if success goto slhup -if < \%x 10 goto slloop ; try 10 times to get a login prompt -else goto slhup ; hang up and start again if 10 failures - -:sluid -; -; put your userid here: -; -output ppp-login\13 -input 1 {Password: } -; -; put your password here: -; -output ppp-password\13 -input 1 {Entering SLIP mode.} -echo -quit - -:slnodial -echo \7No dialtone. Check the telephone line!\7 -exit 1 - -; local variables: -; mode: csh -; comment-start: "; " -; comment-start-skip: "; " -; end: - - - @@ -2559,760 +2031,4 @@ tun0: flags=8051<UP,POINTOPOINT,RUNNI /var/log/ppp.log for clues. - - - - - - Satoshi - Asami - Originally contributed by - - - - - Guy - Helmer - With input from - - - Piero - Serini - - - - - Using SLIP - - SLIP - - - This section applies and is valid only for - &os; 7.X. - - - - Setting Up a SLIP Client - - - SLIP - client - - - The following is one way to set up a FreeBSD machine for - SLIP on a static host network. For dynamic hostname - assignments (your address changes each time you dial up), you - probably need to have a more complex setup. - - First, determine which serial port your modem is connected - to. Many people set up a symbolic link, such as - /dev/modem, to point - to the real device name, /dev/cuadN. - This allows you to abstract the actual device name should you - ever need to move the modem to a different port. It can - become quite cumbersome when you need to fix a bunch of files - in /etc and - .kermrc files all over the system! - - - /dev/cuad0 - is COM1, /dev/cuad1 is - COM2, etc. - - - Make sure you have the following in your kernel - configuration file: - - device sl - - It is included in the GENERIC kernel, - so this should not be a problem unless you have deleted - it. - - - Things You Have to Do Only Once - - - - Add your home machine, the gateway and nameservers - to your /etc/hosts file. Ours - looks like this: - - 127.0.0.1 localhost loghost -136.152.64.181 water.CS.Example.EDU water.CS water -136.152.64.1 inr-3.CS.Example.EDU inr-3 slip-gateway -128.32.136.9 ns1.Example.EDU ns1 -128.32.136.12 ns2.Example.EDU ns2 - - - - Make sure you have files before - dns in the hosts: - section of your /etc/nsswitch.conf - file. Without these parameters funny things may - happen. - - - - Edit the /etc/rc.conf - file. - - - - Set your hostname by editing the line that - says: - - hostname="myname.my.domain" - - Your machine's full Internet hostname should be - placed here. - - - - default - route - - Designate the default router by changing the - line: - - defaultrouter="NO" - - to: - - defaultrouter="slip-gateway" - - - - - - Make a file /etc/resolv.conf - which contains: - - domain CS.Example.EDU -nameserver 128.32.136.9 -nameserver 128.32.136.12 - - nameserver - domain name - As you can see, these set up the nameserver hosts. - Of course, the actual domain names and addresses depend - on your environment. - - - - Set the password for root and - toor (and any other - accounts that do not have a password). - - - - Reboot your machine and make sure it comes up with - the correct hostname. - - - - - - Making a SLIP Connection - - - SLIP - connecting with - - - - - Dial up, type slip at the prompt, - enter your machine name and password. What is required - to be entered depends on your environment. If you use - Kermit, you can try a script - like this: - - # kermit setup -set modem hayes -set line /dev/modem -set speed 115200 -set parity none -set flow rts/cts -set terminal bytesize 8 -set file type binary -# The next macro will dial up and login -define slip dial 643-9600, input 10 =>, if failure stop, - -output slip\x0d, input 10 Username:, if failure stop, - -output silvia\x0d, input 10 Password:, if failure stop, - -output ***\x0d, echo \x0aCONNECTED\x0a - - Of course, you have to change the username and - password to fit yours. After doing so, you can just - type slip from the - Kermit prompt to - connect. - - - Leaving your password in plain text anywhere in - the filesystem is generally a bad - idea. Do it at your own risk. - - - - - Leave the Kermit there - (you can suspend it by - - Ctrl - z - ) and as root, - type: - - &prompt.root; slattach -h -c -s 115200 /dev/modem - - If you are able to ping hosts - on the other side of the router, you are connected! - If it does not work, you might want to try - instead of as - an argument to slattach. - - - - - - How to Shutdown the Connection - - Do the following: - - &prompt.root; kill -INT `cat /var/run/slattach.modem.pid` - - to kill slattach. Keep in mind you - must be root to do the above. Then - go back to kermit (by running - fg if you suspended it) and exit from - it (q). - - The &man.slattach.8; manual page says you have to use - ifconfig sl0 down to mark the interface - down, but this does not seem to make any difference. - (ifconfig sl0 reports the same - thing.) - - Some times, your modem might refuse to drop the carrier. - In that case, simply start kermit and - quit it again. It usually goes out on the second - try. - - - - Troubleshooting - - If it does not work, feel free to ask on &a.net.name; - mailing list. The things that people tripped over so - far: - - - - Not using or - in slattach (This should not be - fatal, but some users have reported that this solves - their problems.) - - - - Using instead of - (might be hard to see the - difference on some fonts). - - - - Try ifconfig sl0 to see your - interface status. For example, you might get: - - &prompt.root; ifconfig sl0 -sl0: flags=10<POINTOPOINT> - inet 136.152.64.181 --> 136.152.64.1 netmask ffffff00 - - - - If you get no route to host - messages from &man.ping.8;, there may be a problem - with your routing table. You can use the - netstat -r command to display the - current routes : - - &prompt.root; netstat -r -Routing tables -Destination Gateway Flags Refs Use IfaceMTU Rtt Netmasks: - -(root node) -(root node) - -Route Tree for Protocol Family inet: -(root node) => -default inr-3.Example.EDU UG 8 224515 sl0 - - -localhost.Exampl localhost.Example. UH 5 42127 lo0 - 0.438 -inr-3.Example.ED water.CS.Example.E UH 1 0 sl0 - - -water.CS.Example localhost.Example. UGH 34 47641234 lo0 - 0.438 -(root node) - - The preceding examples are from a relatively busy - system. The numbers on your system will vary depending - on network activity. - - - - - - - - Setting Up a SLIP Server - - - SLIP - server - - - This document provides suggestions for setting up SLIP - Server services on a FreeBSD system, which typically means - configuring your system to automatically start up connections - upon login for remote SLIP clients. - - - - - Prerequisites - - TCP/IP networking - This section is very technical in nature, so background - knowledge is required. It is assumed that you are familiar - with the TCP/IP network protocol, and in particular, network - and node addressing, network address masks, subnetting, - routing, and routing protocols, such as RIP. Configuring - SLIP services on a dial-up server requires a knowledge of - these concepts, and if you are not familiar with them, - please read a copy of either Craig Hunt's TCP/IP - Network Administration published by O'Reilly - & Associates, Inc. (ISBN Number 0-937175-82-X), or - Douglas Comer's books on the TCP/IP protocol. - - modem - It is further assumed that you have already set up your - modem(s) and configured the appropriate system files to - allow logins through your modems. If you have not prepared - your system for this yet, please see for details on dialup services - configuration. You may also want to check the manual pages - or &man.sio.4; for information on the serial port device - driver and &man.ttys.5;, &man.gettytab.5;, &man.getty.8;, - & &man.init.8; for information relevant to configuring - the system to accept logins on modems, and perhaps - &man.stty.1; for information on setting serial port - parameters (such as clocal for - directly-connected serial interfaces). - - - - Quick Overview - - In its typical configuration, using FreeBSD as a SLIP - server works as follows: a SLIP user dials up your FreeBSD - SLIP Server system and logs in with a special SLIP login - ID that uses /usr/sbin/sliplogin as - the special user's shell. The sliplogin - program browses the file - /etc/sliphome/slip.hosts to find a - matching line for the special user, and if it finds a match, - connects the serial line to an available SLIP interface and - then runs the shell script - /etc/sliphome/slip.login to configure - the SLIP interface. - - - An Example of a SLIP Server Login - - For example, if a SLIP user ID were - Shelmerg, - Shelmerg's entry in - /etc/master.passwd would look - something like this: - - Shelmerg:password:1964:89::0:0:Guy Helmer - SLIP:/usr/users/Shelmerg:/usr/sbin/sliplogin - - When Shelmerg logs in, *** DIFF OUTPUT TRUNCATED AT 1000 LINES ***