Forward

Optional

This action causes a completely new message to be created which contains the entire contents of the original message. When the recipient receives the forwarded message, it will appear as though the sender is the Praetor administrator.

By clicking on this address in the Rule Description box you will be presented with the following form where you may complete the destination address, subject keyword, and message text. At a minimum you must provide a destination address in the normal SMTP address format.

Note:

While the above Forward Message to Address window allows for only a single SMTP address to be entered, using an address that represents an Exchange or Domino distribution group will allow multiple recipients to get a copy of the forwarded message.

The entry for the field Append Keyword will be appended to the subject line, which will have the form as shown below from the above example.

Fwd: <original-subject-text> [Found Profanity]

When you have completed this form, press OK to return to the previous screen with the forwarding destination address visible.

Note:

In general you need to exercise some caution when you use an auto-forward mechanism. This doesn't apply directly to Praetor because the Forwarded message it generates has the administrator's email address as the sender. We have received calls from customers to our technical support thinking Praetor is involved in a problem of message loops.

In the cases we have seen, the loop is caused when an Outlook user creates a rule to automatically forward all arriving messages to a mail account on some free email service like hotmail.com or yahoo.com. What they forget is that the free email inbox has some storage limit. Once the limit is reached, no more email can be received and the hotmail or yahoo mail server will send a non-delivery report (NDR) containing the original message back to that very same user. Of course with the user's Outlook auto-forwarding rule still in place, the NDR gets forwarded to the full inbox on that free service, creating the loop.

The best way to prevent such a loop is to educate the users. They need to include an exception with the Outlook auto-forward rule. The exception is to test for NDR from the postmaster address at their email service.

The situation described above specifically deals with Outlook users who have created an auto-forward rule. It would apply to any similar auto-forward capability with a different desktop email client software to an email service with size limits that causes an NDR to be generated.