Each e-mail FS file results in a transmission to a single recipient. However it is possible to send CopiaFacts e-mail which appears to each recipient to have been sent to other people also. The basic (manual) method of doing this is to set the variables EMAILTO_LIST or EMAILCC_LIST to with values containing one or more e-mail addresses.

Suppose you want to send an e-mail to steve@copia.com, with copies to terry@copia.com and tim@copia.com.  You would need to create three FS files, one for each actual recipient, named on an $email_address command; and use the variables to override the To: header and add a Cc: header:

$email_address steve@copia.com

$var_def EMAILTO_LIST "steve@copia.com"

$var_def EMAILCC_LIST "terry@copia.com,tim@copia.com"

...

$email_address terry@copia.com

$var_def EMAILTO_LIST "steve@copia.com"

$var_def EMAILCC_LIST "terry@copia.com,tim@copia.com"

...

$email_address tim@copia.com

$var_def EMAILTO_LIST "steve@copia.com"

$var_def EMAILCC_LIST "terry@copia.com,tim@copia.com"

...

CopiaFacts will then send three separate e-mails to the three specified recipients, but each one will see the correct distribution list.  If you need to send a BCC e-mail, you can also create an FS file with an $email_address recipient who is not named in the TO or CC lists.

Remember that simply adding e-mail addresses into the EMAILTO_LIST and EMAILCC_LIST variables does not result in extra e-mails being sent.

The separator between multiple addresses in these variables defaults to a comma, but can be overridden by assigning a different character to MULTI_TARGET_DELIMITER.  The e-mail header will always be written with comma separators.

You must ensure that the chosen delimiter character does not appear in any of the e-mail addresses, even inside a quoted string.  For this reason it is best to use simple e-mail addresses, without display-name or comment elements (as defined in RFC5322).

Multiple recipients in Job Administration broadcasts

You can include multiple recipients in a broadcast by putting multiple recipient addresses, separated by commas, in a list column or a group of adjacent columns, in a single list row.  You must specify that the list is to be used in this way by specifying the column number or range in the MULTI_TARGET_COLUMN variable.  Note that the list column separator should not be the same as the multiple-recipient separator: you would typically use a tab-separated-value list, with a one or more fields containing comma-separated addresses.

At job launch time the launcher replicates the list row as necessary, with any other fields on the same row being used for all recipients named on the row.  This example list has two rows, each with a single column, but results in five e-mails being sent:

steve@copia.com,tim@copia.com

terry@copia.com,dorothy@copia.com,vanessa@copia.com

The default is that the first item is taken to be the 'to' item, and the remainder are 'cc' items.  You can override this by adding dummy addresses of 'to', 'cc' or 'bcc' in the set, separated by the same delimiter.  The following list row is also valid:

terry@copia.com,cc,dorothy@copia.com,bcc,vanessa@copia.com

Addresses preceding the first 'to', 'cc' or 'bcc' directive are always considered to be first the 'to' address and then 'cc' addresses. Then addresses following a directive are categorized by the closest preceding directive.  If the set starts with 'cc' or 'bcc' and there is no later 'to' entry, the 'to' address will show the actual destination of each e-mail.

Again, the separator between multiple addresses in these variables defaults to a comma, but can be overridden by assigning a different character to MULTI_TARGET_DELIMITER.

E-Mail addresses may consist of a complex string, rather than just a@b, for example: "Steve Hersee" <steve@copia.com>, but you should ensure that the quoted string does not contain the chosen delimiter character.

The broadcast launcher generates FS files with the appropriate EMAILTO_LIST and EMAILCC_LIST variables.  Obviously, there is no need for a BCC list, because these addresses are not published in the resulting e-mails.

Note that MULTI_TARGET_COLUMN can also be specified for fax, voice or SMS broadcasts, in which case the values will be taken to be telephone numbers and no TO, CC, or BCC processing is done.  For combined (FEB1 or SEB1) broadcasts, the presence of an @ anywhere in the set is taken as a signal that the whole set will contain e-mail addresses.  You cannot use this feature to combine phone numbers with e-mail addresses.

The job launcher can either accept the whole set of addresses in a single column, or can also handle lists with the primary recipient in one column and separate columns containing any cc items.  To specify a range of columns in the variable MULTI_TARGET_COLUMN, use a value such as "1-8", which will treat columns 1 to 8 as containing first the To: address and then from 1 to 7 cc addresses.  Effectively the multiple target string will be built from all the entries in a group of adjacent columns.  It is valid for a row to contain fewer columns than the range specifies.

The BCFx variable, where x is the first or only column in a multi-target set, will be modified to contain only the actual destination of the FS.  The other BCF variables of the multi-target set, if any, will contain the normal field content.