Re: [vchkpw] Upgrading from qmail to qmail+vpopmail.
Aran Clary Deltac wrote: Hi all - I've just joined the vpopmail list because of a pressing issue and I need some guidance. 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. I believe domain quotas are broken, I would personally not run sql-logging, you don't need it and it will tax SQL on a busy server. With 10k users doing mysql auth your SQL server will be busy enough. 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. Until you use vpopmail/bin/* to add users vpopmail will have no effect on your server setup. Until you add vdelivermail into your .qmail-default file, vpopmail will have no effect on your delivery. Your only hitch here (from my experience, YMMV) is popping. You will want to have two pop servers running as you slowly migrate since the auth mechanisim will be different between a pure qmail and a vpopmail server. If you migrate overnight, one big migration, you can avoid this. That was the approach I took. Since you have few users now, and will have 10k later, I would opt for the one sweeping migration. DAve
Re: [vchkpw] Upgrading from qmail to qmail+vpopmail.
On Apr 13, 2005, at 9:26 AM, DAve wrote: Your only hitch here (from my experience, YMMV) is popping. You will want to have two pop servers running as you slowly migrate since the auth mechanisim will be different between a pure qmail and a vpopmail server. Not true. I'm pretty sure that if you run qmail-pop3d as root, vchkpw can authenticate system users as well as virtual ones. Look at the --enable-system-user (or some similar wording) option on the vpopmail build. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ You don't need a laptop to troubleshoot high-speed Internet: sniffter.com
[vchkpw] Upgrading from qmail to qmail+vpopmail.
Hi all - I've just joined the vpopmail list because of a pressing issue and I need some guidance. 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. I see docs for UPGADE and INSTALL and various README-*, but none of them seem to be talking about a situation where someone has been running qmail for a while and wants to add vpopmail. Any ideas/hints/thoughts appreciated. Thanks, Aran
Re: [vchkpw] Upgrading from qmail to qmail+vpopmail.
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. -Kurt
Re: [vchkpw] Upgrading from qmail to qmail+vpopmail.
Kurt Bigler said the following on 4/12/2005 6:25 PM: 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 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. -Kurt Having run it on a much smaller scale than you're positioning for, I second the qmailadmin component, and highly recommend vqadmin for much better admin control (easier to confirm and reset passwords, and a few other features.) If your new 10K+ customer is all one domain, vqadmin might be more of a 'nice to have', but for handling several++ domains, it almost seems like a 'very-nice' to 'must-have' admin tool...including adding new domains, and more control over locking out accounts, managing quotas(if that's working in vpopmail), disabling change password per-user/per-domain, etc. Strong recommendation to look into it. Good Luck, but you've come to the right place. Rick Oh, and I /think/ you can leave your local accounts local, and your new virtual accounts as 'virtual' if you want. Might be simpler than migrating your locals over to being virtual. Look into configuring /var/qmail/control/locals, and /var/qmail/control/virtualdomains, but that may be more appropriate to lurk around the qmail list for a while.
