| MAX_BAUD | [CV >C] A value (a valid multiple of 2400) assigned to this variable will limit the baud rate for the current fax outbound call. It overrides the $baud_max command in the CFG or USR file and has the same hardware limitations. It also overrides any Max Baud Action Code. You can use the 'variable group' feature to set this variable automatically for selected destination numbers, as shown in this example. See also STEPDOWN_BAUD |
| MBX_... | These variables must be pre-defined for use by the built-in MBX file. |
| MBX_APPLYGCT | The pathname of a GCT or GTT file used on an $apply_gct command. |
| MBX_MAILSTOP | The mail-stop items for a $mail_stop command |
| MBX_MSGDIR | The pathname for received faxes, for a $message_dir command. This value is double-expanded, see examples. |
| MBX_OFFSET | The offset for an applied GCT, for an $apply_gct command |
| MBX_PRPNAME | The name of a post-receive process, for a $post_receive command |
| MBX_PRPTYPE | The type of a post-receive process, for a $post_receive command |
| MIN_BAUD | [CV >C] A value (a valid multiple of 2400) assigned to this variable will limit the baud rate for the current fax outbound call. It overrides the $baud_min command in the CFG or USR file and has the same hardware limitations (including availability only for Dialogic, Diva and Brooktrout boards/ports). For Bladeware this option has to be set in the BladeWare Profile. |
| These variables are an exception to the rule that the longest possible variable name is always expanded. Variable expansions of the form @MEMOx are processed specially, and only an exact match is expanded. Thus if you have defined MEMO3 in an FS file, but have not defined MEMO30, then writing @MEMO30 in a cover sheet template file will not cause the value of MEMO3 followed by a zero to be expanded. This feature allows you to include a large number of @MEMOx expansions in a cover sheet template file, and have them correctly expand to blank if a smaller number of $var_def MEMOx commands have been created in the FS file by either FFCLIENT or another FS file generation program. |
| If you wish to word-wrap text in cover sheet MEMOx variables, see the topic describing cover sheets. |
| MONITOR_EVENT | [SRO] This variable contains the event description of an event from the MONITOR_LIST file. It is intended for use in the MQM_MESSAGE_TEXT variable value to identify the event. For more information, see Real-Time Status Monitoring. |
| MONITOR_LIST | [CV >C] This variable specifies the list of events to be monitored by means of messages to the $monitor_qname queue. For details of the syntax, see Real-Time Status Monitoring. |
| MQM_MESSAGE_TEXT | [CV >C] This variable controls the content of the message written to the queue specified by $monitor_qname. For more information, see Real-Time Status Monitoring. |
| MSMQ_FS_PRI | [CV >J] (no longer used, see $msmq_pri). |
| MSMQ_NOTIFY_PRI | [CV >J] (no longer used, see $msmq_pri). |
| MSMQ_PREPROC_PRI | [CV >J] (no longer used, see $msmq_pri). |
| [CV >J] When a column number or range (e.g. "1-8") is specified in this variable, each row of a job administration broadcast list will be examined to see if the column or columns have multiple entries separated by the delimiter character defined by MULTI_TARGET_DELIMITER (which defaults to comma). If so, they will all be combined to produce a set of entries and the row will be copied as many times as necessary, to create a row for each of the multiple entries. The principal use of this feature is to send an e-mail broadcast item to multiple recipients, but it can also be used for fax, voice and SMS broadcasts. |
| [CV >J] (See MULTI_TARGET_COLUMN) |
| MX_BREAK, MX_CONTINUE | [CV >E] See E-Mail error handling. |