1.1 Target group. 1.2 Summary of contents. The internet Value Edition delivery unit extends internet Services by providing mail services.

Transcription

1 1 Preface The internet Value Edition delivery unit extends internet Services by providing mail services. 1.1 Target group This manual is intended for BS2000 administrators who want to install mail services. It is assumed that the reader is familiar with the operating system BS2000/OSD and the basic concepts of TCP/IP. 1.2 Summary of contents This manual is arranged as follows: Chapter 2: Overview This chapter presents the basic principles and functionality of the individual components of internet Value Edition. Chapter 3: Installation and Startup This chapter describes the installation of mail services in BS2000/OSD. It also deals with startup issues and the configuration file sendmail.cf. Chapter 4: Operation This chapter presents the most important programs for operating the mail services. U41097-J-Z

2 Notational conventions Preface 1.3 Notational conventions The following notational conventions are used to indicate important functional issues in the text of this manual: For informative texts i! For warnings References References within this manual include the page concerned in the manual and the section or chapter as necessary. References to topics in other manuals include the brief title of the manual concerned. You will find the full title in the list of related publications at the end of this manual. 1.4 README file Information on any functional changes and additions to the current product version described in this manual can be found in the product-specific README file. You will find the README file on your BS2000 computer under the file name SYSRME.INETVALU.010.E. The user ID under which the README file is cataloged can be obtained from your system administrator. You can view the README file using the /SHOW-FILE command or an editor, and print it out on a standard printer using the following command: /PRINT-DOCUMENT <filename>,line-spacing=*by-ebcdic-control 2 U41097-J-Z

3 2 Overview Sending and receiving electronic mail ( ) is one of the most important services on the Internet. The post offices are mail servers, which transfer s across the network and deliver them into mailboxes. Mail user agents provide convenient interfaces to create and send s, to access mailboxes, and also to display and process the received electronic mail further. The electronic post office on the Internet is based on the Simple Mail Transfer Protocol (SMTP), which is defined in RFC 821. Whereas only pure text messages could be transmitted originally, a wide variety of formats including images, for example, can be transmitted today. The sendmail TM product ported to BS2000/OSD is the most popular and widespread mail server in use today. sendmail TM is a registered trademark of Sendmail Inc. and includes software that was developed by the University of California in Berkley and its staff members. Two special protocols, the Post Office Protocol (POP3) and the Internet Mail Access Protocol (IMAP) provide access to mailboxes via user agents running on a remote system (PC). The internet Value Edition software package contains the components for the electronic mail service in BS2000/OSD, which is implemented via an SMTP Mail Server, a POP3 server and an IMAP server. In addition, there is also a simple local user agent in POSIX (Mailx) for sending and processing text messages in BS2000/OSD, provided POSIX-SH has been installed. 2.1 Functionality The SMTP server or Mail Transfer Agent (MTA) is responsible for transferring on the Internet based on the Simple Mail Transfer Protocols (SMTP). It can operate as a mail relay or mail end system. A further function worth mentioning here is the option of creating distribution lists and forwarding requests. This is achieved by defining aliases, which permit the user section of a local recipient address to be replaced by one or more recipient addresses. In order to find a suitable route to the end system, the mail server uses the Domain Name Service (DNS). U41097-J-Z

4 Functionality Overview The server receives messages either from another MTA or a mail user agent (MUA). Depending on the user address(es) in the message, it is then passed via a TCP/SMTP connection to another MTA and/or a local mail delivery agent (MDA). The local MDA stores the messages in special files (mailboxes) and thus plays an important role here. The MUA, by contrast, enables the messages in the local mailboxes to be processed further (i.e. read, forwarded, sorted, saved, replied to and deleted). In addition, it also enables messages to be created and passed on to the local MTA for delivery. Some MUAs can also transfer messages to a remote MTA via a TCP/SMTP connection. SMTP SMTP User Agent on PC User Agent Mailx Mail Server SMTP Remote Mail Server POP3 Client POP3 POP3 Server Mailbox IMAP IMAP Client IMAP Server Client BS2000/OSD Internet Server The POP3 and IMAP mechanism enables a client system (especially one not equipped with an MTA) to access the mailboxes of the server system. An IMAP and POP3 server is installed on the server system for this purpose. Among other things, the servers offer clients on a remote system (such as Eudora or Netscape Messenger, for example) the option of reading and deleting messages. 4 U41097-J-Z

