From e5978b0d32a87848eef3ccb5170eb54a44c0f5ee Mon Sep 17 00:00:00 2001 From: Marc Fonvieille Date: Tue, 8 Oct 2002 18:53:51 +0000 Subject: [PATCH] - Add right role attribute to hostid tags - Add various tags - Avoid capitalization of the name "sendmail" - Some punctuation fixes - s/admin/administrator and don't/do not - use of man entity when needed --- .../books/handbook/mail/chapter.sgml | 40 +++++++++---------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/en_US.ISO8859-1/books/handbook/mail/chapter.sgml b/en_US.ISO8859-1/books/handbook/mail/chapter.sgml index 2918e66903..b3d0fa3460 100644 --- a/en_US.ISO8859-1/books/handbook/mail/chapter.sgml +++ b/en_US.ISO8859-1/books/handbook/mail/chapter.sgml @@ -355,8 +355,8 @@ okay.cyberspammer.com OK rejects mail from a specific host on the Internet, another.source.of.spam. The next entry accepts mail connections from a host - okay.cyberspammer.com, which is more exact than - the cyberspammer.com line above. More specific + 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 IP address that begins with 128.32. These hosts would be able @@ -395,7 +395,7 @@ procmail: "|/usr/local/bin/procmail" 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 + 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 @@ -414,7 +414,7 @@ procmail: "|/usr/local/bin/procmail" 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 - mail.example.com, its + mail.example.com, its local-host-names might look something like this: @@ -467,15 +467,15 @@ postmaster@example.com postmaster@noc.example.net In the above example, we have a mapping for a domain - example.com. This file is processed in a + example.com. This file is processed in a first match order down the file. The first item maps - root@example.com to the local mailbox root. The next entry maps - postmaster@example.com to the mailbox postmaster on the host - noc.example.net. Finally, if nothing from example.com has + root@example.com to the local mailbox root. The next 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 mail box joe. + example.com. + This will be mapped to the local mailbox joe. @@ -653,13 +653,13 @@ postmaster@example.com postmaster@noc.example.net Replacing <application>sendmail</application> as the system's default mailer - Sendmail is so ubiquitous + The program 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 compatible implementations of the sendmail command-line interface; this facilitates using them as - drop-in replacements for sendmail. + drop-in replacements for sendmail. Therefore, if you are using an alternative mailer, you will need to make sure that software trying to execute @@ -820,8 +820,8 @@ to /etc/mail/sendmail.cf. Another way is to get a full-time Internet server to provide secondary MX services for your domain. For example, if your company's domain is - example.com and your Internet service provider has - set example.net up to provide secondary MX services + example.com and your Internet service provider has + set example.net up to provide secondary MX services to your domain: example.com. MX 10 example.com. @@ -834,13 +834,13 @@ to /etc/mail/sendmail.cf. When the sending sendmail is trying to deliver the mail it will try to connect to you (example.com) over the modem link. It will most likely time out because you are not online. - Sendmail will automatically deliver it to the + The program sendmail will automatically deliver it to the secondary MX site, i.e. your Internet provider (example.net). The secondary MX site will then periodically try to connect to your host and deliver the mail to the primary MX host (example.com). You might want to use something like this as a login - script. + script: #!/bin/sh # Put me in /usr/local/bin/pppmyisp @@ -852,7 +852,7 @@ to /etc/mail/sendmail.cf. instead in the script above. This will force all mail in your queue for example.com to be processed immediately. - A further refinement of the situation is as follows. + A further refinement of the situation is as follows: Message stolen from the &a.isp;. @@ -916,7 +916,7 @@ the DNS for customer.com. 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 + you are a server administrator and do not 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 @@ -1063,7 +1063,7 @@ freefall MX 20 who.cdrom.com DNS To make life easiest, a user account with the same username should exist on both machines. Use - adduser to do this. + &man.adduser.8; to do this. The mailhost you will be using must be the designated mail exchanger for each workstation on the network. This is done in @@ -1082,7 +1082,7 @@ freefall MX 20 who.cdrom.com If you are doing virtual email hosting, the following information will come in handy. For this example, we - will assume you have a customer with their own domain, in this + will assume you have a customer with his own domain, in this case customer1.org, and you want all the mail for customer1.org sent to your mailhost,