# | Name | Location | Type | Details | Index | Description |
---|---|---|---|---|---|---|
.01 | transmission script | 0;1 | FREE TEXT | B | This is the name of the transmission script. | |
1 | priority | 0;2 | NUMERIC | AC | This field is used by MailMan to decide which script to play when trying to transmit messages in background. The higher the number the lower the priority for being chosen. See also the Number of Attempts field. When MailMan is transmitting using the TCP/IP Poller (XMRTCP), it assumes that there is only one possible TCP/IP connection per domain and does not look for multiple scripts to roll over to. This field is only operable for SMTP type scripts (using standard asynchronous WAN connections). PRIORITIES can go from 0 to 9999 where 0 is the highest and 9999 is the lowest. If the field has no value, 9999 is assumed. | |
1.1 | number of attempts | 0;3 | NUMERIC | MailMan tests against this field to determine how many times it should try a particular protocol before giving up and trying the next one. This field is used in conjunction with the Priority field. When the the Number of tries to transmit the messages in the queue exceeds the value of this field, a Transmission Failure bulletin is sent to the Postmaster. This field is only active with the SMTP type of transmission script. | ||
1.2 | type | 0;4 | SET OF CODES | FTP:File Transfer Protocol SMTP:Simple Mail Transfer Protocol TELNET:Interactive / TalkMan TCPCHAN:TCP/IP Channel OTHER:OTHER | Each transmission script must be given a type so that it can be handled properly. asynchronous connections on the WAN are of the type IDCU. These scripts may compete with each other according to their priorities (See the PRIORITY field). Scripts that use TCP/IP channels should be marked with the type TCPCHAN so that they are ignored during prioritization unless the TCP/IP enabled CPUs have Task Manager running on them, in which case they should be made SMTP type. In other words, if the physical link is on a CPU that Task Manager runs on the transmission script can be of the type SMTP. If it is not on such a CPU another type must be chosen. Other types are TELNET (used for TalkMan or other interactive scripts), FTP (for File Transfers) and Other. | |
1.3 | physical link / device | 0;5 | FREE TEXT | The physical link is the channel that the transmission will take place on. This field is always a free text pointer to the device file. See field 17 / Physical Link Device for more information. | ||
1.4 | network address (mailman host) | 0;6 | FREE TEXT | The network address is that identifier that, used appropriately on the physical link, allows specification of the system to be contacted. | ||
1.5 | out of service | 0;7 | SET OF CODES | 0:in service 1:out of service | This is the preferred field to set to take a script out of service, to prevent it from being used. | |
2 | text | 1;0 | WORD-PROCESSING | This is the text of the script. See description above. | ||
99 | transmission script notes | NOTES;0 | WORD-PROCESSING | Keep notes that are important for systems management here. |
Error: Invalid Global File Type: 4.21