Customizing the text of mail failure messages
You can customize the text of messages that IBM® Domino® sends when various mail failures occur. The text you specify is added to the default text for the message. Customize messages to provide text in multiple languages or supply users with additional information about how to respond to a failure. For example, add text that provides the phone number to call in case a mail message does not reach your server.
About this task
You can enter customized text directly on the Configuration Settings document or create text files for each customized message and then use the Configuration Settings document to specify the location of each file.
Procedure
- Make sure you already have a Configuration Settings document for the server(s) to be configured.
- From the Domino Administrator, click the Configuration tab and expand the Messaging section.
- Click Configurations.
- Select the Configuration Settings document for the mail server or servers you want to administer, and click Edit Configuration.
- Click the Router/SMTP > Advanced > Controls tab.
- In the Failure Messages section,
choose a method for specifying the customized text for failure messages:
Table 1. Failure Messages fields Method
Description
Text file
The Router adds customized text to failure messages from external files. For each condition listed, enter the complete path to a text file that contains customized text you want to add to the default failure message.
Text
The Router adds customized text to failure messages from text entered in the Configuration Settings document. For each condition listed, enter the customized text you want to add to the default failure message.
- Complete these fields, and then click Save &
Close:
Table 2. Message delivery failure fields Field
Enter
Transfer failure
Transfer failures occur when there is a connection failure between the servers.
If you specified Text in Step 6, enter text to add to the default transfer failure message; otherwise specify the path to a file containing the text -- for example, C:\DOMINO\DATA\TRANSFER.TXT.
Delivery failure
Delivery failures occur when the server is unable to deliver the message to the recipient's mail file.
If you specified Text in Step 6, enter text to add to the default delivery failure message; otherwise specify the path to a file containing the text -- for example, C:\DOMINO\DATA\DELIVER.TXT.
Message expiration
Message expiration failures occur when Domino cannot transfer the message to its destination in a given period of time.
If you specified Text in Step 6, enter text to add to the default message expiration notification; otherwise specify the path to a file containing the text -- for example, C:\DOMINO\DATA\EXPIRE.TXT.
Domain failure
Domain failures occur when Domino cannot identify the destination domain for a recipient of a message.
If you specified Text in Step 6, enter text to add to the default message for domain failures, or specify the path to a file containing the text -- for example, C:\DOMINO\DATA\DOMAIN.TXT.
Server failure
Server failures occur when Domino cannot connect to the destination server.
If you specified Text in Step 6, enter text to add to the default message for server failures; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\SERVER.TXT.
Username failure
User name failures occur when Domino cannot match the local part of an address to a recipient. For example, if you send a message to jdoe@renovations.com, but Domino cannot find jdoe in the Domino Directory, the server generates a user name failure message.
If you specified Text in Step 6, enter text to add to the default message for user name failures; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\USER.TXT.
Size failure
Size failures occur when Domino rejects a message because its size is greater than the maximum message size.
If you specified Text in Step 6, enter text to add to the default message for size failures; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\SIZE.TXT.
Restriction failure
Restriction failures occur when Domino rejects a message based on outbound Router restrictions. For example, if you send a message to jdoe@renovations.com, but renovations.com is listed in the Deny messages from the following Internet addresses to be sent to the Internet field on the Router/SMTP > Restrictions and Controls > SMTP Outbound Controls tab of the Server Configuration document, Domino rejects the message and generates a restriction failure message.
If you specified Text in Step 6, enter text to add to the default message for restriction failures; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\RESTRICT.TXT.
Delay notification
Low-priority routing delays occur when MAIL.BOX receives a message that is marked low priority and the Router waits to process the message until the specified low-priority routing time (12:00 AM to 6:00 AM by default). If low-priority delay notifications are enabled for the message, the Router sends a delay notification to the originator's address.
If you specified Text in Step 6, enter text to add to the default low-priority delay notification; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\DELAY.TXT
Quota warning notification
The Router sends Quota warning notifications to users whose mail files exceed their configured quota warning threshold.
If you specified Text in Step 6, enter text to add to the default quota warning notification; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\WARNING.TXT.
Quota error notification
The Router sends Quota error notifications to users whose mail files exceed their configured quota.
If you specified Text in Step 6, enter text to add to the default quota error notification; otherwise, specify the path to a file containing the text -- for example, C:\DOMINO\DATA\QUOTA.TXT.
- The change takes effect after the next Router configuration update. To put the new setting into effect immediately, reload the routing configuration.