Files > DOMAIN

This file is used to name all of the domains to which MailMan messages may be routed. Each name in this file corresponds to the right side of a MailMan address-the part following the "@". Domains may have synonyms, allowing users to name sites with one name, while MailMan uses the more formal Domain Naming conventions. This file also controls whether messages are queued for immediate transmission and into what queue they are dropped. Any domain may have a relay domain, which controls the routing as follows: If a domain has a named relay domain, the message is put in the queue for the relay domain. If not, and the domain has a TRANSMISSION SCRIPT, then the message is put in the queue for that domain. Otherwise, the message is put in the queue for the Parent domain, as defined at MailMan initialization time.
.01name(+)0;1FREE TEXTBThis name is the exact name of the domain, as used in network addressing. It consists of "." (dot) pieces that are formed hierarchically starting at the right. Domains with dot pieces to the left are administered by the domain whose domain name consists of its name less the 1st dot piece. For example: A.DOMAIN.COM is administered by DOMAIN.COM. The domain name may be from 1 to 64 characters. Each dot piece may be up to 20 characters, and must begin with an alpha or numeric, and be composed of only alpha, numeric, or "-" characters.
1flags0;2FREE TEXTThe flags field controls the flow of messages to this domain from the local node. Flags are: S = Send. MailMan should start a TaskMan task to transmit the message as soon as the message is received. C = Close. MailMan will not allow users to address mail to this domain. Q or "" (the null string) = Queue. MailMan will not deliver until a task is explicitly created to deliver the mail. P = Poll. A TaskMan task will poll all domains with this flag. N = NO-forward. MailMan will not allow messages to be forwarded to this domain. T = Talkman enabled. The presence of this flag allows Talkman to be used at your site. It is also necessary to put a 'T' command into the script so that TalkMan will be invoked properly.
1.5security key0;11FREE TEXTThis field, if defined, names a security key which must be held by the sender. If the sender does not have this key, then he may not address this domain.
1.6validation number0;15NUMERICThis field is used for security. If filled in any messaging services that contact you will need to know the value of this field, or their requests will be ignored. Messaging services = other MailMan domains.
1.61new validation number0;18NUMERICThis field is used for security. It is a temporary value, it is set when a new validation number is negotiated with another Domain. It is moved to the Validation Number, field 1.6, after it is confirmed by the other Domain.
1.7disable turn command0;16BOOLEANy:YES
This field, if set to "YES", means that a remote domain calling this domain will not be able to execute the SMTP TURN command. This means that the sending domain must open the link. This allows an extra measure of security, to insure that the sending domain establishes the link.
2relay domain0;3POINTER4.2This is the name of the domain, if any, to which messages are to be always routed. For example, if traffic from Los Angeles to Washington is always to be routed through San Francisco, then the RELAY DOMAIN for Los Angeles is defined to be San Francisco. The relay domain overides any other path determination processes, such as scripts and parent domains.
4transmission script1;0MULTIPLE4.21See the Technical Description for how this field is used in implicit routing by the name server. This field should always have at least one Script command in it unless implicit routing is desirable. Each line of this text field is interpreted by the MailMan script processor. There are commands to be used: Open Device Wait Xecute Call These commands are described in other documentation.
4.2notes5;0WORD-PROCESSINGNETWORK NOTES should be used to document idiosyncracies which occur when communicating with the domain in question.
5synonym2;0MULTIPLE4.23Other names by which this domain is known.
5.5station0;13FREE TEXTThis is the domain's station.
6mcts routing indicator0;4FREE TEXTThis is a three character routing indicator for the VADATS network's MCTS terminal system. statistics reflect the messages as they are actually transmitted, not as they are addressed.
6.2dhcp routing indicator0;14FREE TEXTADThis field is used to route messages when they arrive at the central data collection point at the domain FOC-AUSTIN.DOMAIN.EXT.
6.5mailman host0;12FREE TEXTThis field contains a logical or physical address of a remote domain so that a connection can occur.
6.6ftp blob ip addressIP;1FREE TEXTThis field contains the IP address of this host so that it can be used as the to address for files that will be sent to this domain.
6.61tcp/ip poll flagP;1SET OF CODES0:DO NOT POLL
DThis is the information needed to log in the FTP service of this site if the standard route needs to be overridden. . This field is required. Set the value of it to zero ("0" Do Not Poll) unless you know that you are using the XMRTCP TCP/IP poller.
6.62ftp3;1FREE TEXTThis is the information needed by to log into an FTP service to send files. It is overridden by the site if they wish in their Kernel Site Parameters and sent to the sender in real time. There are really two pieces of data in this field separated by a ";". Piece number 1 is the username. Piece number 2 is the password.
6.7ftp blob directoryFTP-DIR;1FREE TEXTThis field contains the directory into which a file should be put by a domain sending it files to attach to multimedia messages.
7*outgoing message count0;5NUMERICThis is a count of the number of messages which have been transmitted to this domain since the counter was last set to zero. As of Kernel 7 this field was *'d and it will be deleted 18 month from the date that the community was notified (6/5/90).
8*outgoing line count0;6NUMERICThis is a count of the number of lines of text which have been transmitted to this domain since the counter was last set to zero. SEE FIELD 7 ABOUT '*'.
9*incoming message count0;7NUMERICThis is a count of the number of messages which have been received from this domain since the counter was last reset. SEE FIELD 7 ABOUT '*'.
10*incoming line count0;8NUMERICThis is the count of the number of lines which have been received from this domain since the counter was last reset. SEE FIELD 7 ABOUT '*'.
11*error last reported0;9DATE-TIMEThis is the date/time at which a physical link error was last reported to the network log device. This timestamp is checked by the error reporting programs to insure that too many error messages are not sent. SEE FIELD 7 ABOUT '*'.
12*number of recoverable errors0;10NUMERICThis is a count of the number of recoverable errors which have occurred while sending or receiving messages to or from this domain, since the counter was last set to zero. Recoverable errors are errors which are detected by checksums, etc, which require retransmission of the line. SEE FIELD 7 ABOUT '*'.
13*progress report3;1FREE TEXTThis field contains the time (in $H format) of the last time a queue dump routine reported its progress. If this field is undefined, or more than 5 minutes old, then the queue is assumed to be inactive. If not, then the MESSAGE IN TRANSIT and LAST LINE TRANSMITTED fields indicate the current status of the queue transmission. SEE FIELD 7 ABOUT '*'.
14*message in transit3;2NUMERICIf this field exists, it indicates the message number of message currently being transmitted. SEE FIELD 7 ABOUT '*'.
15*line last transmitted3;3NUMERICIf this field exists, it indicates the line number of the MESSAGE IN TRANSIT which was sent just prior to the last PROGRESS REPORT. SEE FIELD 7 ABOUT '*'.
15.4*errors this transmission3;4NUMERICNumber of "soft" errors (non-fatal) that have been encountered during the course of the current transmission. This is the total number of soft errors encountered during entire transmission. SEE FIELD 7 ABOUT '*'.
15.5*rate of transmission3;5NUMERICTransmission rate (in seconds) since the posting of the last progress report. This number is based on the number of lines trasmitted since the last progress report and the number of seconds since the last progress report. SEE FIELD 7 ABOUT '*'.
15.6*characters rec'd3;8NUMERICThis is the number of characters received during the current process and is for the current message. SEE FIELD 7 ABOUT '*'.
15.7*characters sent3;9NUMERICThis is the number of characters in the current message that have been sent so far. SEE FIELD 7 ABOUT '*'.
16poll list4;0MULTIPLE4.24If this domain belongs to a poll list, then it will be activated when a background poller is activated to send mail to this list.
17physical link device0;17FREE TEXTThis field is used for network mail ONLY. If there is no device named in field 1.3 of the TRANSMISSION SCRIPT, then this device is used. If no device is named in this field, then the device named in field 8.25 of file 4.3 is used. If there's no device named in that field, then there is no device. If this domain has a physical link such as a miniengine port, a direct line to another cpu, a modem, etc., this port should be named in this field to direct network mail to the proper output device. There must be an entry in the DEVICE file for this cpu port. The name field of the DEVICE file can be a literal (such as MINIENGINE-OUT or CPU B LINK) but the $I field must match with the correct cpu $I. If the link is physically located on a cpu other than the one the network mail is being sent from, the local DEVICE file MUST reflect that in the OTHER CPU field of the device file if the transmission is to take place immediately. If it is not identified properly, the message will go into a queue to be processed the next time a network message is sent from or recieved on the processor with the physical link. NOTE: The DEVICE files on all cpu's must have matching device names to correctly route the message to the proper cpu for sending.
20level 1 nameCOMPUTEDThe most right "." piece of a domain name ($P(domain-name,".",$L(domain-name,"."))
21level 2 nameCOMPUTED$P(domain-name,".",$L(domain-name,".")-1)
22level 3 nameCOMPUTED$P(domain-name,".",$L(domain-name,".")-2)
23level 4 nameCOMPUTED$P(domain-name,".",$L(domain-name,".")-3)
24*network device3;6FREE TEXTSEE FIELD 7 ABOUT '*'.
25*transmission task#3;7NUMERICThe transmission task# points to the TaskMan task that has been generated to handle delivery of messages to the domain in background. SEE FIELD 7 ABOUT '*'.
50directory requests flag50;1NUMERICAEThis field controls whether or not the XMMGR-DIRECTORY-ALL option will send a message requesting the user directory for the domain. If the value is null or zero, no request will be made. If the value is a positive integer, a request will be made at the same time as other domains with the same number in this field are made. A task must be set up and scheduled for each number assigned using the XMDIR-REQUEST-ALL option, which is then run every 90 days (or according to what you change the reschedule value to).
100*message statistics month100;0WORD-PROCESSINGMessage statistics are collected by month. SEE FIELD 7 ABOUT '*'

Referenced by 29 types

  1. INSTITUTION (4) -- domain
  2. DOMAIN (4.2) -- relay domain
  3. MESSAGE STATISTICS (4.2999) -- name
  4. MAILMAN SITE PARAMETERS (4.3) -- domain name, parent
  5. FOUNDATIONS SITE PARAMETERS (18.01) -- domain name
  6. INTERIM REPORTS (64.6) -- domain name
  7. BORROWERS/FILE AREAS (195.9) -- domain file pointer
  8. AR TRANSMISSION RECORDS (349) -- remote domain
  9. AR TRANSMISSION TYPE (349.1) -- remote domain
  10. AR TRANSMISSION SEGMENTS (349.9) -- domain
  11. *PDX PARAMETER (394.2) -- pdx domain
  12. VAQ - PARAMETER (394.81) -- domain
  13. VAQ - RELEASE GROUP (394.82) -- remote domain
  14. 2507 REQUEST (396.3) -- owner domain
  15. 2507 EXAM (396.4) -- transferred out to
  16. CMOP SYSTEM (550) -- cmop domain
  17. CMOP NATIONAL SITE (552) -- facility domain
  18. LIBRARY TRANSACTIONS (682.1) -- to station
  19. OBS (704.117) -- facility_id
  20. EEO SERVER PARAMETERS (789.5) -- domain
  22. HL LOGICAL LINK (870) -- mailman domain
  23. ENG INIT PARAMETERS (6910) -- project planning rollup domain, project tracking rollup domain
  24. NOIS LOCATION (7105.1) -- domain
  25. KERNEL SYSTEM PARAMETERS (8989.3) -- domain name
  26. PARAMETERS (8989.5) -- entity
  27. RPC BROKER SITE PARAMETERS (8994.1) -- domain name
  28. VAMC NETWORK HEALTH EXCHANGE (537000) -- requesting place