The Retry Queue dialog, located under Queues » Mail Queues, is used to determine how MDaemon will handle messages that cannot be delivered due to some non-fatal error, such as when the receiving server is temporarily unavailable.
Keep message in the remote 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
When this box is checked, MDaemon will inform the sender when his or her message is removed and placed in the retry queue. The text of this message can be found (and edited) in the DeliveryWarning.dat file in MDaemon's \app\ folder.
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 DeliveryWarning.dat file in MDaemon's \app\ folder.
Include original message when informing sender
Click this option to include the original message as an attachment in the above notification messages to the sender.
Place undeliverable DSN messages into bad message queue
Click this checkbox if you wish to place undeliverable Delivery Status Notification (DSN) messages into the bad message queue rather than retrying them.
This only applies to DSN messages generated by MDaemon.
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. If you enter "0" days into this option then the message will be bounced back after the first retry attempt. The default setting is 2 days.
Place the undeliverable message in the bad message queue
When this option is enabled, a message will be moved to the bad message queue once it has reached the time limit set in the "If a message is still undeliverable after xx days then:" option.
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:" option, this switch will cause MDaemon to send a message to the sender informing him that the message has been permanently removed from the server. The text of this message can be found (and edited) in the DeliveryError.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
By default, the retry system will not inform the postmaster that a message could not be delivered when that message was auto-generated by MDaemon. Clear this checkbox if you wish to inform the postmaster about the failure of those messages as well. 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 or postmaster
Click this option to include the original message as an attachment in the delivery failure messages to the sender or postmaster.
Place messages with no recipients into bad message queue
When this option is enabled, messages with no recipient data will be moved to the bad message queue. When disabled, they will be deleted. This option is enabled by default.