5 Overview Functionality Structure of messages The structure of messages is defined in RFC 822. Messages consist of a message header and the message text. The header and text are separated by exactly one blank line. Both the header and the message text consist of readable characters in ASCII format. The message header is composed of multiple statements which, in principle, are each placed in a separate line, but may also be split over multiple lines for the sake of clarity. The statements consist of a name and a text section, for which the format is defined by the name. Depending on the name and also on other statements, a specific type of statement could occur in a message header exactly once, not at all, no more than once or any number of times. Most of the names are defined in RFC 822. RFC 1522 defines some extensions. Names beginning with X- are intended for private extensions. The program /usr/sbin/sendmail includes the SMTP protocol and represents the mail server. The server can be set up and controlled individually via the configuration file /etc/mail/sendmail.cf. On starting up the system, the mail server is started together with other servers and usually waits for requests on port number 25 by default. U41097-J-Z

6 Eine Dokuschablone von Frank Flachenecker

7 3 Installation and startup This chapter describes how you can install and start the server included in the internet Value Edition software package. Software requirements internet Value Edition V1.0 requires internet Services V Installation The following port numbers are used by default by the components included in the internet Value Edition: Port Protocol Explanation 143 tcp/udp IMAP Internet Message Access Protocol 110 tcp/udp POP3 Post Office Protocol - Version 3 25 tcp/udp SMTP Simple Mail Transfer Protocol The individual components of the internet Value Edition software package are installed as POSIX program packages via the package installation with the POSIX installation program (see the manual POSIX V1.0A Basics for Users and System Administrators ). In order to install and run the internet Value Edition, the PLAM library SINLIB.INETVALU.010 must be available as a sharable library under the user ID TSOS. This library contains all the elements to be installed in the UFS. The POSIX subsystem must be started. Since the internet Value Edition applications must be run as privileged applications, they must be installed under the SYSROOT or TSOS ID (UID=0, GID=0) with the POSIX installation tool as follows: /CALL-PROCEDURE *LIB(LIB=$TSOS.SINPRC.POSIX-BC.<version>,ELEMENT=POSINST) Function: Installation of POSIX program packages Product Name: INETVALU Product Version: 010 U41097-J-Z

8 Installation Installation and startup Following a successful installation, all other activities required are performed in the POSIX shell under the user ID TSOS. In order to do this, the POSIX shell, and thus the server, must be started under the user ID TSOS with the BS2000 command START-POSIX. The relevant commands and files can be found in the /usr/sbin and /etc/mail directories. List of the most important files used by sendmail: File name Type Explanation /usr/sbin/sendmail Program MTA; additional functions /usr/sbin/smtpd Link to sendmail sendmail daemon; -bd option /usr/sbin/newaliases Link to sendmail Updates the alias file; -bi option /usr/sbin/mailq Link to sendmail Prints the mail queue; -bp option /usr/sbin/mail.local Program Mail delivery agent (MDA) /usr/sbin/mailstats Program Prints mail statistics /usr/sbin/makemap Program Makes a keymap file /usr/sbin/smtpdpid Program Displays the daemon - Pid /usr/sbin/praliases Program Prints the alias file /etc/mail/aliases Text file Alias file /etc/mail/aliases.db Index file Alias file /etc/mail/sendmail.cf Text file Configuration /etc/mail/sendmail.pid Text file Log file for starting the daemon /etc/mail/install Directory Installation directory /etc/mail/sendmail.hf Text file Help texts /var/mail/ Directory Directory for mailboxes /var/mail/user Text file Mailbox; USER : user name /var/mqueue Directory Directory for message queues /etc/mail/sendmail.st Index file Statistics file (optional) /etc/rc2.d/strtsmtp Script Start procedure /etc/rc0.d/killsmtp Script Stop procedure /usr/sbin/startsmtp Script Starts the daemon manually /usr/sbin/stopsmtp Script Stops the daemon manually 8 U41097-J-Z

