Implementing Policy › Email Administration › Artifact Protection and Security

Artifact Protection and Security

You use artifacts to protect mail delivery to a mailbox in the following ways:

• Use the ARTIFACT keyword in notifications and notification phrases.

  Note: The artifact security level must match the mailbox rule Minimum Artifact Type setting for the mailbox to which the email is sent. Types that are more secure than what is set are allowed. In other words, if you set ARTIFACT=PROTECTED, then both PROTECTED and SECURE are allowed, but NONE is not allowed.

• Set the Minimum Artifact Type option in the Mailbox Rule Detail.

You can embed an artifact in a notification phrase and specify the security level for the artifact, for example:

%REQUEST=@{ARTIFACT=PROTECTED:call_req_id.ref_num}%

Note: For more information about the tables for the Minimum Artifact Type option (filter_min_artifact_type) and the Mailbox Rule Detail (usp_mailbox_rule table), see the Technical Reference Guide.

Example: No Validation of Artifacts

The following example shows no ARTIFACT format. No validation of artifacts can be performed.

Usage: %REQUEST=@{call_req_id.ref_num}%

Example: %REQUEST=1234%

Example: No Validation of Artifacts

The following example shows the ARTIFACT=NONE format. ARTIFACT=NONE is the same as not adding the keyword; no validation of artifacts can be performed.

Usage: %REQUEST=@{ARTIFACT=NONE:call_req_id.ref_num}%

Example: %REQUEST=1234%

Example: Validate a Ticket Number Against the Hash for Confirmation

The following example shows the ARTIFACT=PROTECTED format. The PROTECTED format validates a ticket against the hash for confirmation. The letter "A" denotes the type of formatting. Commas separate "A", the hash code, and the ticket number.

Usage: %REQUEST=@{ARTIFACT=PROTECTED:call_req_id.ref_num}%

Example: %REQUEST=A,12345678,1234%

Example: Encrypt the Ticket Number

The following example shows the ARTIFACT=SECURE format. The SECURE format encrypts the ref_num, and then encodes the result in Base64 encoding so it can safely be included in the message text. The letter "B" denotes the type of formatting. Commas separate "B" and a password encrypted ticket number.

Usage: %REQUEST=@{ARTIFACT=SECURE:call_req_id.ref_num}%

Example: %REQUEST=B,da1jhr+9U5GVfd2VGH4dsnx2+PaSvygDS2e3IqjpjtyNSDW2u/KNPX61nopDu/KB%