On Wed, 17 Apr 1996, Ian Jackson wrote:
> Indeed. The important thing is for the user to be able to get at the
> envelope recipient information, which most MTA's don't allow in a
> sensible way. Having the MTA be able to bounce addresses with unknown
> suffixes is good too, as it preserves the `strict addressing' model
> for email address local parts.
I will think about this issue, but probably not until after first full
release of Exim.
> One of qmail's good features is the ability to have a virtual domain
> owned by a user, so that they have the config files in their directory
> and so that any programs executed are executed as them. Can exim do
> this ?
The sysadmin can set up a domain with, for example, an alias file owned
by a user, and arrange that any programs run as a result of such
aliasing are run as that user. This would seem to go some of the way.
Something like this (I haven't tested it), where I'm using my login id
(ph10) and my group (ph10) as an example:
virtual:
driver = aliasfile,
domains = ph10.virtual.domain,
no_more;
directory = /home/ph10,
file = /home/ph10/virtual.aliasfile,
search_type = lsearch,
user = ph10
Is this good enough? One could use the expansion mechanisms to
generalize for many users:
virtual:
driver = aliasfile,
domains = *.virtual.domain,
no_more;
directory = /home/$local_part,
file = /home/$local_part/virtual.aliasfile,
search_type = lsearch,
user = $local_part
(A restricted set of domains could be specified by doing a dbm lookup,
if required. Or listed explicitly or specified via a regular expression
if that is simple enough.)
--
Philip Hazel University Computing Service,
ph10@??? New Museums Site, Cambridge CB2 3QG,
P.Hazel@??? England. Phone: +44 1223 334714
