However I do believe it is best to have all mail setup as virtual domains.
This allows you to use the Qmailadmin with all your accounts and makes it
easier to manage.
---
Brad Dameron [EMAIL PROTECTED]
Network Account Executive 877-663-4349
TSCNet Online Services www.tscnet.com
> -----Original Message-----
> From: Bill Shupp [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 02, 2001 3:44 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Strange request...
>
>
> on 3/2/01 4:52 PM, [EMAIL PROTECTED] at [EMAIL PROTECTED] wrote:
>
> > Hi List;
> >
> > I'm really not sure if this is possible, but here is my question.
> >
> > With VPOPMail, you can support /etc/passwd users. With the
> POP3 daemon
> > that comes with it, you can authenticate an /etc/passwd
> user and open up
> > the relay for that user.
> >
> > Now, if you use another program that works off of the
> vpopmail library
> > (such as courier imap for example) it will handle virtual
> domain users (in
> > the form of [EMAIL PROTECTED]) but, it will NOT handle
> /etc/passwd users
> > being passed down to the vpopmail authentication module and
> thus open a
> > relay for that user.
> >
> > I suppose the answer would be to move the /etc/passwd users
> into a virtual
> > domain and compile it with default domain, but it seems
> that since the
> > vpopmail program can handle it, why can the library not
> handle it for
> > other programs that support vpopmail authentication?
>
> It should work. Just have courierimap ONLY use the
> authvchkpw module. And
> if vchkpw is setup to authorize /etc/passwd users, it should work.
>
> -Bill
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/2001
