Linux Network Administrator Manual (20)
2000-07-31 15:41
Publisher: NetBull Readings: 1031 Translation: Zhao Wei GoHigh@shtdu.edu.cn Appendix A PLIP empty printer cable In order to make an empty printer cable for PLIP connections, you need two 25-pin connector (called DB-25) and some cables with 11 wires. This cable must not exceed 15 meters. If you look at the connector, you should be able to see the small number of each pin root, the pin in the upper left corner is 1 (if you will be wide-faced, the pin in the lower right corner is 25. For empty printer cable, you must connect two connector to the following pins: D0 2 - 15 Error D1 3 --- 13 SLCT D2 4 --- 12 Papout D3 5 --- 10 ACK D4 6 --- 11 Busy Ground 25 --- 25 Ground Error 15 --- 2 D0 SLCT 13 --- 3 D1 Papout 12 --- 4 D2 ACK 10 --- 5 D3 Busy 11 --- 6 D4 All other The pin remains unconnected. If this cable is shielded, the shield should only be connected to the metal housing of one end DB-25. Appendix B SMAIL Sample Profile This section shows a sample profile for a UUCP end site on a local area. They are sample files included in the SMAIL-3.1.28 release source program. Although I made a simple explanation for these documents, I suggest you read very beautiful SMAIL (8) manual, which discussed these documents in detail. One, you have understood the basic principles behind the SMAIL configuration, which is worth reading. This is very easy! The first file shown is Routers, which describes a small router for SMAIL. When SMAIL must deliver a message to a given address, it sends this address to all routers until one of them matches. The so-called match here refers to this router in its database, that is, its Paths file, / etc / hosts, or any route selection mechanism for the router interface. The entry in the SMAIL configuration file is always starting with a unique name, which determines the corresponding router, transmission method, or guide. They followed the list of properties of their behavior. This list list consists of a national global property, such as the driver used, and only the dedicated properties that only the corresponding driver can understand. The attribute is separated by commas, and the global and dedicated attribute are separated by a semicolon. In order to make these differences more obvious, assume that you have to maintain two independent path alias files; a routing information containing your domain, and the other contains global routing information, which is likely to be generated from the UUCP map. With SMAIL, you can now specify two routers in the Router file, which use the path alias (Pathalias) driver. This driver finds the host name in a path alias database.
It expects to give it a name in a private property: # # p = Pathalias, # l = uux; # ing matched, Deliver over uucp file = pathalias Paths / domain, # file is / usr / lib / smail / paths / domain proto = lsearch, # file is unsorted optional, # ignore if the file does not exist request = vbrew.com, # \ @ly * .vbrew.com hosts # # pathalias database for routing to hosts outside our domain world_paths: driver = pathalias, # look up host in a paths file transport = uux; # if matched, deliver over UUCP file = paths / world, # file is / usr / lib / smail / paths / world proto = bsearch, # file is sorted with sort (1) Optional, # ignore if the file does not exist -required "The second global property given in the BEFORE Search is defined in the two Routers entries to define the transmission mode used when the router is matched with the address. In our case, the message will be delivered by UUX transmission. Transfer mode is defined in the Transports file, which will be explained below. If you specify a method file instead of the Transports property, you can fine-tune which transmission method to deliver a message. The method file provides mapping from the target host to the transmission mode. Here we don't discuss this. The following Routers file defines a router for a local area network to query the parser library. However, on an Internet host, you may use a router that handles MX records. Therefore, you should open another INET_BIND router that is annotated to build a BIND driver in the SMAIL. In a hybrid environment in which UUCP and TCP / IP, you may encounter such problems, there is a host that occasionally with SLIP or PPP in the / etc / hosts file. Usually, you still want to send any emails to them via UUCP. To avoid the INET_HOSTS driver matching these hosts, you must put them in the Paths / Force file. This is another database of path alias and queries before the SMAIL query parser.
# A Sample / usr / lib / smail / routers file # # force - force uucp Delivery to Certain Hosts, Even # The isy is in out = pathalias, # ook up host in a paths file transport = UUX; # if matched, deliver over uucp file = paths / force, # file is / usr / lib / smail / path / force optional, # ignore if the file does not exist prot = lsearch, # file is unsorted (Linear Search) -required, # no required domains domain = uucp, # strip ending ".uucp" before searching # inet_addrs - match domain literals containing literal #IP addresses, such as in janet @ [191.72.2.1] inet_addrs: driver = gethostbyaddr, # driver to match IP domain literals transport = smtp; # deliver using SMTP over TCP / IP fail_if_error, # fail if address is malformed check_for_local, # deliver directly if host is ourself # inet_hosts - match hostnames with gethostbyname (3N) # Comment this out if you Wish to use the bind version instead. inet_hosts: driver = gethostbyname, # match hosts with the library function transport = SMTP; # use default SMTP -required, # no required domains -domain, # no defined domain suffixes -only_local_domain, # do not restrict to defined domains # inet_hosts - alternate version using BIND to access the DNS #inet_hosts: # driver = bind, # use built-in BIND driver # transport = smtp; # use TCP / IP SMTP for delivery # #defnames, # use standard domain searching #defer_no_connect, # try again if the nameserver is down # -local_mx_okay, # fail (do not pass through ) an mx # # t The local host # # Pathalias Database for intra-domain routing domain_paths: driver = pathalias, # l u hT in a path file transport = uux; # if matched, Deliver over uucp file =
Paths / domain, # file is / usr / lib / smail / paths / domain proto = lsearch, # file is unsorted optional, # ignore if the file does not exist request = vbrew.com, # \ @ly * .vbrew.com hosts # # pathalias database for routing to hosts outside our domain world_paths: driver = pathalias, # look up host in a paths file transport = uux; # if matched, deliver over UUCP file = paths / world, # file is / usr / lib / smail / paths / world proto = bsearch, # file is sorted with sort (1) Optional, # ignore if the file does not exist -required "before searching # smart_host - a partically specified smarthost director # If the smart_path attribute is not defined in # / usr / lib / smail / config, this router is ignored # The transport attribute is overridden by the global # smart_transport variable smart_host: driver. = smarthost, # special-case driver transport = uux; # by default deliver over uucp -path, # @ Use smart_path config file variable for the local address of the message for the local address is in DIR Configured in the ECTORS file. The composition of this file is similar to the Routers file, with a range of entries that define each guide. The guide does not deliver a message, which only performs some possible redirects (eg by alias), mail forwarding, etc. When the message is delivered to a local address, for example, the JANET, SMAIL sends the username to each guide. If there is a match, it or specifies a message to deliver a transmission mode (eg, to the user's mail box file), or generate a new address (for example, after evaluating an alias). Due to the security issues included, the guides usually do a lot of checks to see if the files they are using. The address acquired with some suspicious methods (for example, from a writable AliaSes file) is not secure. Some transmission drivers will reject such an address, such as delivering messages to a file transmission. In addition to this, SMAIL also associates users with each address. Any read and write operation is performed as a user. For example, for the mailbox to Janet, the address is of course associated with Janet. Other addresses, such as those obtained from the AliaSes file, is associated with other users, such as Nobody users. For details on these features, please refer to the SMAIL (8) manual page.
# A sample / usr / lib / smail / directors file # aliasinclude - expand ": include: filename" addresses produced # by alias files aliasinclude: driver = aliasinclude, # use this special-case driver nobody; # access file as nobody user if unsecure copysecure, # get permissions from alias director copyowners, # get owners from alias director # forwardinclude - expand ": include: filename" addrs produced # by forward files forwardinclude: driver = forwardinclude, # use this special-case driver nobody; # access file as nobody user if unsecure checkpath, # check path accessibility copysecure, # get perms from forwarding director copyowners, # get owners from forwarding director # aliases - search for alias expansions stored in a database aliases: driver = aliasfile, # general-purpose aliasing director -nobody, # all addresses are associated # with nobody by default anyway sender_okay, # don "t remove sender from expansions owner = owner- $ user; # problems go to an owner address file = / usr / lib / aliases, # default : sendmail compatible modemask = 002, # should not be globally writable optional, # ignore if file does not exist proto = lsearch, # unsorted ASCII file # dotforward - expand .forward files in user home directories dotforward: driver = forwardfile, # general-purpose forwarding director owner = real- $ user, # problems go to the user "s mailbox nobody, # use nobody user, if unsecure sender_okay; # sender never removed from expansion file = ~ / .forward, # .forward file in home directories checkowner , # the user can oown this file = root, # or root can oow the file modemask = 002, # it shouth not be globally writable caution = 0-10: uucp: daemon, # don
Trun Things as root or remotly accessible home directories unselease = "~ ftp: ~ uucp: ~ nuucp: / tmp: / usr / tmp", # forwardto - expand a "forward to" line at the top of # the user "s mailbox file forwardto: driver = forwardfile, owner = Postmaster, # errors go to Postmaster nobody, # use nobody user, if unsecure sender_okay; # don" t remove sender from expansion file = / var / spool / mail / $ {lc: user}, # location of user "s mailbox forwardto, # enable" forward to "check checkowner, # the user can oown file = root, # or root can own the file modemask = 0002, # Under System V, Group Mail Can Write Caution = 0-10: UUCP: DAEMON, # DON "T Run Things as root or daem # user - match users on the local host with delivery to their mailboxes user: driver = user; # driver to match usernames transport = local, # local transport goes to mailboxes # real_user - match usernames when prefixed with the string "real-" real_user: driver = user; # driver to match usernames transport = local, # local t ransport goes to mailboxes prefix = "real-", # for example, match real-root # lists - expand mailing lists stored below / usr / lib / smail / lists lists: driver = forwardfile, caution, # flag all addresses with caution nobody , # AND dam ootay, # do not remove the sender = Owner- $ user; # The list wer @ a name of the mailing list to limited limited file = lists / $ {lc: user}, in Successful routing or redirect a message, SMAIL transmits messages to the transmission mode specified by the router or guide that matches the address. These transmission methods are defined in the Transporst file. Once again, a transmission method is defined by a national and private options. The most important options for each entry are to process the transfer drivers, for example, the PIPE driver, which calls the command specified in the CMD property.
In addition to this, the transmission method can also be used in many global properties, which in the message header and it is likely to perform various transformations on the message body. For example, the return_path property enters a return_path field into the message header. UNIX_FROM_HACK properties make it add a> symbol in front of each row starting with from from.
# A sample / usr / lib / smail / transports file # local - deliver mail to local users local: driver = appendfile, # append message to a file return_path, # include a Return-Path: field from, # supply a From_ envelope line UNIX_FROM_HACK, # insert> before from in body local; # @ use local forms for Delivery File = / var / spool / mail / $ {lc: user}, # location of mailbox files group = mail, # group to o file for system v mode = 0660, # group mail can access suffix = "/ n", # append an extra newline # pipe - deliver mail to shell commands pipe: driver = pipe, # pipe message to another program return_path, # include a Return-Path: field from, # supply a From_ envelope line unix_from_hack, # insert> before from in body local; # use local forms for delivery cmd = "/ bin / sh -c $ user", # send address to the Bourne Shell parent_env, # environment Info from parent addr pipe_as_user, # @ user-id associated with address ignore_status, # ignore a non-Zero EXIT STATUS IGNORE_WRITE_ERRORS, # ignore write errors, IE, Broken pipe umask = 0022, # umask for child process -log_output, # do not log stdout / stderr # file - deliver mail to files file: driver = appendfile, return_path, # include a Return-Path: field from, # supply a From_ envelope line unix_from_hack, # insert> before from in body local; # use local forms for delivery file = $ user, # file is taken from address append_as_user, # use user-id associated with address expand_user, # expand ~ and $ within address suffix = "/ n", # append an extra newline mode = 0600, # set permissions to 600 # uux - Deliver to the Rmail Program on A Remote UUCP Site UUX: driver =
PIPE, UUCP, # Use uucp-style addressing forms from, # supply a from_ envelope line max_addrs = 5, # at MOST 5 Addresses per invocation max_chars = 200; # at Most 200 Chars of Addresses cmd = "/ usr / bin / uux - -r -a $ sender -g $ grade $ host rmail $ (($ user) $) ", pipe_as_sender, # have uucp logs contain caller log_output, # save error output for bounce messages # defer_child_errors, # retry if uux returns! an error # demand - deliver to a remote rmail program, polling immediately demand: driver = pipe, uucp, # use UUCP-style addressing forms from, # supply a From_ envelope line max_addrs = 5, # at most 5 addresses per invocation max_chars = 200; # at MOST 200 Chars of Addresses CMD = "/ USR / BIN / UUX ---A $ Sender -g $ GRADE $ Host! RMAIL $ ((USER) $)", PIPE_AS_SENDER, # Have uucp logs contain Caller log_output ., # save error output for bounce messages # defer_child_errors, # retry if uux returns an error # hbsmtp - half-baked BSMTP The output files must # be processed regularly and sent out via UUCP hbsmtp: driver = ap. PENDFILE, INET, # USE RFC 822-Addressing Hbsmtp, #batched smtp w / o helow and quit -max_addrs, -max_chars; # no limit on number of addresss file = "/ var / spool / smail / hbsmtp / $ host", User = root, # file is oowned by root mode = 0600, #OnLy Read- / Writable by root. # SMTP - Deliver Using SMTP over TCP / IP SMTP: DRIVER = TCPSMTP, INET, -MAX_ADDRS, -MAX_CHARS; # no limit On Number of Addresses Short_timeout = 5m, # Timeout for Short Operations long_timeout = 2H, # Timeout for Longer SMTP Operations Service =
smtp, # connect to this service port # For internet use: uncomment the below 4 lines # use_bind, # resolve MX and multiple A records # defnames, # use standard domain searching # defer_no_connect, # try again if the nameserver is down # -local_mx_okay , # fail an mx to the local host:
Linux free pigeon
