Linux Network Administrator Manual (14)
2000-07-30 20:46
Publisher: NetBull Readings: 1138 Translation: Zhao Wei GoHigh@shtdu.edu.cn Chapter 14 Configuration and Run SMAIL This chapter will give you a quick start of SMAIL and the functional overview it provides. Although SMAIL behavior is largely compatible with Sendmail, their configuration files are completely different. The main profile is / usr / lib / smail / config. You must edit this file to reflect your specific value of your site. If you are just a UUCP's end site, you rarely need to be changed accordingly. Other files that configure routing and transfer options are of course also possible; these files will also summarize the theory and. By default, SMAIL will process and distribute all inbound messages. If you have a relatively large traffic, you can first collect information into the so-called queue (Queue) and process them only during a certain interval. When the message is processed on the TCP / IP network, SMAIL will run in later mode: when the system boot is started, it is called from rc.inet2, and puts themselves into the background to wait for the SMTP port. (Usually port 25) The TCP connection is entered. This is very useful when you may encounter greater information traffic, because SMAIL will not run immediately for each inbound connection. Another method is to let inetd manage the SMTP port, and whenever this port is connected, it is called SMAIL. SMAIL has many signs to control their own behavior; discuss them in detail here, they don't have much help to you. Fortunately, SMAIL supports some standard operating modes that are turned on, such as RMAIL and SMTPD when you call SMAIL through a specific command name. Typically, these alias itself is a symbolic connection to the SMAIL execution file. We will encounter most of the characteristics when discussing various features of SMAIL. In all environments, you should have two to SMAIL; they are / usr / bin / rmail and / usr / sbin / sendmail. [1] When you write and send a mail message using a user agent (such as ELM), the mail message will be delivered to Rmail to deliver, and the recipient list is given on the command line. There is also the same case for messages received through UUCP. However, some versions of the ELM call / usr / sbin / sendmail instead of RMAIL, so you need them. For example, if you put SMAIL in / usr / local / bin, type the following two lines under the Shell Tip: # ln -s / usr / local / bin / smail / usr / bin / rmail # ln -s / usr / local / bin / smail / usr / sbin / sendmail If you want to study more deeply to configure SMAIL, see Man Page SMAIL (1) and SMAIL (5). If it is not included in the Linux release version you wish, you can get from the SMAIL source program. 14.1 UUCP setting To use Smail in an environment with only UUCP, the basic installation process is very simple. First, you must be sure that you already have the two symbols mentioned above to connect Rmail and Sendmail. If you also want to receive SMTP batch information from other sites, you also need to set RSMTP as a connection to SMAIL. In the Smail release of Vince Skahan, you will find a sample profile. It is named config.SAMPLE and exists in / usr / lib / smail. You must copy it to config and edit it for your site.
Suppose your site name is SWIM.TWobirds.com and register with SWIM in the UUCP map. Your sensitive host is ulysses. At this point, your config file should look like this: # # 正 domain names visible_domain = two names: uucp # u = swim.twobirds.com # # Use this as uucp-name as well uucp_name = Swim.twobirds.com # # Our smarthost smart_host = ulysses The first statement informs SMAIL to the domain to which you are located. Insert them here and separate them with a colon. If your site name is registered in a UUCP map, then you should also add UUCP. When processing a mail message, SMAIL uses HostName (2) system call to determine your host's name, and check the receiver's address and this hostname, add all the names in this list. If the address matches any of these names or informal hostnames, the recipient is considered local, and SMAIL will attempt to deliver this message to a user or alias on the local host. Otherwise, the recipient is considered to be remote and starts trying to deliver to the destination host. Visible_name should contain a single, wholly-owned domain name for your site on the outbound mail. This name will be used when generating the sender's address on all outbound mail. You must be sure to use a SMAIL to identify the name representative of the local host (i.e., the host name listed in the Visible_Domain property.). Otherwise, the reply made to your email will pop up your site. The last statement sets the path for sensitive host routing (described in Section 13.4). For this sample setting, SMAIL forwards all messages to the remote address to the sensitive host. Since the message will be delivered through UUCP, this property must specify a system that your UUCP software knows. See Chapter 12 letting a site for uucp. There is also an option used in the above file we have not given an explanation so far; this is uucp_name. The reason for using this option is: By default, SMAIL uses the value returned by HostName (2) to UUCP, such as the return path given in the FROM / header row. If your hostname is not registered in the UUCP map plan group, you should tell Smail to replace it with your wholly-owned domain name. [2] This can be added to the UUCP_NAME option in the Config file. There is also a file in / usr / lib / smail, called Paths.Sample. It is an example of a Paths file. However, unless you have more messages that are more than one site, you don't need it. If you do have multiple mail connections, you need to write a file yourself or generate from the USENET map. The PATHS file will be discussed later in this chapter. 14.2 Setting up for the LAN (LAN) If you are running a site, there are two or more hosts constitute a LAN, then you must specify a host to handle your UUCP and external world connections. Between the hosts on your LAN, you are likely to exchange emails on TCP / IP with SMTP. Suppose we now return to the virtual winery again, and VSTOUT is set to become a gateway for UUCP. In a connected environment, it is best to place all users' mailbox on a single file system, which can be loaded in NFS on all other hosts. This allows users to change from one machine to another, do not need to bring their mail (or worse, every morning checking three or four machines) Do not have new mail).
So you also want the address of the sender to be unrelated to the machine written by the mail. In the address of the sender, the domain name is used instead of the host name, it is a very practical use method. For example, Janet users will specify an address ket@vbrew.com instead of janet@vale.vbrew.com. Below we will explain how to let the server identify the domain name as a valid name of your site. Another way to hold all mail box on a central host is to use POP or IMAP. POP represents Post Office Protocol that allows users to access their mailbox through a simple TCP / IP connection. IMAP, Interactive Mail Access Protocol, similar to POP, but more common. The clients and server programs of IMAP and POP have been ported to Linux, which can be obtained from / pub / Linux / system / network in sunsite.unc.edu. 14.2.1 Writing the configuration file brewery is working as follows: In addition to all hosts of the mail server VStout itself use sensitive host routing to pass all outbound messages to the server. VSTOUT itself sends all outbound mail to the true sensitive host used to pass all brewery mail; this host is called Moria. In addition to VStout, all other hosts of the standard config files look like this: # # u = vbrew.com # # whaat we name uresels visible_name = vbrew.com # # smart-host routing: via smtp to vstout smart_path = vStout Smart_Transport = SMTP This is very similar to our UUCP site. The main difference is that the transmission used to send mail to the sensitive host is SMTP. The Visible_Domain property allows SMAIL to use domain names on all outbound emails to replace the local hostname. On the uucp mail gateway vStout, the config file looks a little different: # # u htnames: hostnames = vbrew.com: vStout.vbrew.com: vStout # # What we name urselevs visible_name = vbrew.com # in the uucp world , we're known as vbrew.com uucp_name = vbrew.com # # Smart transport: via uucp to moria smart_path = moria smart_transport = uux # # we're authoritative for our domain auth_domains = vbrew.com this config file uses a different The solution tells the SMAIL local host called. Not given a domain list and let it use a system call to find the host name, but a list of a list is explicitly given. The above configuration itself contains wholly-owned and free host names, as well as domain names. This makes SMAIL to identify Janet@vbrew.com as a local address and deliver messages to Janet. Auth_Domains variable named a domain, for this domain, VStout is considered authorized. That is, when SMAIL receives any email to address host.vbrew.com, if Host is not the name of any local machine, then it will reject this mail message and return it to sender.
If there is no such entry, any such message will be sent to the sensitive host, and the Sensitive Host will return it to vStout, which is looped until the message is discarded due to the maximum number of hops. 14.2.2 Running SMAIL First, you have to decide whether Smail is run as a separate background program (daemon), or let the inetd manages the SMTP port and call SMAIL only when some clients request an SMTP connection. Typically, on the mail server, you will prefer the way the background program operation is modeled because this does not increase the SMAIL sub-process for each individual connection to increase the load. Since the mail server also passes most inbound messages to the user, you will choose the ONETD operation on many other hosts. For each individual host, no matter which mode of operation you choose, you must be sure to have the following entry in the / etc / service file: SMTP 25 / TCP # Simple Mail Transfer Protocol defines the TCP for SMTP connection The port number. 25 is a standard port number defined in the Assigned Numbers RFC. When running in the background mode, SMAIL will put yourself in the background and wait for the connection to occur in the SMTP port. When a connection occurs, it generates and boots an SMTP conversation with a peer process. The SMAIL background program typically uses the following command to start from the rc.inet2 script: / usr / local / bin / smail -bd -q15m -bd flag opens the background mode, -Q15M makes it processed every 15 minutes A message in the queue at a time. If you want to use the inetd method, then you should contain this line in your /etc/inetd.conf file: SMTP Stream TCP NOWAIT ROOT / USR / SBIN / SMTPD SMTPD SMTPD should be a symbolic link to the SMAIL execution file. Remember, after you have made changes, you must send it a HUP signal to let inetd reread inetd.conf. The daemon mode and inetd mode are mutually exclusive. If you run SMAIL in an inNive mode, you should be a trip to note any SMTP service in inetd.conf. Similarly, when inetd manages SMAIL, be sure that rc.inet2 does not start the SMAIL background program. 14.3 If you don't have successful completion ___ If you have encountered a problem during installation, there are several features that may help you find the root of the problem. The first place that needs to be checked is Samil's log file. They are placed in / var / spoo / smail / log, named logfile and paniclog, respectively. The former lists all matters, while the latter is only used to store errors information such as configuration errors. The typical entry in logfile looks like this: 04/24/94 07:12:04: [mopuwu8-00023ub] received | From: root | Program: Sendmail | Size: 1468 bytes 04/24/94 07:12: 04: [mopuwu8-00023ub] Delivered | VIA: vStout.vbrew.com | To: root@vstout.vbrew.com | Orig-to: root@vstout.vbrew.com | Router: smart_host | Transport: SMTP This shows The message of root to root@vstout.vbrew.com has been passed to host VStout via SMTP.
SMAIL can also produce a similar entry in the log file, but use an error message to replace the Delivered section: 04/24/94 07:12:04: [Mopuwu8-00023ub] received | From: root | Program: Sendmail | size: 1468 07:12:04: [mopuwu8-00023ub] root@vstout.vbrew.com ... Deferred (ERR_148) Transport SMTP: Connect: Connection Refused The above error For SMAIL, you can correctly identify The message should be delivered to VStout but the SMTP service of the VSTOUT is a typical error. If this happens, you or have a configuration problem, or because your SMAIL executor does not support TCP. This problem is not so special. There are many SMAIL executives that have compiled wells, do not support TCP / IP networking, even in some Linux issues. If you encounter this situation, you must compile SMAIL yourself. If you have already installed SMAIL, you can log in to your machine's SMTP port via Telnet to check if it supports TCP network. A successful connection to the SMTP service is as shown below (your input is used in this manner): $ telnet localhost smtp trying 127.0.0.1 ... connect to localhost. Escape character is '^]'. 220 monad.swb.de smail3. 1.28 # 6 Ready At Sun, 23 Jan 94 19:26 Met Quit 221 Monad.swb.de Closing Connection If this test does not generate SMTP titles (rows starting at 220 yards), first confident that yourself in your own SMAIL compile The configuration is indeed correct, which is discussed below. If you encounter a problem with SMAIL, and the error message generated from SMAIL cannot determine the problem, then you can turn on the debug information. You can use the -D flag to do, followed by a digital option that specifies the length of the debug information (you can add space before the flag and number). SMAIL will print out its operational report on the screen, which may give you more clues about an error. [I don't know, people may not think this is interesting:] If you have no help, you may want to call SMAIL by giving the -BR option on the command line. About this option man page says: "Send huge amounts of mail messages to the enemy domain, as well as the RFC standard. Try to let it go down to the protocol layer 26 and return." Although this option does not solve your problem, it may be for you Provide some comfort and comfort. [3] 14.3.1 Compiling SMAIL If you really think that your SMAIL has no TCP network support, you must get the source code. If you are getting from the CD-ROM, then it is generally included in your release, otherwise you can get from the online FTP site. [4] When compiling SMAIL, you'd better start using the configuration file set from Vince Skahan's NewSpak release. In order to compile with TCP network drivers, you must set the Driver_Configuration Macro in the conf / editme file to BSD-Network or Arpa-Network. The former is suitable for the installation of the LAN, but the Internet needs ARPA-NETWORK. The difference between the two is that the latter is a direct-specific driver that can identify the MX recorded BIND service, and the former is not. 14.4 Mail delivery mode As mentioned above, SMAIL can immediately deliver messages or discharge the queue later.
If you choose to discharge the message into the queue, SMAIL will store all messages in / var / spool / smail directory. SMAIL does not deal with these messages until it is clearly informative (this is also called "running the queue"). You can choose one of three delivery modes by setting the Delivery_Mode property in the config file. This selects the delivery mode to the front desk (immediately handles the inbound message), the background (the message will be delivered by the child process ", and the parent process will exit immediately after the child is derived), and queued . If the Boolean variable queue_only is set in the config file, then the inbound message will always be discharged into the queue regardless of this option. If you open the queuing option, you must be aware of the queue to be checked regularly; generally 10 or 15 minutes. If you run SMAIL in Daemon mode, you must add the option -Q10M on the command line to process a queue every 10 minutes. In addition, you can call RUNQ from cron with these intervals. Runq should be a link to SMAIL. You can call Smail by calling SMAIL with option -bp to display the current mail queue. Similarly, you can make a link to SMAIL Mailq, and call Mailq: $ mailq -v mopvb1r-00023ub from: root (in / var / spool / smail / input) Date: Sun, 24 APR 94 07:12 Met DST Args: -Oem -omp Sendmail Root@vstout.vbrew.com log of transactions: xdefer: Reason: (ERR_148) Transport SMTP;
Connect: Connection Refused
This shows a message in the message queue. Matters Logs (only when you give Mailq - V option) may give the additional reason why it is still waiting for delivery. If there is no trial to deliver this message so far, it will not be displayed.
Even if you don't use the queue, then when SMAIL finds that the message will be put into the queue when it is fails due to a short reason. For SMTP connections, this may be a unreachable host; but when the file system is full, the message will also be delivered. So you should place a queue and run the process queue once every 1 hour (using Runq), otherwise, any extension message will always stay in the queue.
14.5 Various other Config options
There are also many options that can be set in the config file, which is very useful, but the SMAIL is not required, so we don't discuss them here. But only the options you may use for some reason:
ERROR_COPY_POSTMASTER
If this Boolean variable is set, any error will generate a message to the mail manager. Usually, this is only to detect errors in the configuration. This feature is turned on by placing it in the config file and put a plus sign ( ) in front.
MAX_HOP_COUNT
If a message is hopped (i.e., the number of hosts) is equal to or exceeds this number, an attempt to deduct messages will generate an error message and returned to the sender. This is used to prevent messages from constraid looping. The count of hops is typically calculated from the number of Received: fields in the message header, but can also be manually set by using the -h option on the command line.
The default value for this variable is 20.
Postmaster mail administrator's address. If Postmaster cannot parse into a valid local address, as the last means. The default is ROOT. 14.6 Message (Packet) Routing and Delivery
SMAIL divides mail into three different tasks, routers, guides, and transmitter modules (Router, Director, Transport Module).
The router module is used to parse all remote addresses, and determine which host will be sent to the next host, and which transmitter must be used. Different transmitters, such as UUCP or SMTP are used depending on the characteristics of the link.
The local address will give the guide task for parsing any forwarding and alias. For example, the address may be a alias or a mailing list, or the user may want to forward her email to another address. If the resulting address is remote, it will be transmitted to the router module for additional routing, otherwise it will perform local delivery transfer. So far, the most common case is to deliver into a mail box, but the message may also be transmitted to a command, or is attached to some files.
Finally, the transmitter module is responsible for the choice of delivery. It tries to deliver this message and bounce the message if it fails, or delays the message.
With SMAIL, you have a lot of freedom when configuring these tasks. For each task, there are many drivers that you can choose from. To describe them to SMAIL, they are Routers, Directors, and Transports located in / usr / lib / smail. If these files do not exist, then reasonable default values will be adopted, these default values are suitable for many sites that use SMTP or UUCP transmission. If you want to change the SMAIL's routing policy, or to modify a transfer, you should get sample files from the SMAIL source release, copy the sample file to / usr / lib / smail directory, and follow you Need to modify them. Sample profiles are also given in Appendix B.
14.7 Routing of Message (Packet)
When a message is given, SMAIL first checks whether its destination is local or a remote site. If the target host address is one of the local hostnames configured in config, the message is transferred to the guide module. Otherwise, SMAIL will send the destination address to a series of router drivers to find the host forwarded the message. They can be described in the Routers file; if this file does not exist, a family default value can be used.
The next destination host (name) will pass to all routers and will choose the router that is the most determined route. Consider a message to joe@foo.bar.com. Then, a router may know the default route to all hosts in the bar.com domain, while the other router has the information of foo.bar.com itself. Since the latter is more accurate, the latter will be selected. If there are two routers that provide "best match", then the one of the Routers files will appear first.
Now, this router specifies the transmitter used, such as UUCP, and generates a new destination address. This new address is passed to this transmitter with the host (name) to forward the message. In the above example, SMAIL may find foo.bar.com by using the UUCP using path ernie! Bert. It will generate a new target bert! Foo.bar.com! User, and let the UUCP transmitter transmit this target as the envelope address to Ernie.
When using the default setting, there is a following router:
If the destination host address can use gethostByName (3) or gethostbyaddr (3) library to call the resolution, the message will be delivered in SMTP. The only exception is that if the address reference (involved) to the local host, the message is also transmitted to the guide module. SMAIL can also identify the IP address written in points four as a legitimate host name as long as they can be parsed using the gethostbyaddr (3) call. For example, Scrooge @ [149.76.12.4] will be a valid address, although this is a very different email address on QUARK.PHYSICS.GROUCHU.EDU.
If your machine is on the Internet, then these routers are not what you want, because they do not support MX records. See below for this situation.
If the path retrieval database / usr / lib / smail / paths exists, SMAIL will try to find the target host in this file (minus any .uucp's end). The mail that is sent to the address that the router matches the message will be delivered using the path found in the UUCP and the database.
Host address (removal any .uucp end) will compare the output of the UUNAME command to check whether the target host is actually a UUCP neighbor. If this is true, then the message will be delivered using a UUCP transmitter.
If the address cannot be matched with any of the routers above, it will be delivered to the sensitive host. The path to the sensitive host and the transmitter used are set in the Config file.
These default settings are workable for many simple settings, but if the routing requirements are slightly complex, it will fail. If you are facing any questions described below, you need to install your own Routers file to override the default file. A sample Routers file is given in Appendix B, you can start with it. Some Linux distributions also carry a family profile that is edited to overcome these difficulties.
When your host has a double dial IP and UUCP link, it may produce the worst problem. At this point you have a host name and host name that you only pass through the SLIP link, SMAIL will try to deliver any emails for these hosts via SMTP. This is usually not what you want, because even if the SLIP link is regularly activated, SMTP is much slower than the email passed through UUCP. For situations that use default settings, there is no way to evade Smail.
You can avoid this problem by allowing SMAIL to check the paths file before querying the parser, and put all the hosts you want to force to deliver the host into the PATHS file. If you don't want to send any messages via SMTP, you can also completely comment out of the parser-based router.
Another problem is that the default setting is not provided for real Internet mail routing, as the resolver-based router does not estimate (Evaluate) MX records. In order to enable full support for Internet mail routing, comment out this router and remove the annotation of the router using bind. However, the SAMIL executor included in some Linux distribution is not compiled into bind support. If you enable Bind, you get a message in the paniclog file. Top 14.2 above).
Finally, it is generally not a good idea using the UUNAME driver. The first is when you don't have UUCP, it will generate a configuration error because the uuname command will not be found. Second, when you are listed in your UUCP Systems file than the actual location, you are listed in your UUCP SYSTEMS file. These may be a site that you only exchange new, or you occasionally use an anonymous uucp to download files, but there is no traffic traffic outside this. In order to solve the first problem, you can replace UUname with only a simple exit 0 shell script. However, more conventional solutions are editing the Routers file and completely delete this driver.
14.7.1 Paths Database
SMAIL expects to find the path alias database (Pathalias Database) in the PATHS file under / usr / lib / smail. This file is optional, so if you don't need to perform any path alias route selection, just simply delete any pre-existing Paths files.
Paths must be a row-wide ASCII file that contains entries with map destination sites named UUCP BANG PATHS. Because SMAIL uses a binary tree search to find a site, this file must be row. The file must not be included, and the site name and the path must be separated from the table. The path alias database has been discussed in detail in Chapter 13.
If this file is written in yourself, you should be confident that all legitimate names of a site are included. For example, if a site is known to have a form of format UUCP name and a full-owned domain name (Fully Qualified Domain Name), you must join an entry for these two names. You can sort this file by passing this file to the Sort (1) command.
However, if your site is just a page site (a leaf site), then don't need a PATHS file at all; just set the sensitive host properties in your config file and let your email feeder processes all routes.
14.8 Delivery message to your local address (packet)
Very general, a local address is just a user's login name. In this case, the message is delivered to her mailing box, / var / spool / mail / user. Other cases include alias and mailing list names, as well as mail forwarders for users. In these cases, the local address is extended into a new address list, which is or local, or it may be remote.
In addition to these "normal" addresses, SMAIL can also handle the type, like file name and pipeline command for other local message purposes. These itself is not an address, so you don't send emails to the address of /etc/passwd@vbrew.com; only when they get from forwarding and alias files, they are valid.
A file name (File Name) is any string starting with a slash (/) or the broken number (~). The latter represents the user's home directory, and only when the file name is from one .forward file or from a forwarding entry in the mail box (see below). When delivering to a file, SMAIL attaches messages to this file and creates this file if necessary.
A PIPE command can be any un * x command in front of the pipeline symbol (|). This allows SMAIL to pass commands and its parameters to the shell, but does not include the preamble '|'. The message itself is fed on the standard input to this command.
For example, in order to send the mailing list into a local news group (NewsGroup), you can use a shell script called Gateit and set a local alias, this alias will use "-gateit" to deliver all from this mailing list. news. If the quote includes space, double quotation is used. Since the safety factor involved, if the address is obtained in some unreliable method (for example, if the alias file from which the address is being used is written), avoid executing this command.
14.8.1 Local users
The most common case of a local address is a mail box for a user. This mailbox is located in / var / spool / mail and has the name of this user. It belongs to this user and has a group name Mail and attribute 600. If it does not exist, SMAIL creates it.
Note that although / var / spool / mail is currently a standard location of a mailbox file, some mail software may compile different paths, such as / usr / spool / mail. If you go to your machine, you will have a failure, you should try to make a symbolic link to / var / spool / mail.
SMAIL requires two addresses: MAILER-Daemon and Postmaster. When a rebound message is generated as a message that cannot be delivered, a copy will be sent to the Postmaster account to check (in case of this possibility due to configuration issues). Mailer-daemon is on the rebound message as a sender address.
If these addresses do not have a valid account on your system, SMAIL implies MAILER-Daemon to Postmaster, Postmaster to Root. Usually you should override this mapping by establishing an alias for the Postmaster account, establish an alias to a user responsible for maintaining the mail software.
14.8.2 forwarding
Users can use SMAIL support to redirect her email by forwarding mail to another address. One choice is
Forward to Recipient, ...
Put in the first line of her mailbox file. This will send all inbound messages to the specified recipient list. Another method is that she can build a .forward file in her home directory, which contains a list of recipients separately with a comma. For all kinds of forwarding, each line of the file will be read and explained.
Note that any type of address can be used. Therefore, an actual example of a forefront file for a vacation can be
Janet, "| Vacation"
The first address will deliver the inbound message to the Janet's mailbox, and the Vacation command will return a short notice to the sender.
14.8.3 alien files
Samil can handle those alias files compatible with Berkeley's Sendmail. In the alias file, you can have the following form.
Alias: Recipients
Recipients is a list of addresses separately with a comma, which will be replaced by alias. The recipient list can be continued if the next line begins with a tab.
There is a special property that allows SMAIL to process mailing from alien files: If you specify ": include: filename" as a recipient, SMAIL will read the specified file and replace its content as a list of recipients.
The main alias files are / usr / lib / aliases. If you choose to make this file is writable, SMAIL will not deliver any message to the shell command given by the file. An example of an example is as follows:
# vbrew.com / usr / lib / aliases file
Hostmaster: Janet
Postmaster: Janet
Usenet: phil
# The development mailing list.
Developments: Joe, SUE, MARK, BIFF / VAR / MAIL / LOG / DEVELOPMENT
Owner-develop: Joe
# Announcements of General Interest is beamaled to all
# of the staff
Announce:: incrude: / usr / lib / smail / staff,
/ VAR / MAIL / LOG / ANNOUNCE
Owner-announce: root
# Gate The Foobar Mailing List to a local newsgroup
PPP-List: "| / usr / local / lib / Gateit local.lists.ppp"
If an error occurs when it is delivered to an address generated from the AliaSES file, SMAIL will try to send a copy of the error message to "Alias Owner"). For example, when delivering a message to the development message, if the delivery is delivered to the BIFF, the copy of an error message will be sent to the sender, as well as Postmaster and Owner-Development. If the owner's address does not exist, then additional error messages will not be generated.
SMAIL will become Nobody users when delivering the file or when the program given in the AliaSes file is called. Especially when delivering the document, this will be very troublesome. For example, in the files given above, Nobody must have this log file and write it, otherwise delivery to them will fail.
14.8.4 mailing list
In addition to using AliaSes files, mailing lists can also be managed through files in / usr / lib / smail / lists directory. A mailing list named nag-bugs is described by the lists / nag-bugs file, which should have the address of the group-separated group member. The list can be given in multiple lines, and the comment is used to use the HASH symbol.
For each mailing list, there should be a user (or alias) named Owner-ListName; any error that occurs when resolving an address will report. This address is also used as the sender's address in the Sender: Title field of all outbound messages.
14.9 Transmitter Based on UUCP
There are many compiled transporters that use the UUCP assembly to enter the smail. In a UUCP environment, the message is usually transmitted by calling Rmail on the next host and requires the RMAIL message on the standard input and the RMAIL envelope address. On your host, Rmail should be a link to the smail command.
When a message is handed to the UUCP transmitter, the SMAIL converts the target address into a UUCP BANG path. For example, User @ Host will be converted to Host! User. Any existing '% address operator will be retained, so user% host @ Gateway will be converted to Gateway! User% host. However, SMAIL does not generate such an address.
On the other hand, SMAIL can send and receive BSMTP batch by UUCP. Using BSMTP, one or more messages is wrapped in a single batch, this batch contains a command that will be issued when an actual SMTP connection is established. BSMTP is frequently used to store-forward (eg, UUCP-based) networks to save disk space. The sample transports file in Appendix B contains a Transmitter with a BSMTP batch in a queue directory that can generate partial BSMTP batch. In the future, use a shell script that adds the appropriate helo and quit commands, they must be merged into the final batch.
For the specified UUCP connection, in order to enable the BSMTP transmitter, you must use the so-called Method file (for more information, see the SMAIL (5) man page). If you only have a UUCP link and use a sensitive host router, you can enable send SMTP batch by setting the configuration variable smart_transport to BSMTP instead of UUX. To receive SMTP batch on UUCP, you must be sure that you have a unbatching command, and the remote site will send your own batch to this command. If the remote site also uses SMAIL, then you need to make RSMTP as a link to SMAIL. If the remote site runs Sendmail, you should additionally install a shell script called / usr / bin / bsmtp, which executes a simple "EXEC RSMTP" (symbolic link is not working).
14.10 SMTP-based transmitter
Current SMAIL supports an SMTP driver to deliver messages on TCP connections. [6] The host name is designated as a wholly-owned domain name that can be parsed by network software, or when the point four group representations enclosed in square brackets, deliver messages to any number of addresses on a single host. Yes. Typically, the address parsed by any bind, gethostbyname (3), or gethostbyaddr (3) router driver will be delivered to the SMTP transmitter.
The SMTP driver will be accepted to the remote host through the SMTP port listed in / etc / services. If it can't be reached, or the connection timeout, then it will be duck again later.
Delivery on the Internet, requiring the route of the destination host to design to the Route-Addr format described in Chapter 13, not as a BANG path. [7] Therefore, SMAIL will convert user% host @ Gateway (here Gateway is arriving through Host1! Host2! Host3) becomes source - routing address <@ host2, @ host3: user% host@gateway>, this will be as a message The envelope address is sent to HOST1. To open these transformations (together with the built-in BIND driver), you must edit the entry about the SMTP driver in the Transports file. A sample transports file is given in Appendix B.
14.11 Host Name Limit (Qualification)
Sometimes the unlimited host name specified in the sender or receiver address (that is, the host name without a domain name) is worth doing. For example, when a gateway is connected between the two networks, one of the networks requires the whole domain name. On an Internet-UUCP relay, the default host name is defined by default should be mapped to the UUCP domain. Other address modifications other than this are unreliable.
/ usr / lib / smail / qualify file tells SMAIL which domain name is attached to which host name. The entries in the Qualify file consist of a host name starting from the first column, and the domain name of the post-follow. The HASH symbols as the first non-space character is considered to be a notes. Each entry is to search according to the order of the appearance.
If the Qualify file does not exist, then no hostname qualification operation is performed at all.
Special host name * matches any hostname, thus allowing you to map all unbeated hosts before entering a default domain. It should only be used for the last entry.
In a virtual winery, all hosts have been set to use a wholly-owned domain name in the sender address. Unlimited recipients are considered to be in a UUCP domain, so only one single entry is required in the Qalify file.
# / usr / lib / smail / qualify, Last Changed Feb 12, 1994 by Janet
#
* UUCP
Comment
[1] This is a new standard location in Sendmail in accordance with the Linux file system standard. Another common location is / usr / lib. [2] The reason is: Suppose your host name is Monad, but it is not registered in the map. However, there is a site called Monad in the mapping, so each of Monad! Root, even from your direct UUCP neighbor, it will be sent to another monad. This is an annoying to anyone.
[3] Do not use it if your mood is bad.
[4] If you are bought from the vendor, you are eligible to get the source code in accordance with SMAIL copy conditions.
[5] You can find the default configuration file below from Samples / Generic from the source directory.
[6] The author said this support is "simple". For the future version of SMAIL, they predict a complete backend program that can be more efficiently processed.
[7] However, using the router in the Internet is completely unidentified. Instead, the wholly-owned domain name should be used.
source:
Linux free pigeon
