108

Retry Configuration dialog

Retry Configuration dialog

Retry Frequency

Keep message in the primary queue for at least xx minutes

This setting governs the length of time a message will remain in the remote queue before being removed and placed in the retry queue. The remote queue will generally attempt to deliver the message more frequently than the retry queue.

Retry sending undeliverable mail once every xx minutes

This setting determines how frequently the messages in the retry queue are processed.

Inform the sender when message is placed in retry queue

This switch will inform the sender when his/her message is removed and placed in the retry queue. The text of this message can be found (and edited) in the DELWARN.DAT file.

Inform the sender when subsequent delivery attempts fail

If a delivery attempt of a message in the retry queue fails, a message explaining this fact will be dispatched to the sender of the message. The text of this message can be found (and edited) in the DELWARN.DAT file.

Include original message when informing sender

If a delivery attempt of a message fails and you have selected to let the sender know, MDaemon will attach the original message to the delivery notification.

Place undeliverable DSN messages into bad queue

With this switch enabled, if MDaemon's delivery failure messages are not able to be delivered the server will place these messages in the bad queue instead of retrying them over and over for the time limit.

Ultimate Fate of Undeliverable Mail

If a message is still undeliverable after xx days then:

This setting determines the number of days that a message can remain in the retry queue before being removed.

Place the undeliverable message in the bad message queue

Once a message has reached the time limit set in the If A Message Is Still Undeliverable After xx Days Then: control, a copy of that message will be moved to the bad message directory if this switch is enabled.

Inform the sender that the message could not be delivered

Once a message has reached the time limit set in the If A Message Is Still Undeliverable After xx Days Then: control, this switch will cause MDaemon to send a message to the sender informing them that the message has been permanently removed from the server. The text of this message can be found (and edited) in the DELERR.DAT file.

Inform the postmaster that the message could not be delivered

If this switch is enabled, the postmaster will be notified when a message has been permanently removed from the retry system.

. . . unless it’s an mdaemon auto-generated message

The retry system will never inform MDaemon when an auto-generated message fails to be delivered. However, because such information may be useful to the postmaster, he or she will be informed when these messages cannot be delivered. Check this box if you do not want the postmaster to be informed when auto-generated messages cannot be delivered. Examples of auto-generated messages are return-receipt notifications, auto-responder generated messages, results of account processing, and so on.

Include original message when informing sender

If a delivery attempt of a message fails and you have selected to let the sender know, MDaemon will attach the original message to the delivery notification.