9 Installation and startup Startup 3.2 Startup After the internet Value Edition has been installed, the configuration file /etc/mail/sendmail.cf can be customized for specific situations as described in the sections below. The mail server can also be directly used without modifying the configuration file The sendmail.cf configuration file The configuration file sendmail.cf is read and interpreted on starting the sendmail program (in any function). It contains information on the local configuration (e.g. paths to important files) and the network environment as well as the rules for processing and delivering messages. A copy of the default configuration file can be found in the directory /etc/mail/install. Apart from the pathnames of important files (which match the default installation), the supplied sendmail.cf does not include any system-specific information. sendmail retrieves the required system-specific information via system calls and from the Domain Name Service (DNS). Before using sendmail, the domain name of the system (e.g. systemx.siemens.de) and the DNS aliases, if any, should be stored on the DNS server. The DNS server name must be saved in /etc/resolv.conf. This enables sendmail to be run without modifying the configuration file. The default configuration file was generated with the promiscuous relay feature and thus allows messages to be forwarded anywhere. The following sections provide you with a brief introduction to the structure of the configuration file Commands Commands are uppercase letters that must be placed in the first column of a line, followed by command-specific parameters. Blank lines and lines beginning with # are comment lines and are ignored. Continuation lines for commands begin with a space or tab character. In some commands (at least the rewriting rules), tab characters are an integral part of the command syntax. It is therefore important to ensure that these tab characters are retained when a configuration file is processed or transferred. This is particularly significant when copying the file into BS2000 with bs2cp, which converts tab characters to spaces by default. U41097-J-Z

10 Startup Installation and startup List of commands: Command V D C F R S O H M K P T E Meaning Version of the configuration file Declare macro Declare/extend class Read/extend class from a file Rewriting rule : check, evaluate and rewrite addresses Start of a ruleset Option Declare message header Declare mailer Declare key file Declare priority of delivery Declare trusted users Define environment variable Macros A macro assigns a text string to a symbol consisting of one or more characters. If the symbol is made up of multiple characters, it must be entered within braces. A number of symbols have a defined meaning for sendmail. The configuration file is only one of many locations at which such macros are defined. Private symbols should consist of multiple letters and begin with an uppercase letter. Macros are used in rules, header declarations and mailer declarations. 10 U41097-J-Z

11 Installation and startup Startup Example Symbol b j m w h u v Value Current time in the format defined by RFC822 Own canonical DNS host name (e.g. dcwww.mch.sni.de) Own domain name (e.g. mch.sni.de) Short name of the host (e.g. dcwww) Host portion of the recipient address of a message User name of the recipient of a message Version of the sendmail program Classes Classes (or class macros, to be more precise) are essentially the same as macros, except for the fact that a list of strings is assigned to the symbol here instead of one text string. In the case of a multiple declaration, the list is extended. The individual elements of a list are separated by blanks or tab characters. Example Symbol Value m Own domain name (e.g. mch.sni.de mch.siemens.de) w Listofhostnames (e.g. dcwww dcwww.mch.sni.de pgab0021 localhost [ ]) t Trusted users (e.g. root daemon ) Rules A rule (command R) consists of three parts: lhs (left hand side), rhs (right hand side) and an optional comment. There must be at least one tab character between the lhs and rhs and also between the rhs and comment. A ruleset (command S) combines the rules which follow into a single executable unit. The ruleset is identified by a numeric or alphanumeric ID and can be called from within rules like a subroutine. U41097-J-Z

12 Startup Installation and startup Before a rule is executed, each address to be processed is placed in a special area called the workspace and is split into tokens in the process. The delimiters are.:%@!^=/[] and are themselves also tokens. Blanks also serve as delimiters, but are not tokens. The lhs defines a pattern string, which may include wildcard operators. If the lhs does not match the contents of the workspace, the next rule is processed. In the pattern matches, the rhs operator is executed. This supplies the workspace again and also determines which rule is executed next. The wildcard operators of the lhs are: $* Match zero, one or more tokens $+ Match one or more tokens $- Match exactly one token $=x Match one or more tokens, which combine to form an element of class x. $~x Match a token that is not an element of class x. The rhs may begin with $: or $@. $: indicates that the rule which follows is to be executed next. $@ indicates that the ruleset has ended. Otherwise, the current rule is executed again until the match fails (risk of an infinite loop). The tokens replaced by a wildcard symbol are then available to the rhs again: The rhs operator $n (where n is a positive integer) represents the string replaced by the n-th lhs wildcard operator. With $>n, therhs calls ruleset n like a subroutine. $[...] determines the DNS name by a DNS call. $(...) enables access to a map (an index file). $@ inserts the host name; $: inserts the user name. $# resolves to a mailer (e.g. the local delivery agent or the SMTP delivery agent for a partner host) and terminates the address processing. 12 U41097-J-Z

