This article applies to:
- Trustwave MailMarshal (SEG)
- Trustwave ECM/MailMarshal Exchange
Question:
- How do I change Default Email Templates in MailMarshal?
- How can I send email notifications in a language other than English?
Procedure:
MailMarshal uses email templates to cater for such occurences as undeliverable or timed-out messages. You can override these default notification templates and create your own custom messages.
See also Q10334: How do I disable DeadLetter and Undeliverable notifications to the Administrator mailbox?
The exact list of templates and user interface names vary by version of MailMarshal. For details please see the Help and User Guide for your version.
- Create a Custom Template
For each template that you want to override, create the desired custom template in the MailMarshal Configurator or Management Interface (under Policy Elements | Email Templates). The template can contain whatever data you require. Note: The last section of this article shows some default templates and the data they contain. These can be used as a reference when creating your custom templates. Definitions of variables are provided in the User Guide.
- Configure MailMarshal to Use the New Template
Open the Advanced system properties | Templates item (in MailMarshal (SEG) 10 Management Interface, underSystem Configuration; in earlier versions, under Trustwave SEG Properties). For each template that you want to override, select the desired template from the menu.
All templates configured under the Email Templates node in the Configurator will be available in the menu.
- Commit configuration changes.
Note that the templates used for email sent by the end user web interface cannot be customized (Spam Quarantine Management or Quarantine Management website).
Default Templates
Engine:
The following templates are the defaults for messages generated by the Engine in recent versions of SEG and ECM.
Dead Letter (Incoming):
[Header]
reply-to=
from={ServerAddress}
to={Administrator}
cc=
bcc=
subject=Dead Letter: "{Subject}"
[Attachments]
attach=
[Body]
Message {MessageName} has been placed in the DeadLetter\Unpacking folder
by the Engine because of:
{Reason}
The recipients that have been affected are:
{FormattedRecipients}
Additional Information
======================
Sender: <{Sender}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Dead Letter (Internal):
[Header]
reply-to=
from={ServerAddress}
to={Administrator}
cc=
bcc=
subject=Dead Letter: "{Subject}"
[Attachments]
attach=
[Body]
Internal Message {MessageName} has been placed in the DeadLetter\Unpacking folder
by the Engine because of:
{Reason}
The recipients that have been affected are:
{FormattedRecipients}
Additional Information
======================
Sender: <{Sender}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Dead Letter (Outgoing):
[Header]
reply-to=
from={ServerAddress}
to={Administrator}; {LocalSender}
cc=
bcc=
subject=Dead Letter: "{Subject}"
[Attachments]
attach=
[Body]
Message {MessageName} has been placed in the DeadLetter\Unpacking folder
by the Engine because of:
{Reason}
The recipients that have been affected are:
{FormattedRecipients}
Additional Information
======================
Sender: <{Sender}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Undetermined (Incoming):
[Header]
from={ServerAddress}
to={Administrator}
subject=Undetermined Result Received
[Attachments]
attach=
[Body]
Message {MessageName} has been placed in the Undetermined folder
by the Engine because of: {Reason}
The recipients that have been affected are:
{FormattedRecipients}
Additional Information
======================
Sender: <{Sender}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Undetermined (Internal):
[Header]
from={ServerAddress}
to={Administrator}; {LocalSender}
subject=Undetermined Result Received
[Attachments]
attach=
[Body]
Internal Message {MessageName} has been placed in the Undetermined folder
by the Engine because of: {Reason}
The recipients that have been affected are:
{FormattedRecipients}
Additional Information
======================
Sender: <{Sender}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Undetermined (Outgoing):
[Header]
from={ServerAddress}
to={Administrator}; {LocalSender}
subject=Undetermined Result Received
[Attachments]
attach=
[Body]
Message {MessageName} has been placed in the Undetermined folder
by the Engine because of: {Reason}
The recipients that have been affected are:
{FormattedRecipients}
Additional Information
======================
Sender: <{Sender}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Sender:
The following templates are the defaults for messages generated by the Sender in recent versions of SEG (MailMarshal Exchange does not use the MailMarshal Sender service).
Bad domain:
[Header]
reply-to=
from={ServerAddress}
to={ReturnPath}
cc=
bcc=
subject=Undeliverable Mail: "{Subject}"
[Body]
Your message:
From: {From}
Subject: {Subject}
Could not be delivered because the domain name was unresolvable:
{Reason}
The following recipients were affected:
{FormattedRecipientsAffected}
Additional Information
======================
Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Last-Attempt-Date: <{LastAttemptDate}>
Dead Letter (Incoming):
[Header]
reply-to=
from={ServerAddress}
to={Administrator}
cc=
bcc=
subject=Dead Letter: "{Subject}"
[AttachMessage]
attach={MessageFullName}
[Body]
Message {MessageName} has been placed in the DeadLetter\Routing folder because of:
{Reason}
The recipients that have been effected are:
{FormattedRecipientsAffected}
Additional Information
======================
Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
Remote-MTA: <{RemoteIP}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Last-Attempt-Date: <{LastAttemptDate}>
Dead Letter (Outgoing):
[Header]
reply-to=
from={ServerAddress}
to={Administrator}; {LocalSender}
cc=
bcc=
subject=Dead Letter: "{Subject}"
[AttachMessage]
attach={MessageFullName}
[Body]
Message {MessageName} has been placed in the DeadLetter\Routing folder because of:
{Reason}
The recipients that have been effected are:
{FormattedRecipientsAffected}
Additional Information
======================
Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
Remote-MTA: <{RemoteIP}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Last-Attempt-Date: <{LastAttemptDate}>
Expired:
[Header]
reply-to=
from={ServerAddress}
to={ReturnPath}
cc=
bcc=
subject=Timed Out Mail: "{Subject}"
[Body]
Delivery of a message from you has exceeded the retry time:
From: {From}
Subject: {Subject}
The following recipients could not be delivered:
{FormattedRecipientsAffected}
Additional Information
======================
Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
MessageName: <{MessageName}>
Failure:
[Header]
reply-to=
from={ServerAddress}
to={ReturnPath}
cc=
bcc=
subject=Undeliverable Mail: "{Subject}"
[Body]
Your message:
From: {From}
Subject: {Subject}
Could not be delivered because of
{Reason}
The following recipients were affected:
{FormattedRecipientsAffected}
Additional Information
======================
Original Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
Remote-MTA: <{RemoteIP}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Last-Attempt-Date: <{LastAttemptDate}>
Failure (TLS):
[Header]
reply-to=
from={ServerAddress}
to={ReturnPath}
cc=
bcc=
subject=Returned TLS Mail: "{Subject}"
[Body]
Your TLS message:
From: {From}
Subject: {Subject}
Could not be securely delivered to some or all of the intended recipients.
{Reason}
The following recipients were affected:
{FormattedRecipientsAffected}
Additional Information
======================
Original Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Last-Attempt-Date: <{LastAttemptDate}>
Forward Unknown:
[Header]
reply-to={ReturnPath}
from={Sender}
to={Administrator}
cc=
bcc=
subject=Unknown POP3 Account: "{ShortRecipientList}"
[AttachMessage]
attach={MessageFullName}
[Body]
A message
From: {From}
Subject: {Subject}
could not be delivered to the following recipients as they do not
have a POP3 mailbox
{FormattedRecipientsAffected}
The domain for this recipient only accepts POP3 mail. No mailbox has
been configured for the recipient email address. Any undeliverable
email is to be sent to the administrator.
Additional Information
======================
Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Killed:
[Header]
reply-to=
from={ServerAddress}
to={ReturnPath}
cc=
bcc=
subject=Message Returned: "{Subject}"
[Body]
The delivery of your message:
From: {From}
Subject: {Subject}
was stopped by the administrator
The message was not delivered to the following recipients:
{FormattedRecipientsAffected}
Your message was received {TimeEnteredQueue}.
Additional Information
======================
Original Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Overdue:
[Header]
reply-to=
from={ServerAddress}
to={ReturnPath}
cc=
bcc=
subject=Message Delayed: "{Subject}"
[Body]
Your message
From: {From}
Subject: {Subject}
Has been delayed for some or all of the intended recipients.
The recipients that were affected are:
{FormattedRecipientsAffected}
Your message was received {TimeEnteredQueue}.
The mail system will keep trying to deliver your message for another
{TimeLeft}.
Additional Information
======================
Original Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Undeliverable:
[Header]
reply-to=
from={ServerAddress}
to={Administrator}
cc=
bcc=
subject=Unable to Return Message: {Subject}
[AttachMessage]
attach={MessageFullName}
[Body]
The message {MessageName} has expired or could not be
delivered to the intended recipient, and could not be returned
to the original sender.
This message could not be returned, because the sender did not
provide a return-path routing information. This is likely because
the message is also a notification for an undeliverable message,
or was generated by a MAILER-DAEMON.
Additional Information
======================
Sender: <{Sender}>
Sender-MTA: <{SenderIP}>
Reporting-MTA: <{HostName}>
MessageName: <{MessageName}>
Last-Attempt-Date: <{LastAttemptDate}>
Reason: <{Reason}>
- This article was previously published as:
- NETIQKB29238
- Marshal KB154