HP 3000 Manuals HP 3000 Manuals
Configuring the Local MTA To configure the local MTA, * Select the LOCMTA item from the Configure X.400 menu. This displays the Configure Local MTA screenwhich allows you to define the attributes for the local MTA/RTS on X.400.Figure 6-1. Configure Local MTA Screen The fields on the screen are: MTA Name (Message Transfer Agent) Required. Default: SERVER. Enter the name that has been assigned to your local MTA. The local MTA name cannot be the same as an adjacent MTA name, HP X.400/HP Desk Node name, Sendmail connection name, OpenMail connection name, or API client name. The RTS sends this name when establishing a connection with an adjacent MTA when passwords are used. This field is a printable string of up to 32 characters. Country Code Required. See Appendix C for a list of country codes. Administration Domain Name Optional. If this MTA only connects to PRMDs, leave this field blank. This field is a printable string of up to 16 characters. See Appendix D for a list of ADMDs. Private Domain Name Optional. If your local MTA is part of a private network, enter the name assigned by your company or organization to identify the network. This field is a printable string of up to 16 characters. Is TSAP HEX or ASCII Required if TSAP value is entered. Enter H if (H/A)? the TSAP address is to be entered in the HEX format, or A for the ASCII format. If there is a TSAP address displayed in the next field, this field displays the format of the TSAP. If you change the format, the displayed TSAP address converts to the new format. A TSAP value in ASCII format is converted to its HEX format by concatenating the hexadecimal ASCII codes of the characters. For example, the HEX format of the ASCII TSAP value MHS is 4D4853. This is obtained by concatenating the hexadecimal ASCII code for M (4D), the hexadecimal ASCII code for H (48), and the hexadecimal ASCII code for S (53). If the present TSAP is in HEX and the ASCII equivalent contains unprintable characters, then the TSAP value does not convert into ASCII when you enter A. You need to erase the TSAP value in the next field before you can enter A in this field. Local TSAP (Transport Selector): Optional. Default: 4D4853 (HEX), MHS (ASCII). Transport Service Access Point (or transport selector) that identifies the X.400 MHS on the local system. The combination of the TSAP and SSAP values should be unique on the local system. The previous field indicates the format of this TSAP address. If this field is HEX, it can contain up to 32 hexadecimal digits, must have an even number of digits, and can contain spaces to make the field easier to read. If this field is ASCII, it can contain up to 16 characters (spaces are valid characters). If this field is modified, you must restart OTS and then restart the RTS. Is SSAP HEX or ASCII Required if SSAP value is entered. In general, (H/A)? the SSAP value is not entered. Enter H if the SSAP address is to be entered in the HEX format, or A for the ASCII format. If there is an SSAP address displayed in the next field, this field displays the format of the SSAP. If you change the format, the displayed SSAP address converts to the new format. An SSAP value in ASCII format is converted to its HEX format by concatenating the hexadecimal ASCII codes of the characters. For example, the HEX format of the ASCII SSAP value MHS is 4D4853. This is obtained by concatenating the hexadecimal ASCII code for M (4D), the hexadecimal ASCII code for H (48), and the hexadecimal ASCII code for S (53). If the present SSAP is in HEX and the ASCII equivalent contains unprintable characters, then the SSAP value does not convert into ASCII when you enter A. You need to erase the SSAP value in the next field before you can enter A in this field. Local SSAP (Session Selector) Optional. Session Service Access Point (or session selector) that identifies the X.400 MHS on the local system. The combination of the TSAP and SSAP values should be unique on the local system. In general, this field should be left blank. The first version of the U.S. GOSIP 1.0 profile (FIPS 146) recommended that the X.400 SSAP value be HEX 02 which conflicted with the CCITT 1984 X.400 standard specifying that the SSAP should always be null. This conflict was resolved in a later version of the U.S. GOSIP profile, but some vendors' GOSIP compliant implementations may not have incorporated the revision. If you are connecting to such an implementation, you may need to enter 02 in HEX here. Configuring an SSAP value may cause problems with other vendors whose X.400 implementations do not allow SSAP values to be entered. Please contact your HP Representative if you have questions or concerns regarding SSAP configuration. The previous field indicates the format of this SSAP address. If this field is HEX, it can contain up to 32 hexadecimal digits, must have an even number of digits, and can contain spaces to make the field easier to read. If this field is ASCII, it can contain up to 16 characters (spaces are valid characters). If this field is modified, you must restart OTS and then restart the RTS. Default Access Control Optional. Default: SEND AND RECEIVE. Limit X.400 connectivity of users not in any user groups to send and/or receive or to have no permission to send and receive. If you add or modify a user group, this value is used as the default access control value. To select a new value for this field, press the Help key. Your choices are: SEND AND RECEIVE, SEND ONLY, RECEIVE ONLY, and NEITHER SEND NOR RECEIVE. Default Profile Supported Optional. Default: NIST84. Define the profile type supported at the user agent level for users not in any user groups. If you add or modify a user group, this value is used as the default profile supported. To select a new value for this field, press the Help key. Your choices are: EWOS88 (1988 X.400, Europe), NIST88 (1988 X.400, U.S.A.), NIST84 (1984 X.400, U.S.A.), CEN41201 (1984 X.400 for PRMD to PRMD connections, Europe), and CEN41202 (1984 X.400 for ADMD to PRMD connections, Europe). If the X.400 system conforms to more than one of these, use the first profile listed. For example, if the X.400 system conforms to NIST84 and EWOS88, select EWOS88. If the X.400 system conforms to 1984 X.400 standard only, then it can only generate 1984 X.400 messages. Default Character Set Supported Optional. Default: IA5. Define the character set that can be received by users not in any user groups. When another user group attempts to communicate with you using OpenMail, the appropriate character set is used for the message sent to you. If you add or modify a user group, this value is used as the default character set supported. To select a new value for this field, press the Help key. Your choices are: T.61 (teletex), ISO6937, and IA5. Allow an incoming connection from a non configured adjacent MTA? Required. Default: n. If the RTS is to (y or n) receive messages from an MTA which is not configured on the local system as an adjacent MTA, enter y. If the RTS will not receive messages from an unknown MTA, enter n. If RTS event logging is enabled, events received from adjacent MTAs that are not configured are logged into /usr/spool/x400/log/default.evnt. ______________________________________________ NOTE Use the allow incoming connections feature with caution. If you allow connections from unknown MTAs that know the local MTA's TSAP and NSAP addresses, these unknown MTAs can send unwanted mail or use the local MTA as a relay node. ______________________________________________ When the fields on this screen are correctly defined, * Press the Perform Task key to save the data in the configuration file. A confirmation message displays. If an SSAP value is configured, a warning message displays reminding you that the SSAP field should be left blank unless all systems you are connecting to are U.S. GOSIP compliant. If you need to specify the information to log for billing, * Press the Action Menu key to display the Action Menu window so you can select Message Elements for BillingorO/R Address Fields for Billing. To remove the Action Menu from the screen, * Select Help or Back to Main, or * Press Exit Menu. Logging the Billing Information Logging the billing information allows you to save information about a message that can be used to create a billing application. Fields that have both printable characters and T.61 format can log fields with printable characters, T.61 formatted fields, or both fields. Selecting Message Elements to Log for Billing. To specify the message elements to log, * Select Message Elements for Billing from the Configure Local MTA Action Menu. This displays the Message Elements to be Logged for Billing window. Mark each element that you want logged.Figure 6-2. Message Elements to Log for Billing Window The elements on the screen are: Originator address O/R address of the originator. If you select this field, you should select the O/R attributes to log. If you do not select any O/R attributes, the O/R address is not logged. Type of message The type of message. One of three values is logged: M for message, P for probe, and R for report. Message size The size of the message in bytes. Date Date the message was relayed in mm/dd/yy format where mm is the month, dd is the day, and yy is the year the message was relayed. Recipient address O/R address of the recipient. If you select this field, you should select the O/R attributes to log. If you do not select any O/R attributes, the O/R address is not logged. Content type The type of data in the message body. For example, 0 is logged for P0 or 2 is logged for P1. Time The time the message was relayed in hh:mm:ss format where hh is the hour, mm is the minute, and ss is the second the message was relayed. Priority The priority of the message. One of three values is logged: 0 for normal, 1 for non-urgent, or 2 for urgent. MPDU Identifier Domain Domain information associated with the unique information identifier of this message. MPDU Identifier Local Local information associated with the unique information identifier of this message. Non-Delivery MPDU Domain Domain information associated with the unique information identifier of the nondelivered message. Non-Delivery MPDU Local Local MTA information associated with the information unique identifier of the nondelivered message. Per recipient flag Level of report requested. Delivery Time The time the message was delivered in hh:mm:ss format where hh is the hour, mm is the minute, and ss is the second the message was delivered. Diagnostic The diagnostic code for non-delivery. Reason The reason code for non-delivery. Delivery Date The date the message was received in mm/dd/yy format where mm is the month, dd is the day, and yy is the year the message was received. When the fields on this window are correctly defined, * Press the Done key. * Press the Perform Task key. If you want the configured billing information to take effect immediately, you must stop and then restart the MTA. The information selected is logged in the bill file /usr/spool/x400/log/bill.log. Selecting O/R Address Fields to Log for Billing. To specify the O/R address fields to log, * Select O/R Address Fields for Billing from the Configure Local MTA Action Menu. This displays the O/R Address Fields to be Logged for Billing window.Figure 6-3. O/R Address Fields to Log for Billing Window
NOTE You must mark the Originator Address and/or Recipient Address elements in the Message Elements to Log for Billing window in order for any of these attributes to be logged.
The following is a list of O/R attributes that can be logged: Country Code ADMD PRMD Organization Name Organization Units 1-4 Surname Given Name Generational Qualifier Common Name Initials Terminal Id Network Address (X.121 address) Numeric User (UA identifier) Domain Defined Attributes 1-4 Physical Delivery Fields Country Code Physical Delivery Fields Service Name Physical Delivery Fields Postal Code When the fields on this window are correctly defined, * Press the Done key. * Press the Perform Task key. If you want the configured billing information to take effect immediately, you must stop and then restart the MTA. The information selected is logged in the bill file /usr/spool/x400/log/bill.log. Reading the Bill File. A C program /usr/lib/x400/ex_applic.c, allows you to view the logged billing information and is generated the first time you configure billing information and each time the billing configuration changes. To view the logged billing information, do the following: * Go to the /usr/lib/x400 directory: cd /usr/lib/x400 * If you are viewing the bill file for the first time, or if you have changed the billing configuration, compile ex_applic.c: cc ex_applic.c -o ex_applic * Run ex_applic: ex_applic < /usr/spool/x400/log/bill.log The billing information is printed to stdout.
![[]](../../pic3k/M011985/FFN143c50.gif)
![[]](../../pic3k/M011985/FFN153c50.gif)
![[]](../../pic3k/M011985/FFN163c50.gif)