> On a previously installed vpopmail system, how do I know which
> parameters were passed to ./configure ? I have the directory in which
> the tar file was untarred into.
Then look into the config.status file.
> > > Also should the tcpserver file be /etc/tcp.smtp or
> > > /home/vpopmail/etc/tcp.smtp ?
> > Both locations will work fine, but vpopmail will need root access if you
> > want to use the /etc location.
> What exactly do I do for giving vpopmail root access?
chown root ~vpopmail/bin/vchkpw
chmod u+s ~vpopmail/bin/vchkpw
However, I'd only suggest to do this if you have your domains managed
under different user id's (in fact, then you'll _need_ these
modifications); if you're going with all domains under the vpopmail id,
you'll go better with ~vpopmail/etc/tcp.smtp.
> > > And address extensions=OFF as shown above, will it mean I won't be able to use
> > > .qmail-payal-linux kind of addresses?
> > No; these addresses will be handled by qmail itself _before_ vpopmail
> > drops in (through being called out of .qmail-default) and work in either
> > case.
> Then what is the use of qmail-ext parameter for ./configure ?
See the ChangeLog (this option appeared in 4.10.12):
- added new configure option --enable-qmail-ext. This
was the default in old installations. Now there is
an option to turn it off.
--enable-qmail-ext=y (default) will deliver mail
for [EMAIL PROTECTED] to [EMAIL PROTECTED]
--enable-qmail-ext=n will NOT deliver mail for
[EMAIL PROTECTED] to [EMAIL PROTECTED] It will
only deliver it to [EMAIL PROTECTED]