13 Installation and startup Startup Example 1 $=w $: $j This rule converts the host name in an address of the form hostname into its canonical form. The user name (which may consist of one or more tokens) is replaced by the wildcard operator $+. The host name is compared with elements of class w (e.g. localhost, pgab0021, dcwww.mch.sni.de). In the case of a match, the workspace is replaced by the rhs with the user name followed by the macro j (the canonical host name). The next rule is then processed. Example 2 R$* % $* $2 This rule replaces all % characters (the rule is recursive). Example 3 R$* $#local $: $1 This rule can be called when it is already known that the address consists of only a user name. The local delivery agent is called with the user name $1 (broadly speaking) Mailers Mailers represent delivery agents. The following mailers are important here: the local mailer, which stores the messages in mailboxes, the program mailer, which passes messages to a program, and the IPC mailer (several variants), which passes messages to a remote MTA via a TCP/SMTP connection. Besides the mailers defined in the configuration file, there are also some predefined mailers (of which the most important is *file*, which appends messages to a file) Message headers The formats of some message headers (e.g. Received from...by... ) are defined in the configuration file, where strings can also be defined via macros. sendmail inserts the statements defined here into every message header (some only if the message header does not already contain a statement of the same name). U41097-J-Z

14 Startup Installation and startup Options There are about 80 options which, among other things, inform sendmail about path names to files and directories (except for sendmail.cf and sendmail.pid, which are compiled). The most important are the alias file (AliasFile) and the directory of message queues (Queue-Directory). timers and other parameters that affect the processing of message queues, parameters for processing the alias files, parameters for load monitoring, parameters for processing message headers Delivery priority The delivery priority determines the order in which queued messages are processed. It is derived from the contents of the Precedence statement (usually special-delivery firstclass list junk bulk ) and is an integer value (i.e. may be negative). If no assignment is possible, the value 0 is assumed Testing a modified configuration file A modified configuration file can be tested with the following command: sendmail -bt -C <conffile> conffile identifies the path name of the configuration file. If desired, a help text describing the test options can be displayed by entering a?. The test mode is exited by 14 U41097-J-Z

15 4 Operation This chapter presents the most important programs for operating the mail services. 4.1 The sendmail program sendmail can execute many functions under the control of command parameters. The most important control flags are described below. The command syntax is: path name flag recipient addresses The -b flag defines the functionality of sendmail. Path name Flag Address Function Notes sendmail -bd Start daemon The startsmtp script must be used to manually start the daemon (even if it is already active). smtpd Same as sendmail -bd sendmail -bi Update alias file The index file /etc/mail/aliases.db is derived from /etc//mail/aliases. The aliases will then also be available to an already running daemon. newaliases Same as sendmail -bi sendmail -bp List contents of the mail queue directory mailq Same as sendmail -bp sendmail -bm Mandatory entry Send message Sends a text message from the standard input to the specified recipient (only for testing purposes). This is the default setting. U41097-J-Z

16 The sendmail program Operation Path name Flag Address Function Notes sendmail -bv Mandatory entry Verify address Alias evaluation; determines the mailer s sendmail sendmail -bt Test mode Tests rules and other functions of the configuration file. After sendmail responds with Enter <ruleset> <address>, you can enter a? to obtain a help text. Other flags are described starting on page 16 and page 23, respectively Processing the mail queue with the -q flag Every message that is received by sendmail, regardless of the source, is initially saved in files in the /var/mqueue directory. When the message has been successfully forwarded or the monitoring period has expired (queuereturn in the sendmail.cf), the saved files are deleted. The file names consist of 10 characters, of which the last 8 are the queue identification, which also appears in some headers (e.g. Received...by...). Files that begin with qf contain headers and control information (e.g. time when first sent). Files that begin with df contain the message text. The first character of the queue-id indicates at which hour of the day the file was created (0h corresponds to A, 1h to B, etc.). The last 5 characters are derived from the process identification. Characters 2 and 3 are normally AA, but are incremented when required (queue-id already assigned). If a message cannot be forwarded immediately, e.g., because the partner MTA has not responded, then the sendmail flag -q can be used to control when the next attempt to forward the message should be made. This task is usually performed by the daemon, which canbestartedinthestartsmtp script as follows: smtpd -q1h In the above case, the processing of the queue is repeated at hourly intervals. The time interval can be specified in weeks (w), days (d), hours (h), minutes (m) and seconds (s). It is also possible to specify combined values such as 1h30m. 16 U41097-J-Z

