CopiaFacts provides a number of different ways to prevent sending faxes or e-mails to specific numbers or addresses.  The original dBASE index look-up files are supported by all versions, and from CopiaFacts engine release 7.230 with F7DATABASE.DLL version 7.221, a wide range of standard databases are supported for looking up the items to be excluded.

For version 8, a new method of processing Do-Not-Send checking has been implemented in the Job Administration launcher, in FFBC, and for global Do-Not-Send files in the COPIAFACTS engine.  It is recommended that you should switch to use it if you have not already done so.

This look-up method uses a highly-optimized in-memory search. Of course, it might stretch a system which is already tight on virtual memory, but tests have shown that most do-not-send files take only tens of megabytes, and even if you have a do-not-send list of quarter of a million e-mail addresses, this should take less than 100MB in virtual memory, and will take only a few seconds to load. Look-up is then almost instantaneous and involves no disk access.  From CopiaFacts 8.1, this look-up method can also use a SQL database, but with some loss of efficiency.

All do-not-send look-ups are done on the original number as supplied on a the appropriate FS file command, before any additions or alterations made by phone-mask processing.  Non-numeric characters are stripped from the phone string before the look-up is done, as are characters following a vertical bar character (indicating that they are to be sent in-band after dialing).

Launch-time Do-Not-Send Checking

This method offers the following advantages for job administration and FFBC launches:

Multiple do-not-send files can be specified

Greater efficiency because the files are checked centrally during launch

Significantly reduced network load and contention by not checking index files from all lines/threads.

Earlier detection of matches, eliminating wasted processing such as document conversion.

The ability to specify white-lists of numbers to be excluded from checking for specific Job Administration clients

The ability to record a code with the index entry to report, for example, on the source of the entry

Customized outcome codes can be specified to be applied to matches from each list.

Automatic reloading of index files if they change.  Index files can be changed and updated without affecting look-up operations.

The launch-time Do-Not-Send checking for Job Administration and FFBC is described in the following section:

Launch-Time Do-Not-Send Checking

Global 'Pre-Loaded' Do-Not-Send Checking at Transmit Time

From release 8.037, the COPIAFACTS engine can also use a similar method of handling global do-not-send look-ups.  This has the following additional advantages:

The index files are loaded and held in memory at startup, and reloaded if the timestamp changes (but SQL look-up is now also supported).

Multilple look-up files are supported.

No network load for do-not-send look-up unless the file changes

Significantly reduced load on the engine thread that searches for processing tasks.

The configuration commands used for this method of global do-not-send checking are $dns_phone and $dns_email.  If you are using Job Administration to launch all your outbound transactions, you do not need to specify global do-not-send checking in COPIAFACTS as well.

Combining Launch-time and Transmit-time Checking

If you are a user of Job Administration, we recommend:

for global do-not-send look-up, use $dns_phone and $dns_email in SYSTEM.UJP

for per-client do-not-send look-up, use $dns_phone and $dns_email in OWNER.UJP (and whitelist commands if required to override the global look-up)

If you use FFBC to generate broadcasts, we recommend:

for global do-not-send look-up, use the configuration file versions of $dns_phone and $dns_email in FAXFACTS.CFG

for per-broadcast do-not-send look-up, use $dns_phone and $dns_email in the broadcast template file (and whitelist commands if required to override the global look-up)

If your system is not used for broadcasting, you will probably only have a global do-not-send requirement:

use the configuration file versions of $dns_phone and $dns_email in FAXFACTS.CFG

Legacy Do-Not-Send look-up

The do-not-send look-up used by earlier releases of CopiaFacts remains supported, but is not recommended for new applications.  Since CopiaFacts 8.062, the newer launch-time and pre-loaded look-up methods now support SQL and other database look-up, so there is no need for the older methods.

Legacy Do-Not-Send look-up can be done both globally and for specific user profiles (.USR) or broadcast jobs (.UJP).  When both global look-up and user-specific look-up are specified, a number or e-mail address will be excluded if it appears in either index.

If you use the newer methods of Do-Not-Send checking, you should disable Legacy Do-Not-Send checking as documented at the links below.

The following sections describe the different look-up operations that can be performed:

Global Do-Not-Send NDX look-up

Global Do-Not-Send database look-up

User-Specific Do-Not-Send NDX look-up

User-Specific Do-Not-Send database look-up

Do-Not-Send NDX look-up before broadcast launch

North-American Phone Number Handling

From CopiaFacts version 8.2, and for users in the North American Number Plan area, telephone numbers will be automatically adjusted so that they can ve checked with or without a leading '1' digit:  See the Telephone Number Formats topic.