From owner-freebsd-doc Tue May 21 19:49:11 2002 Delivered-To: freebsd-doc@freebsd.org Received: from mail.reppep.com (www.reppep.com [64.81.19.108]) by hub.freebsd.org (Postfix) with ESMTP id 7A3E137B409; Tue, 21 May 2002 19:48:56 -0700 (PDT) Received: from [64.81.19.109] (g4.reppep.com [64.81.19.109]) by mail.reppep.com (Postfix) with ESMTP id A74BD17C06; Tue, 21 May 2002 21:50:44 -0400 (EDT) Mime-Version: 1.0 X-Sender: pepper@mail.reppep.com Message-Id: In-Reply-To: <200205210150.g4L1o3R30761@freefall.freebsd.org> References: <200205210150.g4L1o3R30761@freefall.freebsd.org> Date: Tue, 21 May 2002 22:45:47 -0400 To: Giorgos Keramidas From: Chris Pepper Subject: Re: docs/38318: Many typo, grammar, and minor tag patches. Cc: freebsd-doc@FreeBSD.org Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Giorgios, I've taken your suggestions. Here's a revised patch for doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml. Chris Pepper --- chapter.sgml Tue May 21 22:26:40 2002 +++ chapter.sgml.fixed Tue May 21 22:42:29 2002 @@ -397,7 +397,7 @@ 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 the - domain example.com and the host + domain example.com and the host mail.example.com, its local-host-names might look something like this: @@ -406,7 +406,7 @@ mail.example.com When this file is updated, &man.sendmail.8; needs to be - restarted for it to read the changes. + restarted to read the changes. @@ -416,15 +416,15 @@ sendmail's master configuration file, sendmail.cf controls the overall behavior of sendmail, including everything - from rewriting e-mail addresses to printing reject messages for + 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 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 features - and behavior of sendmail. Please see + file can be built from &man.m4.1; macros that define the features + and behavior of sendmail. Please see /usr/src/contrib/sendmail/cf/README for some of the details. @@ -436,11 +436,11 @@ <filename>/etc/mail/virtusertable</filename> - The virtualusertable maps mail for + The virtusertable maps mail addresses for virtual domains and mailboxes to real mailboxes. These mailboxes can be local, - remote, an alias defined in - /etc/mail/aliases or a file. + remote, aliases defined in + /etc/mail/aliases or files. Example Virtual Domain Mail Map @@ -570,8 +570,8 @@ sendmail-compatible system. If applications continue to use sendmail's binaries to try and send - e-mail after you have disabled it, the mail may transparently - queue forever. + e-mail after you have disabled them, mail could go into an + inactive sendmail queue, and never be delivered. If you only want to disable @@ -599,12 +599,20 @@ Add a script to /usr/local/etc/rc.d/ that ends in .sh and is executable by - root. The script should also accept the - parameters 'start' and 'stop'. So that you could, for example, execute - /usr/local/etc/rc.d/supermailer.sh start - or /usr/local/etc/rc.d/supermailer.sh stop. - The system will call your script using 'start' when the it - boots and using 'stop' when the it shuts down. + root. The script should accept start and + stop parameters. At startup time the + system scripts will execute the command, e.g., + + /usr/local/etc/rc.d/supermailer.sh start + + which you can also use to manually start the server. At + shutdown time, the system scripts will use the + stop option, running the command + + /usr/local/etc/rc.d/supermailer.sh start + + which you can also use to manually stop the server + while the system is running. @@ -613,13 +621,13 @@ (including 4.6-RELEASE and later) With later versions of FreeBSD, you can use the - above method or you can also set + above method or you can set mta_start_script="filename" in /etc/rc.conf, where filename is the name of some - script that you want executed on boot to start your + script that you want executed at boot to start your MTA. @@ -630,11 +638,10 @@ the system's default mailer Sendmail is so ubiquitous - as standard software on Unix systems, that some software - just presumes that it is already installed and configured. - For this reason, many alternative MTA's provide utilities - that implement exactly the same command-line interface - that sendmail provides. + 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 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 @@ -656,17 +663,17 @@ purgestat /usr/libexec/sendmail/sendmail This means that when any of these common commands - are run, such as /usr/bin/sendmail - the program that is actually sitting in that location + (such as sendmail itself) are run, + the system actually invokes a copy of mailwrapper named sendmail, which checks mailer.conf and executes /usr/libexec/sendmail/sendmail instead. This system makes it easy to change what binaries - are actually executed when these default system utilities - are run. + are actually executed when these default sendmail functions + are invoked. Therefore if you wanted /usr/local/supermailer/bin/sendmail-compat - to be run instead of sendmail, you would change + to be run instead of sendmail, you could change /etc/mail/mailer.conf to read: sendmail /usr/local/supermailer/bin/sendmail-compat @@ -681,12 +688,12 @@ Finishing - Once you have everything configured how you want it, you should + Once you have everything configured the way you want it, you should either kill the sendmail processes that you no longer need and start the processes belonging to your new - software. Or you should reboot your machine. Rebooting will also + software, or simply reboot. Rebooting will also give you the opportunity to ensure that you have correctly - configured your machine to start your new MTA on boot. + configured your system to start your new MTA automatically on boot. @@ -801,13 +808,13 @@ Only one host should be specified as the final recipient (add Cw bigco.com in - /etc/mail/sendmail.cf on bigco.com). + /etc/mail/sendmail.cf on bigco.com). - When the senders' sendmail is trying to + When the sending sendmail is trying to deliver the mail it will try to connect to you over the modem link. It will most likely time out because you are not online. sendmail will automatically deliver it to the - secondary MX site, i.e., your Internet provider. The secondary MX + secondary MX site, i.e. your Internet provider. The secondary MX site will try every (sendmail_flags = -bd -q15m in /etc/rc.conf) 15 minutes to connect to @@ -869,7 +876,7 @@ In default FreeBSD installations, - Sendmail is configured to only + sendmail is configured to only send mail from the host it is running on. For example, if a POP3 server is installed, then users will be able to check mail from school, work, or other remote locations @@ -881,22 +888,22 @@ message. There are several ways to get around this. The most - straight forward solution is to put your ISP's address in + straightforward solution is to put your ISP's address in a relay-domains file at /etc/mail/relay-domains. A quick way to do this would be: &prompt.root; echo "your.isp.example.com" > /etc/mail/relay-domains - After creating this file you must restart + After creating or editing this file you must restart sendmail. This works great if you are a server admin and don't wish to send mail locally, or would like to use a point and click client/system on another machine or even another ISP. It is also very useful if you only have one or two email - accounts setup. If there are a large number of addresses + accounts set up. If there are a large number of addresses to add, you can simply open this file in your favorite - text editor and then add the domains one per line: + text editor and then add the domains, one per line: your.isp.example.com other.isp.example.net @@ -904,8 +911,8 @@ www.example.org Now any mail sent through your system, by any host in - this list, providing the user has an account on your - system, will succeed. This is a very nice way to allow + this list (provided the user has an account on your + system), will succeed. This is a very nice way to allow users to send mail from your system remotely without allowing people to send SPAM through your system. @@ -931,7 +938,7 @@ hosts as long as you have set up /etc/resolv.conf or are running your own name server. If you would like to have mail for your host - delivered to that specific host, there are two methods: + delivered to the MTA (e.g., sendmail) on your own FreeBSD host, there are two methods: @@ -950,16 +957,16 @@ SMTP Regardless of which of the above you choose, in order to have - mail delivered directly to your host, you must have a permanent - (static) IP address (no dynamic PPP dial-up). If you are behind a + mail delivered directly to your host, it must have a permanent + static IP address (not a dynamic address, as with most PPP dial-up configurations). If you are behind a firewall, it must pass SMTP traffic on to you. If you want to - receive mail at your host itself, you need to be sure of one of two + receive mail directly at your host, you need to be sure of either of two things: MX record - Make sure that the MX record in your DNS points to your + Make sure that the (lowest-numbered) MX record in your DNS points to your host's IP address. @@ -981,7 +988,8 @@ If that is what you see, mail directly to yourlogin@example.FreeBSD.org should work without - problems. + problems (assuming sendmail is + running correctly on example.FreeBSD.org). If instead you see something like this: @@ -1010,12 +1018,14 @@ freefall MX 20 who.cdrom.com As you can see, freefall had many MX entries. - The lowest MX number is the host that ends up receiving the mail in - the end while the others will queue mail temporarily if - freefall is busy or down. + The lowest MX number is the host that receives mail directly if + available; if it's not accessible for some reason, the others + (sometimes called backup MXes) accept messages + temporarily, and pass it along when a lower-numbered host becomes + available, eventually to the lowest-numbered host. Alternate MX sites should have separate Internet connections - from your own in order to be the most useful. Your ISP or other + from your own in order to be most useful. Your ISP or another friendly site should have no problem providing this service for you. @@ -1023,13 +1033,13 @@ Mail for Your Domain - In order to set up a mailhost (a.k.a., mail + In order to set up a mailhost (a.k.a. mail server) you need to have any mail sent to various workstations - directed to it. Basically, you want to hijack any - mail for your domain (in this case claim any + mail for any hostname in your domain (in this case *.FreeBSD.org) and divert it to your mail - server so your users can check their mail via POP or directly on - the server. + server so your users can receive their mail on + the master mail server. DNS To make life easiest, a user account with the same @@ -1037,7 +1047,7 @@ adduser to do this. The mailhost you will be using must be the designated mail - exchange for each workstation on the network. This is done in + exchanger for each workstation on the network. This is done in your DNS configuration like so: example.FreeBSD.org A 204.216.27.XX ; Workstation @@ -1048,25 +1058,25 @@ host. You cannot do this yourself unless you are running a DNS - server. If you are not, or cannot, run your own DNS server, talk - to your ISP or whoever does your DNS for you. + server. If you are not, or cannot run your own DNS server, talk + to your ISP or whoever provides your DNS. If you are doing virtual email hosting, the following - information will come in handy. For the sake of an example, we + information will come in handy. For this example, we will assume you have a customer with their own domain, in this - case customer1.org and you want + case customer1.org, and you want all the mail for customer1.org - sent to your mailhost, which is named mail.myhost.com. The entry in your DNS should look like this: customer1.org MX 10 mail.myhost.com - You do not need an A record if you only - want to handle email for the domain. + You do not need an A record for customer1.org if you only + want to handle email for that domain. - Be aware that this means pinging Be aware that pinging customer1.org will not work unless an A record exists for it. @@ -1082,7 +1092,7 @@ Add the hosts to your /etc/mail/local-host-names file if you are using the FEATURE(use_cw_file). If you are using - a version of sendmail earlier than 8.10, the file is + a version of sendmail earlier than 8.10, the file is /etc/sendmail.cw. @@ -1090,7 +1100,7 @@ Add a Cwyour.host.com line to your /etc/mail/sendmail.cf or /etc/mail/sendmail.cf if you are using - sendmail 8.10 or higher. + sendmail 8.10 or higher. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message