17 Operation Additional programs The processing of the queue can also be started manually for all queues or for selected queues: -q Single start for all queues -qiqid Start for all queues whose queue-id contains the string qid. -qrrec Start for all queues for which the recipient contains the string rec. -qssen Start for all queues for which the sender contains the string sen. The above selection criteria may also be combined, which corresponds to a logical AND operation. If the -v flag is also specified, information on the queue processing is output. The command mailq with these flags shows which queues would be processed, but does not start the processing (the -v flag is redundant here). 4.2 Additional programs The local delivery agent mail.local The local delivery agent writes the messages addressed to a valid local user into the mailbox of that user. The path name of the mailbox is /var/mail/user, whereuseristhe user name written in uppercase letters (the conversion of the user name to uppercase occurs in mail.local). If the file does not exist, it is created. Otherwise, the message is appended to any existing messages. Further processing of the messages can be achieved via the local mail program (provided POSIX-SH is installed) or via a remote POP3 or IMAP-based user agent. In the case of remote user agents, note that an account number for the accounting of a POSIX remote login session must be available for the USER (BS2000 command: /ADD-USER or /MODIFY-USER-ATTRIBUTES POSIX-RLOGIN-DEFAULT=*YES). U41097-J-Z

18 Additional programs Operation Printing the alias file with praliases The praliases program prints the information from the alias map file /etc/mail/aliases.db. Local names appear in lowercase letters. The entry is reserved for internal use in sendmail (excludes updating of the alias file). This program is generally suitable for printing any map file in the format xxx.db: praliases -f xxx Creating a map file with makemap makemap can be used to create or extend a map file from a text file (or directly from standard input). (makemap is not needed if the standard configuration file is being used). Syntax: makemap flag hash mapfile < textfile mapfile may be specified without the.db suffix. hash is the type of map file. Blank lines or lines starting with # in the text file are ignored. Valid lines begin with a keyword, followed by a space or tab character, followed by the assigned date: Flags: -d Duplicate keys are allowed -f No conversion to lowercase letters -o Extension of the map file -r Replaceanexistingkey -v Display information on the changes 18 U41097-J-Z

19 Operation Additional programs Printing the statistics file with mailstats The mailstats program prints the statistics file /etc/mail/sendmail.st: If no statistics are to be recorded, the statistics file can be deleted. The command to restart the recording of statistics is: touch /etc/mail/sendmail.st Example Statistics from Thu Jul 23 15:40: M msgsfr bytes_from msgsto bytes_to msgsrej msgsdis Mailer 0 0 0K 4 4K 0 0 prog 1 0 0K 4 4K 0 0 *file* K K 9 0 local K K 13 1 esmtp 7 3 3K 7 8K 0 0 relay T K K 22 1 The first and last columns identify the delivery agent (mailer). msgsfr Messages from this mailer msgsto Messages sent via this mailer bytes_from Length of the messages in Kilobytes bytes_to Length of the messages in Kilobytes msgsrej Messages rejected by this mailer msgsdis Messages discarded by this mailer The bottom line shows the total values. U41097-J-Z

20 Aliases Operation 4.3 Aliases Aliases enable the user section of a local recipient address to be replaced by one or more recipient addresses. These addresses can be local addresses, remote addresses, programs to which the messages are passed or files in which the messages are stored Defining aliases The most important source for aliases is the alias file /etc/mail/aliases (or the map file /etc/mail/aliases.db derived from it). /etc/mail/aliases is a text file. Lines beginning with # and blank lines are ignored. Lines that begin with a space or tab character are treated as continuation characters. Analiasisdefinedintheform: local : alias or: local : alias1, alias2, alias3,..., aliasn local is the user section of a local recipient address and must not contain any space characters. It is always stored in lowercase letters. alias can be: a local name (such as local) a remote address (e.g. user@domain) /file program program arguments :include: alias list If alias is a local name, it is subjected to a repeated alias substitution. This can be prevented with a preceding \. If alias is a remote address, the message is sent to that remote address. If alias is a file, the message is appended to the file. If alias a program, the message is piped to the program. An alias list is a text file. Blank lines and lines beginning with # are ignored. Everything else is interpreted as part of the alias (even # characters are possible). Otherwise, the alias list is subject to the same rules as for aliases in the alias file. 20 U41097-J-Z

