On Sat, 5 Feb 2000, robert rotman wrote:
> the best way, IMHO is:
> set option "move_frozen_messages"
That option was added for someone who wanted to write software to handle
them. Exim has no such support itself.
> set option "remove_move_frozen_messages 14d" (whishlist;)
> send a notification to the postmaster when a frozen message is moved.
> (is that possible?)
Have you noticed these options? (I run with ignore_errmsg_errors_after=12h,
and find that works quite well.)
auto_thaw
Type: time
Default: 0s
If this option is set to a non-zero time, a new delivery is attempted on
frozen messages if this much time has passed since the message was frozen.
ignore_errmsg_errors
Type: boolean
Default: false
If this option is set, failed addresses in error reports (that is,
messages whose senders are '<>') are discarded (with a log entry). The
default action is to freeze such messages for human attention.
ignore_errmsg_errors_after
Type: time
Default: 0s
This option, if it is set to a non-zero time, acts as a delayed version of
ignore_errmsg_errors, which must be unset for this option to take effect.
If an error message is frozen because of delivery failure, then once the
given time has elapsed after the freezing took place, the message is
unfrozen at the next queue run. If delivery fails again, the error message
is discarded. This makes it possible to keep failed error messages around
for a shorter time than the normal maximum retry time.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
