on 4/12/05 11:22 AM, Aran Clary Deltac <[EMAIL PROTECTED]> wrote:

> I've been running a dedicated gentoo server for about a year now.  All
> e-mail has been handled by qmail and delivered to local user accounts.  I
> have the possibility of hosting a client that requires 10k+ e-mail
> accounts.  I really don't want to make system accoutns for each e-mail
> account, so I found vpopmail.
> I just want to make sure I am not doing something dumb.  Here's the
> configure I am useing:  (vpopmail 5.4.10)
> ./configure
> --enable-roaming-users
> --enable-auth-module=mysql
> --enable-sql-logging
> --enable-mysql-limits
> --enable-valias
> --enable-many-domains
> --enable-domainquotas
> I enabled all these extra ones because most of them seemed like
> interesting features that I _might_ want at some point.
> Running 'make' looks good.
> Now, I have no clue if running 'make install-strip' will blow up my
> current production qmail.  I'd like to install vpopmail and migrate my
> settings to it without loosing mail in the process.

Off-hand, I'd think that nothing will really change until you start the
daemon processes that bring vpopmail into the picture.

Do I understand that you have not had any virtual email domains until now?
And that local users are currently having mail delivered to their home
directories and do not require outside pop access?  If so I think it might
be an easy transition.

I think the most difficult part would be to transition existing virtual
domains.  I think there are also options to transition your local users
accounts to be under vpopmail control, but you might not be forced to do
that immediately.

Another trouble spot might be transitioning existing pop service.  You will
be using vchkpw for pop authorization.   For example my ps listing for the
pop service shows this command:

> tcpserver -v -H -R -lvps.breathsense.com -c200 0 110
> /var/qmail/bin/qmail-popup vps.breathsense.com /var/vpopmail/bin/vchkpw
> /var/qmail/bin/qmail-pop3d Maildir

If you are already using qmail-popup on the same port you will be using for
virtual domains, perhaps vchkpw also supports local account authorization
support, via the "default domain" or whatever, but I don't know the ins and
outs of this.

Delivery to virtual domain Maildir's will be handled by vdelivermail,
through the .qmail-default hook for each virtual domain.  This shouldn't get
in the way of existing functionality at all.

The smtp side should work exactly like before, except you will be accepting
mail for additional domains.  The changes to qmail settings gets taken care
of automatically when you create your virtual domains using vpopmail.  Until
you create the domain nothing happens.  When it is created the qmail data
structures are updated.  Presumably existing qmail functionality is not
damaged by this but if you have any doubts you can backup the appropriate
qmail files before adding your first virtual domain.

Support for roaming users is probably not something you need to act on
immediately.  But you will want to transition your smtp daemon.  Again taken
from my ps listing my smtp command looks like this:

> tcpserver -v -H -R -lvps.breathsense.com -x /var/vpopmail/etc/tcp.smtp.cdb
> -c200 -u1003 -g1001 0 25 fixcrio /var/qmail/bin/qmail-smtpd

You need to make sure that /var/vpopmail/etc/tcp.smtp.cdb is set up
correctly to allow your existing smtp connections to be accepted.  There are
comments around that clarify this.  Then when you are ready you can get the
roaming part working and that is not too difficult.

You might want to look at using qmailadmin, which is quite a convenience.  I
use qmailadmin for most things, and use the command line only to create new
domains using vadddomain.  The rest of the vpopmail setup commands (e.g.
adding users) are taken care of qmailadmin.

That's all that comes to mind.  I'm not an old-timer expert, so maybe some
others can chime in, but probably that can get you started.


Reply via email to