A rule is composed by a set of conditions and a set of actions that will be
applied to an incoming message. From the General tab of the Incoming
Messages properties, click on Add to create a new rule:
Conditions:
You can add as many conditions as needed. If no condition are entered, all
actions will be executed.
Possible conditions are:
Find values in the message body: Search for one or more text values in the message body. If the message
contains an html part and an alternative text part, the search will be
performed in the html part only.
Find values in the subject: Search for one or more text values in the message subject.
Find values in a header field Search for one or more text values in a header field. (header fields
examples are available in the Knowledge Base - Header Fields)
Find values in the To, Cc or From field: Search for one or more text values in the To, CC or From field.
Find values in a body field: Search for one or more text values in a body field. A field in a message body is represented by the following format: "field name: field value".
If the field value is on multiple lines, it must be between quotes (for more details, see the Webforms Sample).
Check the message date: Check if the message sent date is included a specified interval.
Check the message size: Check if the message size is included in a specified interval.
Check the message priority: Check the message priority for a specified value. I the priority is not
set, the default message priority is set to 'Normal' priority.
Delivery Status Notification (aka Bounces):
Check -> if the message is a DSN or not.
-> the DSN Type (Failure, Success, Delayed, etc.).
-> the DSN Status
Code (the reason why you receive a DSN): 4.*.* (Temporary failure or soft bounce), 5.*.* (Permanent
failure or hard bounce), 5.1.* (Address Error). You are also able to fill in
any other status codes. To have a full list of the status codes used by the
DSN, see the Knowledge Base.
In order to read more on how to manage DSNs / Bounces with eMill, see the Knowledge Base.
Received date and time schedule: Check to see if the message is received on specific day(s) and hour(s)
of a week.
The record exists in
a data source: The condition is verified if one or more records are found in a data
source. Search is performed by comparing one or more values. Compared values
are either a constant or a from the message header (e.g. the 'From' field).
The record does not exists in the data source : Does the opposite of the above condition.
The message is digitally signed or encrypted: Check if the message is digitally signed or encrypted (see
S/MIME).
The message is an unsubscribe request: Check if the message is
an unsubscribe request from a receiver sent by using your message
unsubscribe link (see Using the Editor for HTML).
Actions:
A rule must have at least one action to execute if the condition as verified.
Possible actions are:
Redirect the message:
Redirects the message to one or more recipients. The message body or subject
is not altered in anyway. The redirected message is placed in the Outbox
folder until it is sent.
Move the message to a folder: Moves the message from the Inbox folder to any sub folder.
Reply to the message:
Creates a new message in reply to the received message. The newly created
message is placed in the Outbox. The response can be a text or a message
template (.eml file). The text can include AMS code (VBScript).
Add a text to the project log :
Appends some text to the project log. This action can be used for debugging
and reporting purpose.
Add a record to a data source: Adds a record to the receivers list, the black list or any other data
source. Record values may be set with constants or fields that are extracted
from the received message (e.g. From field, etc.)
Update a record in a data source: Modifies one or more records in the receivers list, the black list or
any other data source. Records are searched the same way as the The record exists in
a data sourcecondition. Fields can be set with constants, values
extracted from the received message, and for numerical values, they can be
incremented or decremented.
Delete a record from a data source: Remove one or more records the the receivers list, black list or any
other data source. Records are searched the same way as the The record exists in
a data sourcecondition.
Delete the message: Deletes the received message
Save sender certificate to receiver certificate store: If you want to send encrypted messages using the S/MIME protocol, you
need the receiver public key. This action saves the public key included in
the incoming message in your certificate store. Thus, you will be able to
send encrypted messages to this receiver in your future campaigns.
Call a web page: Lets you run actions on an external web application. If the access to
the web application requires an authentication, enter the account user name
and password.
Stop processing rules:
This prevents other rules from executing, it does not prevent other actions
in the current rule to be executed.