# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | name(+) | 0;1 | POINTER | 4.2 | B | Domain for which network mail transmission information is collected. |
1 | progress report | 3;1 | FREE TEXT | This field contains the time in $H format of the last time a queue dump routine reported its progress. If this field is undefined, or 'old', then the queue is assumed to be inactive. If not, the rest of the fields on this node indicate the status of the transmission. | ||
2 | message in transit | 3;2 | POINTER | 3.9 | This points to the 3.9 (Message) file entry of the message being transmitted. | |
3 | line last transmitted | 3;3 | NUMERIC | This is the line number of the message in transit. | ||
4 | errors this transmission | 3;4 | NUMERIC | This is the number of "soft" errors (non-fatal) that have been encountered during the course of the entire current transmission. | ||
5 | rate of transmission | 3;5 | NUMERIC | This is the transmission rate in characters per second for the current transmission. It may be for a single line or for a block or for the entire message. It is updated regularly during the transmission. | ||
6 | network device | 3;6 | FREE TEXT | This is the name of the device (system name) that the transmission is running on. It may be incoming or outgoing. | ||
8 | direction | 3;8 | SET OF CODES | S:SENDING R:RECEIVING | This field is used to report whether, at any given time, we are sending messages to, or receiving messages from, the site. | |
25 | transmission task# | 3;7 | NUMERIC | The transmission task# points to the TaskMan task that has been generated to handle delivery of messages to the domain in background. | ||
41 | xmit start date/time | 4;1 | DATE-TIME | This field helps MailMan determine, after a fatal error, whether to start the transmission process at script 1, try 1, or to start it elsewhere. | ||
42 | xmit finish date/time | 4;2 | DATE-TIME | This may be useful information for debugging purposes. | ||
43 | xmit script | 4;3 | NUMERIC | This tells MailMan which script is/was being used. | ||
44 | xmit tries | 4;4 | NUMERIC | This tells MailMan how many tries have been made with the current script. | ||
45 | xmit latest try date/time | 4;5 | DATE-TIME | This may be useful information for debugging purposes. | ||
46 | xmit script cycle iterations | 4;6 | NUMERIC | This is the number of script cycles we have tried. This field starts off at 0. After we have tried all the scripts available, we bump up this field by 1. | ||
47 | xmit first script | 4;7 | NUMERIC | This field notes which script has the highest priority, that is, which script was tried first. | ||
48 | xmit ip addresses tried | 4;8 | FREE TEXT | This is a list of IP addresses, separated by commas, which have already been used in attempting to connect with the site. We use this list in conjunction with the DNS server, which returns a list of valid addresses to try. Using both lists, we can come up with the next IP address to try. | ||
51 | xmit script record | 5;E1,245 | FREE TEXT | This is a copy of the zeronode of the latest script used. | ||
60 | xmit audit | 6;0 | MULTIPLE | 4.29992 | This multiple contains an audit of the attempts that have been made during this transmission. | |
101 | message statistics month | 100;0 | MULTIPLE | 4.29991 | Message statistics are summed into this area at the end of each successful message received or sent into the appropriate month according to the time the message is received. |
Not Referenced