21 Operation Aliases When an alias list is declared in the alias file, it should be assigned an owner who can be notified in the event of errors. The correct definition of an alias list in the alias file would thus be: locnam : :include: aliaslist owner-locnam : owner-name In order to ensure that the error message is not lost even if it cannot be delivered to the owner, there should also be an entry in the form: owner-owner : postmaster If, after aliasing, it is determined that the message is to be delivered to a user, the system then checks whether a.forward file exists in the user directory. If such a file exists, a further level of aliasing occurs. The.forward file has the same format as an alias list. The local names postmaster and mailer-daemon (the sender of error messages) must be present in the alias file. U41097-J-Z

22 Aliases Operation Example of an alias file and alias list # Alias file # Discard messages to MAILER-DAEMON MAILER-DAEMON: /dev/null # sendmail administrator postmaster: LWI # General list administrator owner-owner: LWI # Multiple recipients. First recipient : Actual user name lwi: \lwi, logger # Addressing via IP address vm2: bcaposix@[ ] # Append message to file Logger: /home1/lwi/logger # Pass message to a script grepfile: "grep -i lwi > /home1/lwi/logger" # Addressee is an alias list DC21BC: :include: /home1/lwi/dc21broadcast owner-dc21bc: LWI # Alias list # DC21broadcast DC21 staff members. Willi.Lutz@s32.MCH1.x400.sni.de Werner.Bayer@s32.MCH1.x400.sni.de Updating (newaliases), printing (praliases) and checking Aliases are defined or deleted in two steps: 1. Editing the /etc/mail/aliases file 2. Updating the /etc/mai/aliases.db mapfilewiththenewaliases command Following these steps, the modified aliases will also be available to an already running daemon. 22 U41097-J-Z

23 Operation Diagnostic aids The contents of the alias file can be printed with the praliases program. The processing of an alias can be verified with sendmail -bv alias 4.4 Diagnostic aids Log file sendmail records entries in the log file (e.g. /var/adm/messages). The number of entries recorded by sendmail is controlled via the LogLevel option in the sendmail.cf file (0: no entries; 9 is the default setting). Note that the LogLevel is associated with the syslog priority as follows: LogLevel >10 syslog priority LOG_CRIT and LOG_ALERT LOG_NOTICE LOG_INFO LOG_DEBUG Under LOG_INFO, entries are recorded for every sent or received message Sending a text file while displaying the SMTP dialog A text file can be sent with the following command: sendmail v <recipient-address> < <text-file> The v option shows the SMTP dialog on the standard output. U41097-J-Z

24 Eine Dokuschablone von Frank Flachenecker

25 Related publications BCAM Volume 1 (BS2000/OSD) User Guide Target group The BCAM manuals are intended for network planners, generators and administrators who define BS2000 systems. Contents Volume 1 describes BCAM itself, how it is embedded in TRANSDATA and open networks, plus generation and administrative activities. Volume 2 contains the commands, macros and error messages required for generation and operation. BCAM Volume 2 (BS2000/OSD) Reference Manual Target group The BCAM manuals are intended for network planners, generators and administrators who define BS2000 systems. Contents Volume 1 describes BCAM itself, how it is embedded in TRANSDATA and open networks, plus generation and administrative activities. Volume 2 contains the commands, macros and error messages required for generation and operation. opennet Server V1.0 SNMP Management for opennet Server User Guide Target Group The manual is intended for people responsible for networks and systems who want to use SNMP-based network and system management. Contents The manual provides a detailed description of the MIBs supplied with opennet Server, and the installation and operation of the subagents. A separate chapter contains an in-depth description of how to operate the BCAM Manager. U41097-J-Z

