Re: [Exim] restricted virt domain with /dev/null for rest

Top Page
Delete this message
Reply to this message
Author: Peter Radcliffe
Date:  
To: exim users
New-Topics: [Exim] spool file locked for LONG times...
Subject: Re: [Exim] restricted virt domain with /dev/null for rest
Randy Bush <randy@???> probably said:
> note that by "deliver locally" there may be relevant ~/.forwards or
> /etc/aliased entries.
>
>     bogus_local:
>       driver = domainlist
>       local_parts = user0:user1
>       domains = bogus.com
>       route_list = * localhost byname
>       self = local

>
> leaves all non-matching as frozed as lowest mx points to self. i want to
> /dev/null them.


Once something is on the machine and you're doing local processing
(rather than sending it on to another machine) deal with it as a local
domain as apposed to messy re-routing hacks. Routing is usually used
for sending things onto a different machine or another copy of exim.

bogus_local:
driver = smartuser
local_parts = user0:user1
domains = bogus.com
new_address = ${local_part}@???
no_more

Put this first in your directors. Only the listed local_parts will
match and will get reprocessed as if they came in for @psg.com
(including any applicable aliases or forwards, etc), anything else
will bounce since the no_more means no other directors will get
checked for that domain.

You could also put a lookup in that local_parts so you don't have to
edit the config file and restart exim for any change. In fact, I'd
recommend uding one of the far more versatile virtual domain configs
in the example configurations - then you could redirect any domains
like this however you chose to, pretty much.

P.

-- 
pir                  pir@???                    pir@???