Jeffrey Goldberg <jeffrey+lists@???> probably said:
> Anyway, if exim does a queue run while exim-route-file is empty I get
> a hard failure because I am sending to an unroutable domain. The router
> listed above is the only router.
>
> I suppose, just as I write this, if I added a director at the end that
> just defered everything that hit it, that should do the job. I will play
> with that. Hmm. Yes, that should work since when the exim-route-file
> contains a * entry everything will go that way, and so will only fall
> through when that file is empty. Now the trick is to create such a
> router.
>
> In the meantime, the only option is to not do any queue runs while not
> connected. That is fine for now, but in the future I expect to need to do
> queue runs for things on a local network.
I don't see this problem.
I have queue_remote_domains="*" and I run a queue run out of cron
every so often. That cron script tests if I have a default route, and
if I don't, I don't do a queue run ...
One of the things I do in the scripts that bring the line up is
'exim -qqf' which bypasses the queue_remote_domains so things go
out immediately when I bring the line up.
But even if you don't test for a default route, remote stuff shouldn't
be routed to get that "unroutable domain" error when the line isn't up
... I have no idea why you're getting that.
P.
--
pir pir@??? pir@???
