Mailing List Archive: exim: users

implementing a delayed delivery host

Index | Next | Previous | View Threaded

paul.osborne at canterbury

Dec 2, 2009, 9:05 AM

Post #1 of 2 (426 views)
Permalink

implementing a delayed delivery host

Afternoon all,

I am going through the hoops of upgrading our mail routing
infrastructure, and one thing that occurred to me which could be useful
would be a delayed delivery host, I suspect there is a sensible name but
that is the best I came up with in the spur of the moment.

My thoughts are that since my MXs talk to multiple mail stores locally
it could be useful if it were not possible to do a mail delivery
immediately because say our Exchange server was unavailable then the
mail could automagically be sent onto another host and spool there quite
happily. The theory being that once the downed system does come back to
life the delayed delivery host can just unload the email at leisure with
no adverse performance on the MXs.

Anyway I have peered through the Exim manual and may be suffering from
wood from the trees syndrome as I cannot see an obvious way to implement
this, so it is either ridiculously simple or hard. :) Thoughts are
welcome.

Many thanks

Paul

--
Paul Osborne
Systems Analyst
Infrastructure Group
Computing Services
Canterbury Christ Church University

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

graeme at graemef

Dec 2, 2009, 11:51 AM

Post #2 of 2 (405 views)
Permalink

Re: implementing a delayed delivery host [In reply to]

On Wed, 2009-12-02 at 17:05 +0000, paul.osborne [at] canterbury wrote:
> Anyway I have peered through the Exim manual and may be suffering from
> wood from the trees syndrome as I cannot see an obvious way to implement
> this, so it is either ridiculously simple or hard. :) Thoughts are
> welcome.

Put this sufficiently early in your routers (before the routers which
deliver to internal hosts):

too_old:
driver = manualroute
condition = ${if > {$message_age}{86400}{yes}{no}}
transport = remote_smtp
route_list = * your.host.name

If you tune the message age to something suitable short, then anything
which doesn't deliver immediately will be punted on the next queue run.
You can also fiddle with conditions to ensure it's only for local
domains, for example.

Simples!

Graeme

--
## List details at http://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads