On Mon, 23 Mar 1998, James FitzGibbon wrote:
> I've noticed a conflict in the aliasfile director.
>
> Let's say that I have a file named /opt/mail/etc/virtual_aliases, the
> contents of which are :
>
> james@??? james@???
> *@somedomain.com someoneelse@???
You are not the first to notice this discrepancy.
> And in my exim configuration, I have :
>
> virtual_domains:
> driver = aliasfile
> file = /opt/mail/etc/virtual_aliases.db
> search_type = dbm*
> include_domain
Exim 1.82 doesn't do any special about lookups for aliases. They behave
just like any other lookup. Consequently, if the original lookup fails,
it tries for * in order to get a default.
The next release of Exim (1.90 - currently in beta as 1.891 with only
minimal documentation, but expected to be released by the end of the
month) has a new feature. If you say, for example,
search_type = dbm*@
then, if the key contains an @ character, before looking for * it will
also look for *@xxxx where xxxx is everything after the last @ in the
key.
> It seems that when search_type is dbm*, the second check for uses just "*"
> as the key. I'm new to exim, but my initial impression (and I suspect other
> sendmail converts) was that because I used the include_domain option, it
> would look up the user as foo@???, then "*@somedomain.com".
Unfortunately not; include_domain simply affects how the key for the
lookup is built. The lookup itself is standard code that is used in many
places in Exim, not just for alias files.
> Still, is there a way of doing what I intially wanted ?
There will be...
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
--
*** Exim information can be found at
http://www.exim.org/ ***
