Strange.  I setup my forwarder as suggested below but it appears qmail
will not allow the following situation:

.qmail-puzzlebox-bobo
        contains text: joshp

where joshp is a /etc/passwd account on the mail system.

if( bobo != bobo )
        .. do not deliver mail
else
        .. deliver

All I need to do is take the 5 billion alias's these people think up for
their domains and selectively send them to a physical account.  I use
pine, so I'm not sure if vpop will work.  I actually installed vpop, and
qmail admin.  Unfortunately, it's not a 'out of the box solution' for
OpenBSD 2.5 , but what is.  It doesn't appear to setup alias's or forwards
successfully.

Thanks for your help / patience :)


Josh

On Mon, 3 Jan 2000, Peter Cavender wrote:

> >Hello,
> >
> >I read the virtual hosting faq, but I'm left wondering how do I set up a
> >virtual mail domain that will send mail to seperate mail users.  The FAQ,
> >as I understand it, only explains how to send <everyone>@yourdom.com to
> >one individuals mail box.  I ( my customers ) need to be able to receive
> >mail addressed to their domain in different mail box's.  For example:
> >
> >Mail For:            Deliver To:
> >--------------------------------------------
> >[EMAIL PROTECTED] -> /home/jill/Maildir
> >[EMAIL PROTECTED] -> /home/bobe/Maildir
> >[EMAIL PROTECTED] -> /home/elli/Maildir
> >
> >Should I use procmail to do this or does one of the mail guru's out there
> >have a super elegant way to achieve this?
> >
> >Thanks for the help, as usual!
> >
> >
> >Josh
> 
> You do send all the mail for a domain to one user (I have a user 
> "forwarder" for this purpose), then, for that user, you have multiple 
> .qmail files that tell where to deliver the messages.  It took me 
> forever to figure this out myself.
> 
> in virtualdomains:
> domain1.com:forwarder-domain1
> domain2.com:forwarder-domain2
> 
> Then make the .qmail files:
> /home/forwarder/.qmail-domain1-jill
> contains "jill"
> 
> /home/forwarder/.qmail-domain2-bobe
> contains "bobe"
> 
> etc.
> 
> 
> Pete
> 
> 

Reply via email to