Ok maybe i don't quite understand you, or i didn't make my situation clear enough:

1: I want the alias user to handle all virtual domains, since i own the box this 
should not be a
problem and i don't need to clutter up my home dir with .qmail files.

2: I am serving to many different people from every virtual domain i have, some being 
actual account
on my machine, some being simple aliases for remote accounts.

now the way i have set it up works perfektly for me, EXCEPT the problem i showed in my 
original
mail.

What i am looking for is a way to make the forwarding dynamical based on the extension.

example:

mail to [EMAIL PROTECTED] is delivered to mbj-ext-1@localhost

and mail to [EMAIL PROTECTED] is delivered to mbj-ext-2@localhost

(both owned by user mbj ofcause)

but i also want mail to [EMAIL PROTECTED] is delivered to tony-ext-1@localhost

and mail to [EMAIL PROTECTED] is delivered to tony-ext-2@localhost

(both owned by user tony ofcause)

at the same time i want mail to sam*@domain.com is delivered to [EMAIL PROTECTED]


i mean instead of having a dead $[EMAIL PROTECTED] command in the alias users 
.qmail-whatever,
isn't there a way for me to route the incomming mail intelligently in a catch-all way 
based on the
first word? (by first word i mean mbj or tony or sam in the examples above)

Do i make any sense or am i very terrible with the english language and unable to 
explain what i
mean (or am i just unable to see the forrest because of to alle the trees blocking my 
vision)? (i am
danish, sorry :)


Thanks for not being too impatient with my stupidity

/Martin

Dave Sill wrote:
> 
> Martin Jespersen <[EMAIL PROTECTED]> wrote:
> 
> >i have a virtual domain like this:
> >
> >domain.com:alias-domain:com
> >
> >
> >now i get a mail to [EMAIL PROTECTED] which is then handled by
> >alias/.qmail-domain:com-mbj-default and
> 
> Correction: that should be ~alias/.qmail-domain:com-mbj or
> ~alias/.qmail-domain:com-default.
> 
> >it looks like this:
> >
> >&[EMAIL PROTECTED]
> >
> >the problem is that user mbj doesn't have control over
> >[EMAIL PROTECTED] with this setup since
> >[EMAIL PROTECTED] also goes to
> >
> >[EMAIL PROTECTED]
> 
> So why don't you direct the domain to mbj in virtualdomains, e.g.:
> 
>   domain.com:mbj-domain:com
> 
> and mbj can set up whatever .qmail-domain:com-* files he wants?
> 
> >i mean, without having to set up individual .qmail-ext files for all
> >the users in alias's home dir....
> 
> How about having to set up individual .qmail-ext files for all
> the users in mbj's home dir?
> 
> If that's not acceptable, run fastforward from
> ~mbj/.qmail-domain:com-default, and mbj will be able to manage the
> domain from an alias table.
> 
> -Dave

Reply via email to