E-Mail Do-Not-Send Checking
This command is used to specify a global do-not-send look-up file which is pre-loaded by the COPIAFACTS engine. If you include this command in your FAXFACTS.CFG file, the use of the legacy files DNS_MAIL.NDX and DNS_DOMN.NDX will be suppressed, but legacy files named on a DNS_MAIL_PATH or DNS_DOMN_PATH configuration file variable will still be used, with a warning message on startup.
Job Administration users should not normally use this command: instead use $dns_email commands in SYSTEM.UJP to perform global do-not-send checking at launch time.
Multiple commands may be supplied. The advantages of pre-loading the do-not-send lists are described in the Configuration topic.
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|
|The timestamp of the file will be checked each time a fresh scan of the TOSEND folders is started (typically every 20 seconds) and the file will be reloaded if it has changed.|
|code||A code which will be used to override the default failure outcome code for matched items. In a 'combined' index/list, the supplied code will be incremented by one for domain-name matches. The default values are 189 for e-mail address matches and 190 for domain matches. The code range 200-249 is suggested for custom outcome codes. If you use the override outcome code on the command, failed items will NOT be protected from accidental transmission if you ignore the warning and enter 'Z' on the JOBADMIN Resubmit Fail dialog.|
|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 DNS_DATA code in a loaded TXT list.|
Items matched in a $whitelist_email specification at launch time (in Job Administration or by FFBC) will not be checked.
The NDX file may contain a positive numeric data value for each entry, and 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). If present and greater than one the value will be saved as the value of a variable named DNS_DATA in the launched FS file.
When multiple commands are specified, items will be checked in the order in which they appear in the file. The outcome code reported will be that of the file in which the item was first matched, if specified.
Default: No transmit-time checking, or only legacy checking will be performed.
$dns_email @FFBASE\dnsemail.ndx 200