26 Related publications internet Services V1.0 (BS2000/OSD) Administrator s Guide Target group This manual is intended for network planners, generators, and administrators who with to use Internet Services in BS2000/OSD. Contents internet Services replaces the delivery units TCP-IP-AP and TCP-IP-SV. The manual describes the functionality of the Internet Services BOOTP/DHCP, TFTP, DNS, FTP, LDAP, and NTP in BS2000/OSD, and also outlines how to use the FTAC interface for FTP. Installation, administration, operation, and logging and diagnostic options of the various components are also covered in the manual. internet Services V1.0 (BS2000/OSD) User Guide Target group This manual is intended for network planners, generators, and administrators, and also users who wish to use Internet Services in conjunction with BS2000/OSD. Contents internet Services replaces the delivery units TCP-IP-AP and TCP-IP-SV. The manual provides an introduction to the components of internet Services. It contains a detailed description of how to use FTP, the FTAC interface for FTP, and TELNET. Network administrators require this manual as a supplement to the Administrator s Guide. internet Value Edition V1.0 (BS2000/OSD) User Guide Target group This manual is intended for network planners, generators, and administrators who with to use Mail Service in BS2000/OSD. Contents internet Value Edition is a supplement to internet Services that is available free of charge. The manual introduces users to the components of internet Value Edition, and provides information on installation, administration, and operation of the Mail Service in BS2000/ OSD. 26 U41097-J-Z

27 Related publications IMON (BS2000/OSD) Installation Monitor User Guide Target group This manual is intended for systems support staff of the BS2000/OSD operating system. Contents The manual describes the installation and administration of BS2000 software using the IMON installation monitor and its three components IMON-BAS, IMON-GPN and IMON- SIC. Installation (standard and customer-specific) using the component IMON-BAS for systems with BS2000-OSD V2.0 and as of BS2000-OSD V3.0 is described in detail with the aid of examples in two separate chapters. BS2000/OSD-BC Introductory Guide to Systems Support User Guide Target group This manual is addressed to BS2000/OSD systems support staff and operators. Contents The manual covers the following topics relating to the management and monitoring of the BS2000/OSD basic configuration: system initialization, parameter service, job and task control, memory/device/user/file/pubset management, assignment of privileges, accounting and operator functions. U41097-J-Z

28 Related publications additional publications sendmail BryanCostaleswithEricAllman O Reilly TM ISBN Ordering RFCs If the Requests for Comments (RFCs) referred to in the text are not included with delivery, they can be ordered in hardcopy form (copying charge) or fetched as a file from "anonymous Internet FTP" or via . Anonymous Internet FTP: in order to fetch an RFC via the Internet from the system nic.ddn.mil (IP address ), please proceed as follows: set up an FTP connection to the system: ftp nic.ddn.mil you can now load the required documents from the directory rfc; a list of the available documents can be found in the file rfc-index.txt. If you do not have Internet access but can use electronic mail, you can request an RFC in this way. The document will be sent to you in response to your Mail query. To do this, send a mail to the user service on the system nic.ddn.mil: mail service@nic.ddn.mil In the Subject field enter the number of the desired RFC, e.g.: Subject: RFC U41097-J-Z

29 Related publications Written queries concerning RFCs should be submitted to: DDN Network Information Center SRI International 333 Ravenswood Ave. Menlo Park, CA 94025, U.S.A. Telefon: Ordering manuals Please apply to your local office for ordering the manuals. U41097-J-Z

30 Eine Dokuschablone von Frank Flachenecker

31 Index /etc/mail/aliases.d alias file 18 /etc/mail/sendmail.cf configuration file 9 /etc/mail/sendmail.st statistics file 19 /usr/sbin/sendmail mail program 5 /var/adm/messages logging file 23 /var/mqueue mail queue 16 A alias file /etc/mail/aliases.db 18 example 22 printing (prealiases) 18 aliases 20 defining 20 function 3 C class example 11 class macro example 11 class macros classes 11 classes class macros 11 configuration file 11 commands configuration file 9 list 10 processing the mail queue 17 rewriting rules 9 tab character 9 configuration file /etc/mail/sendmail.cf 9 classes 11 commands 9 default configuration file 9 delivery priority 14 macros 10 mailer 13 message header 13 options 14 rules 11 testing 14 creating map file (makemap) 18 D default port number IMAP server (143) 7 mail server (25) 5 POP3 server (110) 7 SMTP server (25) 7 defining aliases 20 delivery agent configuration file 13 mail.local 17 delivery priority configuration file 14 precedence statement 14 directory installation 8 U41097-J-Z

