E-Mail Special Action Specification
This command is used to specify a list file which is loaded at launch time, to specify special actions to be performed for specific e-mail addresses or domains. The command may also be placed in an FS Template file (.FST) for use in an FFBC launch. Multiple commands may be supplied to arrange for different types of action, and commands from System, Owner and Jobtype UJP files migrate to the job instance properties in the usual way.
|The same pathname should only be used once in a set of lookup files.|
For more information, see Destination-Specific Processing.
The parameters on this command are used as follows:
|pathname||The pathname of the look-up file to be used. Currently supported file extensions are:|
|.NDX||a character-mode index file created and maintained by the PIN utility.|
|.TXT||a list of entries to be matched|
|databasespec||The components of the database specifier are separated by the vertical bar symbol (|) and are described in more detail in the description of the do-not-send feature.|
|Database Name||The full pathname of a supported database, or a DSN source|
|Table Name||The name of the table to use (default table name: DNS)|
|Key Field Name||The name of the key field to use (default key field RECIPIENT)|
|Timeout Value||Timeout for look-up (defaults to ADO default value)|
|Data Field Name||The name of the data field to use from the matched entry.|
|code||A code which will be used as the default numeric action code for matched items. In a 'combined' index/list, the supplied code will be incremented by one for domain-name matches. If not supplied, only the action code from the list will be returned.|
|domain||A keyword which indicates that the index/list contains only domain names to be matched|
|combined||A keyword which indicates that the index/list contains both e-mail addresses and domain names|
|EmptyOK||A keyword which indicates that the index/list may be empty. This suppresses the check that ensures that at least one entry has been loaded from the file. Failure to load any entries could be a symptom of a corrupted file.|
|WSDelim||A keyword which indicates that any number of white spaces may separate the phone number and the action code in a loaded TXT list.|
The NDX file may contain a positive numeric data value for each entry, the TXT file may contain a positive numeric data value separated from the address/domain entry by a single TAB character (or any whitespace, if WSDelim is used), and the database data field may also contain a numeric value. If present, this will override the default numeric action code.
The action codes from the list(s) in which the item is matched will be returned, separated by semi-colons, in the ACTION_CODES variable in the FS file. Action codes less than 1000 are reserved for system use, and it is recommended that only 4-digit codes are used for user applications.
A domain matched in two lists might acquire a variable definition in the FS as follows:
$var_def ACTION_CODES "1234;2041"
The pre-process commands used to perform the appropriate actions would then be:
$if 1234 $in @ACTION_CODES
$if 2041 $in @ACTION_CODES