On Wed, May 07, 2003 at 12:06:46PM +0200, Nico van der Dussen wrote:
> there seems to be a demand for virtual host routing.
Yes, but in very perlish, and exim style, everybody has different
requirements to how they want to do it. This is something that exim
gives you. It isn't prescriptive about how you must do things, unlike
some MTAs and their authors.
> The code below is from either the manual or from the exim3 to 4
> conversion script, or a combination from both - I can't remember
> anymore
> virtual:
> driver = redirect
> allow_defer
> allow_fail
> data = ${lookup{$local_part}lsearch*{/usr/exim/virtual/alias/$domain}}
> domains = dbm;/usr/exim/virtual/domains
> no_more
> retry_use_local_part
> I also disabled the userforward: director.
That's one way to do it, it's OK. In my case, I want things like forbid_file
and forbid_pipe, because I let users edit their own domain files. I also
make sure that the file that's called is ${lc:$domain}, which is probably
a sensible thing to want to do. I also expand it. So you can say:
*: ${local_part}@....
Which is a useful thing to want to do.
I also allow userforward, so "no_more" is not a useful thing for me. As well
as being able to push things into, say, mailman mailing lists, which I handle
with an internal domain.
> the domains line could most probably be replaced with a dsearch
This is precisely what I do, and of course, if you're going to do something
like that, then you need it in your accept list too.
> This works for me without any problems for about 20 domains sending
> regular mail.
As it should! The question is, is that the way that someone else wants to
manage their systems?
MBM
--
Matthew Byng-Maddick <mbm@???> http://colondot.net/
