On Wed, 13 Oct 2004, Christiaan den Besten wrote:
> I use Mailscanner for mail filtering, so the 'input' exim daemon has 'queue
> only' set in the configuration. But exim requires to have a 'valid' router and
> transport anyway .... ( even when you have queue_only enabled ).
I presume that is because you are doing recipient verification?
> To make exim
> happy I made the following router:
>
> smarthost:
> driver = manualroute
> domains = *
> transport = remote_smtp
> route_list = * 1.2.3.4
> no_more
>
> ( localhost does not work, for exim than thinks it should forward the message
> to the same host and suspects a loop )
Two comments: (1) Since that always accepts, why bother with the
recipient verification? Just turn it off in the ACL. (2) If you just
want a router/transport that accepts, try this:
xxxx:
driver = accept
transport = yyy
yyy:
driver = appendfile
file = /dev/null
But, reading further, I'm not sure this is right, so don't do it till
you understand the rest...
> It should simply accepts all mail (yes, should have used an 'accept' router,
> juist build that one :) ) and should never realy be used because the daemon
> should just (and does) queue the message.
>
> But, exim -does- check if it can reach the (nonexistent) host. So its gives an
> error once every 5 days ;) ....
That is actually strange. It should not be trying to do any deliveries
when queue_only is set. Have you remembered to start the 'input' daemon
with just -bd? If you have used '-q10m' or similar, it's going to be
trying to do deliveries, and you'll get this effect....
> Is there any particular reason for exim to check for 'valid'
> transports/routers in a queue_only mode?
It will verify if you have used 'verify = recipient' in an ACL (or
'verify = sender') but it should not try to deliver.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