32 Index DNS connection to sendmail 9 E example 19 alias file 22 class macro 11 macros 11 rules 13 F file installing 8 format 20 function 4 aliases 3 IMAP 4 POP3 4 functionality sendmail 3 H header message header 5 I IMAP 4 Internet Mail Access Protocol 3 IMAP server port number installation 7 directory 8 TCP-IP-SV 7 used files 8 installation tool POSIX 7 Internet Mail Access Protocol IMAP 3 internet Value Edition installation 7 software requirements 7 startup 9 L lhs wildcard operator 12 logging file /var/adm/messages 23 M macros configuration file 10 example 11 mail delivery agent MDA 4 mail program /usr/sbin/sendmail 5 mail queue /var/mqueue 16 processing commands 17 mail server port number 25 5 Mail Transfer Agent MTA 3 mail user agent MUA 4 mail.local delivery agent 17 mailbox 4 mailer configuration file 13 mail.local 17 mailstats printing the statistics file 19 makemap creating a map file 18 map file creating (makemap) 18 MDA mail delivery agent 4 message header configuration file 13 header 5 message text text messages 5 messages structure 5 32 U41097-J-Z

33 Index MTA Mail Transfer Agent 3 MUA mail user agent 4 O operator lhs wildcard 12 rhs 12 wildcard 12 options configuration file 14 order RFC 28 P PLAM library SINLIB.INETVALU POP3 function 4 Post Office Protocol 3 POP3 server port number port number IMAP server (143) 7 mail server (25) 5 POP3 server (110) 7 SMTP server (25) 7 POSIX installation tool 7 Post Office Protocol POP3 3 prealiases printing programs for the alias file 18 precedence statement delivery priority 14 print statistics file (mailstats) 19 processing mail queue 16 processing the mail queue 16 program /usr/sbin/sendmail 5 programs mailstats 19 makemap 18 praliases 18 sendmail 15 protocol Simple Mail Transfer Protocol 3 protocols Internet Mail Access Protocol 3 Post Office Protocol 3 R recording of statistics start 19 rewriting rules commands 9 RFC order 28 rhs operator 12 rules configuration file 11 example 13 S sendmail DNS connection 9 functionality 3 installing files 8 mail queue 16 programs 15 sendmail.cf configuration file 9 Simple Mail Transfer protocol SMTP 3 SINLIB.INETVALU.020 PLAM library 7 SMTP Simple Mail Transfer Protocol 3 SMTP server port number 25 7 software requirements requirements software 7 start recording of statistics 19 U41097-J-Z

34 Index startup 7, 9 statistics file 19 /etc/mail/sendmail.st 19 example 19 structure messages 5 T tab character commands 9 TCP-IP-SV installing 7 testing configuration file 14 tokens 12 W wildcard operator U41097-J-Z

35 Contents 1 Preface Targetgroup Summaryofcontents Notationalconventions READMEfile Overview Functionality Installation and startup Installation Startup Thesendmail.cfconfigurationfile Commands Macros Classes Rules Mailers Messageheaders Options Deliverypriority Testingamodifiedconfigurationfile Operation Thesendmailprogram Processingth queuewiththe-qflag Additionalprograms Thelocaldeliveryagentmail.local Printingthealiasfilewithpraliases Creatingamapfilewithmakemap Printingthestatisticsfilewithmailstats Aliases Definingaliases Exampleofanaliasfileandaliaslist Updating (newaliases), printing (praliases) and checking Diagnosticaids U41097-J-Z

36 Contents Logfile SendingatextfilewhiledisplayingtheSMTPdialog Related publications Index U41097-J-Z

37 internet Value Edition V1.0 (BS2000/OSD) User Guide Target group This manual is intended for network planners, generators, and administrators, and also users who wish to use Internet Services in conjunction with BS2000/OSD. Contents internet Services replaces the delivery units TCP-IP-AP and TCP-IP-SV. The manual provides an introduction to the components of internet Services. It contains a detailed description of how to use FTP,the FTAC interface for FTP,and TELNET.Network administrators require this manual as asupplement to the Administrator s Guide. Edition: July 1999 File: ival_bhb.pdf Copyright Siemens AG All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers. U41097-J-Z

38 Siemens AG Information and Communication Products Computer Systems User Documentation BS Munich Germany Comments Suggestions Corrections Fax: (++49) Submitted by Comments on internet Value Edition V1.0 U41097-J-Z

39 Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions. Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the The Internet pages of Fujitsu Technology Solutions are available at and the user documentation at Copyright Fujitsu Technology Solutions, 2009 Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions. Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion. Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind. Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Die Internetseiten von Fujitsu Technology Solutions finden Sie unter und unter finden Sie die Benutzerdokumentation. Copyright Fujitsu Technology Solutions, 2009