Nigel Metheringham <Nigel.Metheringham@???> said:
> > Hence what I'd like to be able to do is add a backup or low priority
> > transport, which acts pretty much like a very low priority MX host.
Good idea.
John Henders <jhenders@???> said:
> I like this idea, but wondered about another approach. If you were to
> use the lookuphost driver to match each site, and exim were extended to
> allow specifying a seperate queue, both for delivery into and for queue
> running, this would do what you want, plus have some additional
> benefits.
You don't need to extend Exim for that. You just need several config files
and the "-C" command line option. I have successfully used the following
approach with smail:
* message arrives in "normal" queue.
* router matches the destination domain and sends it to a special
transport.
* special transport pipes message to another instance of smail, with
special "-C" command line option to make the other instance of smail
use a different config file.
* different config file specifies a different spool directory.
* queue runs using the different spool directory are done when
appropriate.
I hoped to be able to use Exim's "-R" option to run the queue only for
certain destinations, without having to use separate spool directories,
but it has turned out not to be efficient. "exim -R" seems to have to
open every message in the queue before deciding whether to process it,
whereas I had initially expected it to get that from a dbm file.
--apb (Alan Barrett)
