Securing incoming and outgoing email

Incoming and outgoing emails use different security mechanisms as follows:

  • For validation, incoming email messages use security keys, the user's login and password, or the user's email address. If the email has at least one of these security mechanisms, Email Engine executes the appropriate action. You can configure Email Engineto use one or more of these methods; however, if the email message requests a modify action, MODIFY_KEY is required.
  • Outgoing email messages, which can include the results of query actions, use AR Systemaccess control for forms and fields. If a user does not have access to the field or form being queried, the field and its contents are not included in the outgoing email message.

Related topic

Configuring-Email-Engine-mailboxes


The topics listed in the following table provide instructions for creating security keys for incoming email, describe how security is handled for outgoing email, and provide instructions for configuring Email Engine to allow modify actions:

Action

Reference

Allow and secure modify actions through incoming emails.

Allow and secure modify actions through outgoing emails.

Validate permissions for incoming email requests with security keys.

Secure outgoing email content.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*