Kerio Tech Version 6.5.2 - Manual (Page 278)

Chapter 6 Kerio Outlook Connector (Offline Edition)
278
Send notification
Sends notification (i.e. a short text message) to a specified address, typically to a cel-
lular phone. It is necessary to define even cellular phones by email addresses, for
example [email protected].
The following macros can be used in the message text:
• $from$ — the notification will show the message sender or the address contained
in the From field.
• $from-name$ — the notification will show the name of the message sender.
• $subject$ — the notification will show the message subject.
• $text$ — the notification will show the message text. Only the first 128 char-
acters will be displayed. To reduce the number of displayed characters, edit the
macro as follows: $text[50]$ (the number in brackets represents the maximum
number of characters displayed in the notification).
Send autoreply
The automatic reply with a specified text. The automatic reply will be sent to each
sender’s address only once a week (so that the automatic reply does not create a loop
in case there is an automatic reply set at the other end).
Stop processing more rules
If the message complies with this rule, no more rules will be processed. Using this
function a user can create more complex rule systems for individual condition types.
Rules are tested rule by rule from the top downwards.
Note: Notifications and autoreplies are protected against looping. This means that the
system does not send a notification in reply to received notification or automatic replies.
The detection of notification or automatic replies is performed using special items in the
message header. Only notifications and automatic replies generated by Kerio MailServer
are detected.
3. Rule description — description of the rule function (it is generated automatically accord-
ing to the rule definition). Highlighted entries are interactive — click them to set other
parameters.
Click on the Options button to open the Rule Condition Options dialog — see above.
is
The entry must exactly match with the specification.
is not
The entry must not match with the specification.
contains
The entry must contain the (sub)string.