On Dec 5, 9:50 pm, Andrew Sackville-West <[EMAIL PROTECTED]>
wrote:
> exchange_router:
> driver = manualroute # not manual!
> data = ${lookup{$local_part}lsearch{/path/to/recipient-file}}
> transport = exchange_smtp
>
> you don't need a 'fail' part (other thread) because since this router
> won't match, and the ACL above will deny it. I think.
>
> hth
>
> A
>
Andrew:
10TB TX! your posts helped immensely!
Now the whole process is starting to make some sense to me.... nothing like
a good example to get you going!
I "think" I can now handle the specifics of what I need to do
programatically (in the conf file). I should at least know enuf to do some
decent testing...
I believe there have only been 2 people, you & someone else that made
reference to the the example conf file distributed with exim. This file
makes more sense than the conf other files. I am at a complete loss as to
why more references to this file do not seem to exist - particularly in
doc's/faq's I've read on debian & exim sites.
I had actually <u>started</u> to go thru this file before, but I stopped,
because of 1 crucial thing.
Even IF I got the file perfect - I'm still not sure where it goes! LOL.
It certainly can't replace exim4.conf.template (I think) because none of the
expected var's are in there.
I don't think I can just place it in /var/lib/exim4/config.autogenerated
because, as the name implies, that file get's overwritten each time exim is
started.
I don't "think" it does anything to leave it in /etc/exim4/exim.conf
because I don't think that any automated process looks at that file...
although I've seen many references to this file, I believe they were all
related to exim ver. 3.
I don't think it can replace sa-exim.conf as that file pertains to spam
assassin.
I have to assume it should not go in /etc/exim.conf as there IS an exim4
directory...
no man page for exim.conf....
anyway... I had given up on exim.conf as a solution for all of the above
reasons...
