Specifying Multiple Email Addresses

When creating a schedule or Distribution List, you can specify multiple email addresses within a single field, row, or record.

When creating a schedule or Distribution List, you can separate each email address with a comma (,) or a semicolon (;).

The multiple email addresses will appear in the To line of a single email when the scheduled output is distributed.

Note:

To distribute separate emails for each address, specify the email addresses on separate lines within the Distribution List.
In the Allowed Email Domains and Addresses dialog box in the ReportCaster Console, if the Restrict user input with this list check box has been selected, user input of email addresses is restricted to a list of allowed email domains and addresses. For more information, see Validating Allowed Email Domains and Addresses.

Example: Specifying Multiple Burst Email Addresses

If you are using the default configuration (Packet Email = YES), one email is distributed for multiple burst values specified for the same email address. The email address values specified on each row are treated as a string that is a key. If there are multiple rows with the same address value (key), one email is distributed with all the burst values. For example, consider the following Distribution List:

Burst Value Address

A            user1@abcd.com;user2@abcd.com
B            user1@abcd.com
C            user1@abcd.com

In this example, user1@abcd.com receives two emails when the scheduled output is distributed. In the first email, user1@abcd.com; user2@abcd.com appears in the email To line and one attachment is distributed for burst value A. In the second email, user1@abcd.com appears in the To line and two attachments are distributed, one for burst value B and one for burst value C.

If you are using the configuration that specifies to distribute a single email for each row (Packet Email = NO), then the following behavior occurs for our example. Three separate emails are distributed. In the first email, user1@abcd.com; user2@abcd.com appears on the To line and one attachment is distributed for burst value A. The second email is sent to user1@abcd.com with one attachment for burst value B. The third email is sent to user1@abcd.com with one attachment for burst value C.

If a schedule has multiple tasks and Packet Email = BURST, then for each burst value the output of all of the tasks is combined and distributed. In our example, three separate emails are distributed. In the first email, user1@abcd.com; user2@abcd.com appears on the To line and all output from the multiple tasks for burst value A are distributed. The second email is sent to user1@abcd.com with all output from all tasks for burst value B. The third email is sent to user1@abcd.com with all output from all tasks for burst value C.

Another consideration is when using the default configuration (Packet Email = YES) and the same burst value is specified multiple times for the same Address (key) value. For example, consider the following Distribution List:

Burst Value Address

A          user1@abcd.com;user2@abcd.com
B          user1@abcd.com
B          user1@abcd.com

In this Distribution List, only two emails are distributed for user1@abcd.com. In the first email, user1@abcd.com; user2@abcd.com appears in the To line and the attachment is for burst value A. In the second email, user1@abcd.com appears in the To line and the attachment is for burst value B. The third row in the Distribution List is ignored since it contains the same key and the same burst value, B, as the second row.

As a best practice, be sure to review your distribution information to make sure you have not duplicated the same burst and address value pairs.

Example: Specifying Multiple Non-Burst Email Addresses

Consider the following sample Distribution List, which does not contain burst values:

Address

user1@abcd.com;user2@abcd.com

user1@abcd.com

user2@abcd.com

user3@abcd.com

user1@abcd.com;user2@abcd.com;user3@abcd.com

In this Distribution List, an email is distributed for each address line regardless of whether Packet Email is set to YES or NO. This is because each address value is unique. For the first email, user1@abcd.com; user2@abcd.com appears in the To line and the attachment is for the full report output from a scheduled report procedure (FEX). The second email is distributed to user1@abcd.com, and so on.

If one of the address lines is repeated in the Distribution List (for example, if user3@abcd.com is added as the sixth line in the example Distribution List), the behavior would work as follows. If Packet Email = YES, only one email is distributed for user3@abcd.com. However, if Packet Email = NO, two separate emails are distributed to user3@abcd.com.