Re: [vchkpw] Upgrading vpopmail 5.5.0
run configure add the line make and make install On Mon, Aug 17, 2009 at 2:51 PM, shiv wrote: > this is strange, after editing the file and add the quick fix and run > ./configure. > the quick fix line get removed from the file. > > after recompile, same result, the table does not exists. > > shiv > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> shiv wrote: >>> >>> hello >>> after upgrading from vpopmail 2.4.27 to 5.5.0 and starting vusaged >>> I am getting the following error >> >> shiv, if you want a quick fix, just edit the vmysql.h file in the >> backends/mysql >> directory, and add a line at the top: >> >> #define MANY_DOMAINS 1 >> >> ..then rebuild the MySQL module and re-start the vusage daemon. >> - -- >> /* >> Matt Brookings GnuPG Key FAE0672C >> Software developer Systems technician >> Inter7 Internet Technologies, Inc. (815)776-9465 >> */ >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.9 (GNU/Linux) >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org >> >> iEYEARECAAYFAkqJj3sACgkQIwet2/rgZywBjACfaEwW+mQQqbi+X0S/Enqd8CTF >> xbkAn07L2aVFfH0536KWQA1ZuWDK4rsr >> =UmL4 >> -END PGP SIGNATURE- >> -- Itamar Reis Peixoto e-mail/msn: ita...@ispbrasil.com.br sip: ita...@ispbrasil.com.br skype: itamarjp icq: 81053601 +55 11 4063 5033 +55 34 3221 8599 !DSPAM:4a8998d932717063020892!
Re: [vchkpw] Upgrading vpopmail 5.5.0
this is strange, after editing the file and add the quick fix and run ./configure. the quick fix line get removed from the file. after recompile, same result, the table does not exists. shiv > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > shiv wrote: >> >> hello >> after upgrading from vpopmail 2.4.27 to 5.5.0 and starting vusaged >> I am getting the following error > > shiv, if you want a quick fix, just edit the vmysql.h file in the > backends/mysql > directory, and add a line at the top: > > #define MANY_DOMAINS 1 > > ..then rebuild the MySQL module and re-start the vusage daemon. > - -- > /* > Matt Brookings GnuPG Key FAE0672C > Software developer Systems technician > Inter7 Internet Technologies, Inc. (815)776-9465 > */ > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkqJj3sACgkQIwet2/rgZywBjACfaEwW+mQQqbi+X0S/Enqd8CTF > xbkAn07L2aVFfH0536KWQA1ZuWDK4rsr > =UmL4 > -END PGP SIGNATURE- > !DSPAM:4a89989132711075413977!
Re: [vchkpw] Upgrading vpopmail 5.5.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 shiv wrote: > > hello > after upgrading from vpopmail 2.4.27 to 5.5.0 and starting vusaged > I am getting the following error shiv, if you want a quick fix, just edit the vmysql.h file in the backends/mysql directory, and add a line at the top: #define MANY_DOMAINS 1 ..then rebuild the MySQL module and re-start the vusage daemon. - -- /* Matt BrookingsGnuPG Key FAE0672C Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqJj3sACgkQIwet2/rgZywBjACfaEwW+mQQqbi+X0S/Enqd8CTF xbkAn07L2aVFfH0536KWQA1ZuWDK4rsr =UmL4 -END PGP SIGNATURE-
Re: [vchkpw] Upgrading vpopmail 5.5.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 shiv wrote: > > hello > after upgrading from vpopmail 2.4.27 to 5.5.0 and starting vusaged > I am getting the following error > > vmysql: sql error[3]: Table 'vpopmail.test.gy' doesn't exist > Attempting to rebuild connection to SQL server > vmysql: connection rebuild failed: Table 'vpopmail.test.gy' doesn't exist > Sorry, no mailbox here by that name. (#5.1.1) You need to --enable-many-domains when configuring the MySQL backend, but it appears this option somehow made it's way out of the configure script. I'll have this fixed shortly. - -- /* Matt BrookingsGnuPG Key FAE0672C Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqJiFAACgkQIwet2/rgZyztugCeKbGCvUFqvxZqLzgkqZRe/Yw6 zVoAoI8mQvN7Q+OpowViLzwSX6ohhTYq =EyLV -END PGP SIGNATURE-
[vchkpw] Upgrading vpopmail 5.5.0
hello after upgrading from vpopmail 2.4.27 to 5.5.0 and starting vusaged I am getting the following error vmysql: sql error[3]: Table 'vpopmail.test.gy' doesn't exist Attempting to rebuild connection to SQL server vmysql: connection rebuild failed: Table 'vpopmail.test.gy' doesn't exist Sorry, no mailbox here by that name. (#5.1.1) I have 2 virtual domains and the is my vpopmail database. ++ | Tables_in_vpopmail | ++ | dir_control | | lastauth | | limits | | relay | | vpopmail | ++ thank you. shiv !DSPAM:4a8986c132711697114391!
Re: [vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
Hi,
I'm not that hero in C. But let's try. So, if we want to log all
addresses using the qmail-ext feature, it is done in (vpopmail 5.2.1)
the main function, line 137 (if ((vpw=vauth_getpw(TheUserExt,
TheDomain)) != NULL ) {), right?
The VALIAS is not used (it is not defined in config.h), so that should
be the only place where the address is checked, is that also right?
Kind regards,
Harm van Tilborg
Tom Collins wrote:
On Jul 27, 2006, at 10:51 AM, Harm van Tilborg wrote:
If users have only access to qmailadmin (maybe not really vpopmail
related, but ok), are they able to use qmail-ext addresses? Or do they
really have to know how qmail deals with the 'ext' addresses?
With qmail-ext enabled, users can put -anything after their email
address and still get the message. They'd have to know about that
feature, and chances are they aren't making use of it.
If you're unsure, you could modify vdelivermail to log any qmail-ext
addresses that it matches. If nothing comes through in a few weeks, you
can probably safely disable that feature.
--
Tom Collins - [EMAIL PROTECTED]
Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/
QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
Re: [vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
On Jul 27, 2006, at 10:51 AM, Harm van Tilborg wrote: If users have only access to qmailadmin (maybe not really vpopmail related, but ok), are they able to use qmail-ext addresses? Or do they really have to know how qmail deals with the 'ext' addresses? With qmail-ext enabled, users can put -anything after their email address and still get the message. They'd have to know about that feature, and chances are they aren't making use of it. If you're unsure, you could modify vdelivermail to log any qmail-ext addresses that it matches. If nothing comes through in a few weeks, you can probably safely disable that feature. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
Re: [vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
Hi, Thanks for the quick response. If users have only access to qmailadmin (maybe not really vpopmail related, but ok), are they able to use qmail-ext addresses? Or do they really have to know how qmail deals with the 'ext' addresses? Kind regards, Harm van Tilborg Tom Collins wrote: On Jul 27, 2006, at 8:12 AM, Harm van Tilborg wrote: 1) I'm still running vpopmail 5.2.1 on some servers and it's finally time to upgrade (yes, finally :[). In the UPGRADE instructions it says it shouldn't be a problem (I'm using the cdb auth-module). Is that really true? I think so, but I haven't done an upgrade from 5.2.1 in a long time. 2) And I would like to turn off qmail-ext support in the upgrade. Could that give any problems? If you have users relying on it to get their email, then it will be a problem. Some of my users make use of it to generate unique email addresses (like tom-amazon for all email from amazon.com) that they can later turn into blackhole or bounce addresses. 3) Domain and user quotas are kind of broken, aren't they? The only way to make them work is with the Maildir++-patch, is that true? Domain quotas are definitely broken, and have been disabled in the current release. 4) Will this upgrade change anything to the already set (but not working) quotas? I don't know -- I don't personally use quotas. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
Re: [vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
On Jul 27, 2006, at 8:12 AM, Harm van Tilborg wrote: 1) I'm still running vpopmail 5.2.1 on some servers and it's finally time to upgrade (yes, finally :[). In the UPGRADE instructions it says it shouldn't be a problem (I'm using the cdb auth-module). Is that really true? I think so, but I haven't done an upgrade from 5.2.1 in a long time. 2) And I would like to turn off qmail-ext support in the upgrade. Could that give any problems? If you have users relying on it to get their email, then it will be a problem. Some of my users make use of it to generate unique email addresses (like tom-amazon for all email from amazon.com) that they can later turn into blackhole or bounce addresses. 3) Domain and user quotas are kind of broken, aren't they? The only way to make them work is with the Maildir++-patch, is that true? Domain quotas are definitely broken, and have been disabled in the current release. 4) Will this upgrade change anything to the already set (but not working) quotas? I don't know -- I don't personally use quotas. -- Tom Collins - [EMAIL PROTECTED] Vpopmail - virtual domains for qmail: http://vpopmail.sf.net/ QmailAdmin - web interface for Vpopmail: http://qmailadmin.sf.net/
[vchkpw] Upgrading from 5.2.1, qmail-ext and quotas
Hi all, I'm dubbing with four questions. 1) I'm still running vpopmail 5.2.1 on some servers and it's finally time to upgrade (yes, finally :[). In the UPGRADE instructions it says it shouldn't be a problem (I'm using the cdb auth-module). Is that really true? 2) And I would like to turn off qmail-ext support in the upgrade. Could that give any problems? 3) Domain and user quotas are kind of broken, aren't they? The only way to make them work is with the Maildir++-patch, is that true? 4) Will this upgrade change anything to the already set (but not working) quotas? Kind regards, Harm van Tilborg PS: keep up the great work!
[vchkpw] Upgrading from 5.3.12
Hi, When we had the original Qmail installation (before I got here), we were using the Vpopmail 5.3.12. This was some sort of development release, and I want to upgrade it to the latest stable release, mainly so I can get later version of Qmailadmin installed. What do I need to look at before upgrading? I am running a backup mail server which I built in September which runs a much later release, and the data seems fine in the new installation, however, I just wanted to know what to expect when doing an upgrade from such an old version? Thanks. Andrew. ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. allpay.net Limited, Fortis et Fides, Whitestone Business Park, Whitestone, Hereford, HR1 3SE. Telephone: 0870 243 3434, Fax: 0870 243 6041. Website: www.allpay.net Email: [EMAIL PROTECTED] **
Re: [vchkpw] Upgrading to 5.4.2
Charles J. Boening wrote (at Tue, Jun 07, 2005 at 03:06:27PM -0700): > Check out /var/qmail/users/assign (I think that's it) > > Make sure you copied that file from the old system. And then run /var/qmail/bin/qmail-newu -- Casey Zacek Senior Engineer NeoSpire, Inc.
RE: [vchkpw] Upgrading to 5.4.2
Check out /var/qmail/users/assign (I think that's it) Make sure you copied that file from the old system. Charlie > -Original Message- > From: NW [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 07, 2005 2:29 PM > To: vchkpw@inter7.com > Subject: [vchkpw] Upgrading to 5.4.2 > > >I have an ancient machine running vpopmail 3.4.11, and > would like to replace it with a new machine running 5.4.2. > I'm running into problems migrating the accounts, and would > like to ask for pointers or help. > >I compiled qmail and vpopmail on the new machine, and > verified that the entire setup does work. To migrate the > user accounts, I copied the ~vpopmail/domains directory from > the old machine to the new one, but I get authentication > errors. (Accounts created on the new machine authenticate > just fine, but not the migrated accounts). > >Looking through the vpasswd files, I see there are a few > minor differences in the format, so I massaged the entries > for migrated domains to match, but I still get authentication errors. > >If I try to manipulate migrated accounts, I am told > "Error: Domain does not exist." If anyone can tell me what > I need to do to get the migrated accounts to work, I will be > very grateful! > > NW > > >
[vchkpw] Upgrading to 5.4.2
I have an ancient machine running vpopmail 3.4.11, and would like to replace it with a new machine running 5.4.2. I'm running into problems migrating the accounts, and would like to ask for pointers or help. I compiled qmail and vpopmail on the new machine, and verified that the entire setup does work. To migrate the user accounts, I copied the ~vpopmail/domains directory from the old machine to the new one, but I get authentication errors. (Accounts created on the new machine authenticate just fine, but not the migrated accounts). Looking through the vpasswd files, I see there are a few minor differences in the format, so I massaged the entries for migrated domains to match, but I still get authentication errors. If I try to manipulate migrated accounts, I am told "Error: Domain does not exist." If anyone can tell me what I need to do to get the migrated accounts to work, I will be very grateful! NW
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
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.
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.
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
[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 5.3.30 to 5.4.x
On Fri, 9 Jul 2004, Tom Collins wrote: > The method of passing the CRAM-MD5 challenge and response from > qmail-smtpd to vchkpw has varied in different releases of the SMTP AUTH > patch to qmail-smtpd and the code if vchkpw. Just a quick note, perhaps this should be in the CHANGELOG or something. The new TLS/auth patch has a build target called "tmprsadh". As far as I can tell, this target was not in the old patch. If you do not specifically do a "make tmprsadh", you'll find that your TLS connections take forever to setup; so long that it may appear that something is broken. It's not, it's just some insanely slow encryption process going on. Once you make the target above, you get these additional files in /var/qmail/control: -rw-rw 1 vpopmail qmail 245 Jul 13 01:56 dh1024.pem -rw-rw 1 vpopmail qmail 156 Jul 13 01:51 dh512.pem -rw-rw 1 vpopmail qmail 493 Jul 13 01:51 rsa512.pem While I don't understand enough about TLS/SSL to explain it, having these files speeds things up quite a bit. Charles
Re: [vchkpw] upgrading 5.3.30 to 5.4.x
On Fri, 9 Jul 2004, Tom Collins wrote: > Someone, somewhere determined the proper order (based on documentation, > perhaps related to the chkpasswd(?) program used on non-vpopmail > systems) and the latest (0.42) SMTP AUTH patch and the code in vpopmail > 5.4.0 were both fixed. Excellent. Sounds fair enough. > You should be able to apply your super-patch-pack, then unpatch (patch > -r?) your original SMTP AUTH patch and then apply the latest patch. I looked at what I was doing (this is an old install) and found that Bill Shupp's mega-patch plus chkusr is really all I need. So I started over with netqmail and the latest patchsets. So far all is well under 5.3.30 with the updated qmail, so I'll be giving the upgrade a shot soon. > Hard to say. We started using an external file > (~vpopmail/etc/vpopmail.mysql) to store MySQL settings instead of > having them hard-coded in vmysql.h. Looks like I already had that. > If you've read through the ChangeLog entries, you should have seen any > critical issues. We started supporting valiases in MySQL fully in > vpopmail and qmailadmin (so you can replace aliases, forwards and > autoresponders in .qmail-alias files with MySQL table entries). Looked at each release from 5.3.30 - 5.4.6 and didn't see anything big beyond the smtp-auth issue. Until my db issues are sorted out I'll be declining on the valias stuff. :) I have to give PGSQL a shot sometime as well. It looks like people have been cleaning that up a bit. Thanks, Charles > -- > Tom Collins - [EMAIL PROTECTED] > QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ > Info on the Sniffter hand-held Network Tester: http://sniffter.com/ > >
Re: [vchkpw] upgrading 5.3.30 to 5.4.x
On Jul 9, 2004, at 12:08 PM, Charles Sprickman wrote: Out of curiousity, what has changed? My current super-patch-pack for qmail was quite difficult to put together, so I'm a litle hesitant to try and get the newer smtp-auth patches into that mess. Is there any way to continue with the old patch? What exactly has changed on the vpopmail side that breaks the old patch? The method of passing the CRAM-MD5 challenge and response from qmail-smtpd to vchkpw has varied in different releases of the SMTP AUTH patch to qmail-smtpd and the code if vchkpw. Someone, somewhere determined the proper order (based on documentation, perhaps related to the chkpasswd(?) program used on non-vpopmail systems) and the latest (0.42) SMTP AUTH patch and the code in vpopmail 5.4.0 were both fixed. You should be able to apply your super-patch-pack, then unpatch (patch -r?) your original SMTP AUTH patch and then apply the latest patch. And is there anything else I should be aware of when upgrading? Like I said, I didn't see anything major in the changelogs, but I'd still like to get some feedback from anyone who's made the jump to 5.4.x from 5.3.30. Hard to say. We started using an external file (~vpopmail/etc/vpopmail.mysql) to store MySQL settings instead of having them hard-coded in vmysql.h. If you've read through the ChangeLog entries, you should have seen any critical issues. We started supporting valiases in MySQL fully in vpopmail and qmailadmin (so you can replace aliases, forwards and autoresponders in .qmail-alias files with MySQL table entries). -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [vchkpw] upgrading 5.3.30 to 5.4.x
Charles Sprickman wrote: Hi, I've been looking through the release notes on all post 5.3.30 releases and so far I don't see any big "gotchas" except for this: http://marc.theaimsgroup.com/?t=10747937905&r=1&w=2 Out of curiousity, what has changed? My current super-patch-pack for qmail was quite difficult to put together, so I'm a litle hesitant to try and get the newer smtp-auth patches into that mess. Is there any way to continue with the old patch? What exactly has changed on the vpopmail side that breaks the old patch? And is there anything else I should be aware of when upgrading? Like I said, I didn't see anything major in the changelogs, but I'd still like to get some feedback from anyone who's made the jump to 5.4.x from 5.3.30. Hi, I have done three machines recently from 5.3.20 to 5.4.5 and I experienced no problems. Two machines used cdb and one used MySQL. I did it all based on Bill Shupp's patches, so I had no worries about my own patches. Regards, Rick
[vchkpw] upgrading 5.3.30 to 5.4.x
Hi, I've been looking through the release notes on all post 5.3.30 releases and so far I don't see any big "gotchas" except for this: http://marc.theaimsgroup.com/?t=10747937905&r=1&w=2 Out of curiousity, what has changed? My current super-patch-pack for qmail was quite difficult to put together, so I'm a litle hesitant to try and get the newer smtp-auth patches into that mess. Is there any way to continue with the old patch? What exactly has changed on the vpopmail side that breaks the old patch? And is there anything else I should be aware of when upgrading? Like I said, I didn't see anything major in the changelogs, but I'd still like to get some feedback from anyone who's made the jump to 5.4.x from 5.3.30. Thanks, Charles
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
On Monday 07 June 2004 3:08 pm, Rick Widmer wrote: > Jeremy Kitchen wrote: > > On Monday 07 June 2004 02:22 pm, Jeremy Kitchen wrote: > >>>As an ex-database admin, I wrote the many-domains=no option as > >>>an optimization to the database schema to save disk space. > >>> > >>>Consider hosting one domain with 1 million email accounts. > >>>The pw_domain(64 char) field is redundant (only one domain). So > >>>we would be wasting 64MB of space in the database. So instead > >>>the table is named after the domain. > >> > >>I was about to ask you this but you ran off before I could.. so I'll just > >>post for discussion purposes. > >> > >>Isn't this what the varchar field is for? > > Yes it is, but the current database layout uses char fields. Still if > you have one domain with 1 million accounts, you have at least 4MB of > duplicated domain names, if the domain name is a.au, better than the > 64MB the current char field would use, but not as good as 0 bytes if the > table is named for the domain and you don't store the domain name at > all. It is interesting in theory, but there probably aren't many sites > like this. > > It does bring up an interesting question... would it be a good idea to > change from char to varchar for all the fields? Standard database design says to *never* use varchars. And if you do use them, you better have a darn good reason. It's easy to spot a newbie doing database design, all fields are varchars. Varchars make it very difficult for the SQL engine to optimize disk to memory paging. Which in practice means no optimization for tables with varchars. When each row is a fixed length, the engine can calculate how many rows will fit in a memory block. Then it can do one disk read per memory block (this is the optimization). With varchar fields the engine needs to read in a section of disk into a temporary memory buffer. Then parse the varchar lengths to calculate row lengths, one row at a time. The end result is more disk reads. And disk I/O is the bottleneck in databases. So it all boils down to significant performance improvements of fixed lenght rows over variable lenght rows. > It should give a > substantial reduction in database size, and I don't think it will be > that much slower. > Someone _should_ be able to do an alter table and > find out if anything breaks... > > > Rick > > p.s. It does bring up a real question - does anyone actually use > separate tables for each domain anymore? It would be nice if we could > remove the option some day. (It causes a number of four state ifdef > structures that are kind of messy.) I know what you mean. I kinda wish I never wrote the two versions. But removing it would break backward compatibility. Ken
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
On Monday 07 June 2004 03:08 pm, Rick Widmer wrote: > Jeremy Kitchen wrote: > > On Monday 07 June 2004 02:22 pm, Jeremy Kitchen wrote: > >>>As an ex-database admin, I wrote the many-domains=no option as > >>>an optimization to the database schema to save disk space. > >>> > >>>Consider hosting one domain with 1 million email accounts. > >>>The pw_domain(64 char) field is redundant (only one domain). So > >>>we would be wasting 64MB of space in the database. So instead > >>>the table is named after the domain. > >> > >>I was about to ask you this but you ran off before I could.. so I'll just > >>post for discussion purposes. > >> > >>Isn't this what the varchar field is for? > > Yes it is, but the current database layout uses char fields. Still if > you have one domain with 1 million accounts, you have at least 4MB of > duplicated domain names, if the domain name is a.au, better than the > 64MB the current char field would use, but not as good as 0 bytes if the > table is named for the domain and you don't store the domain name at > all. It is interesting in theory, but there probably aren't many sites > like this. ahh good point. My thought is though, if you have a million users, 4 megs of extra 'wasted' space (even 64 megs) is trivial. I think people with a million users are more concerned about speed than fretting over a few megs of lost space :) > It does bring up an interesting question... would it be a good idea to > change from char to varchar for all the fields? It should give a > substantial reduction in database size, and I don't think it will be > that much slower. Someone _should_ be able to do an alter table and > find out if anything breaks... yea, I don't think that would break anything. Unfortunately I don't have a machine to try that on (other than a few production servers but I'm sure they'd shoot me if I broke them *grins*) > p.s. It does bring up a real question - does anyone actually use > separate tables for each domain anymore? It would be nice if we could > remove the option some day. (It causes a number of four state ifdef > structures that are kind of messy.) I know when I set up mysql backends I leave it at the default, I would assume that most people also do (unless they really know what they're doing, in which case they probably need the single table anyways for performance reasons) -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
Jeremy Kitchen wrote: On Monday 07 June 2004 02:22 pm, Jeremy Kitchen wrote: As an ex-database admin, I wrote the many-domains=no option as an optimization to the database schema to save disk space. Consider hosting one domain with 1 million email accounts. The pw_domain(64 char) field is redundant (only one domain). So we would be wasting 64MB of space in the database. So instead the table is named after the domain. I was about to ask you this but you ran off before I could.. so I'll just post for discussion purposes. Isn't this what the varchar field is for? Yes it is, but the current database layout uses char fields. Still if you have one domain with 1 million accounts, you have at least 4MB of duplicated domain names, if the domain name is a.au, better than the 64MB the current char field would use, but not as good as 0 bytes if the table is named for the domain and you don't store the domain name at all. It is interesting in theory, but there probably aren't many sites like this. It does bring up an interesting question... would it be a good idea to change from char to varchar for all the fields? It should give a substantial reduction in database size, and I don't think it will be that much slower. Someone _should_ be able to do an alter table and find out if anything breaks... Rick p.s. It does bring up a real question - does anyone actually use separate tables for each domain anymore? It would be nice if we could remove the option some day. (It causes a number of four state ifdef structures that are kind of messy.)
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
On Monday 07 June 2004 02:22 pm, Jeremy Kitchen wrote: > > As an ex-database admin, I wrote the many-domains=no option as > > an optimization to the database schema to save disk space. > > > > Consider hosting one domain with 1 million email accounts. > > The pw_domain(64 char) field is redundant (only one domain). So > > we would be wasting 64MB of space in the database. So instead > > the table is named after the domain. > > I was about to ask you this but you ran off before I could.. so I'll just > post for discussion purposes. > > Isn't this what the varchar field is for? or rather, field TYPE. -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
On Monday 07 June 2004 02:20 pm, Ken Jones wrote: > On Monday 07 June 2004 2:01 pm, Jeremy Kitchen wrote: > > On Monday 07 June 2004 01:39 pm, Martin Leduc wrote: > > > Can you tel me quickly what is the difference between > > > enabled-many-domain=y and =n? > > > > as far as I know it only affects sql (mysql only?) backends, as with > > --enable-many-domains=y (default) it uses one table with all of the > > information, and with it =n it uses one table per domain. > > > > Someone who has actually dug through the code (Tom?, Michael?, Ken?) > > might be able to give you a more definite example, but from my experience > > that's the main difference. > > > > I think --enable-large-site (or similar) is what enables/disables the > > directory hashing, but don't quote me on that. > > As an ex-database admin, I wrote the many-domains=no option as > an optimization to the database schema to save disk space. > > Consider hosting one domain with 1 million email accounts. > The pw_domain(64 char) field is redundant (only one domain). So > we would be wasting 64MB of space in the database. So instead > the table is named after the domain. I was about to ask you this but you ran off before I could.. so I'll just post for discussion purposes. Isn't this what the varchar field is for? -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
On Monday 07 June 2004 2:01 pm, Jeremy Kitchen wrote: > On Monday 07 June 2004 01:39 pm, Martin Leduc wrote: > > Can you tel me quickly what is the difference between > > enabled-many-domain=y and =n? > > as far as I know it only affects sql (mysql only?) backends, as with > --enable-many-domains=y (default) it uses one table with all of the > information, and with it =n it uses one table per domain. > > Someone who has actually dug through the code (Tom?, Michael?, Ken?) might > be able to give you a more definite example, but from my experience that's > the main difference. > > I think --enable-large-site (or similar) is what enables/disables the > directory hashing, but don't quote me on that. As an ex-database admin, I wrote the many-domains=no option as an optimization to the database schema to save disk space. Consider hosting one domain with 1 million email accounts. The pw_domain(64 char) field is redundant (only one domain). So we would be wasting 64MB of space in the database. So instead the table is named after the domain. On the other hand, consider hosting 700 domains. Mysql would have to access 700 tables. Mysql uses file descriptors for each table. In production, we saw mysql opening and closing file descriptors as it tried to share it's available file descriptors across sql queries, which seriously impacted performance. On this type of system, it we got better performance by putting all the data into one table. The end result after performance testing was the single table setup was the best for all servers, except for the case where there are 1 (or a few) domains with many-many email accounts. Hence we made "many domains" the default option. Ken Jones
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
On Monday 07 June 2004 01:39 pm, Martin Leduc wrote: > Can you tel me quickly what is the difference between enabled-many-domain=y > and =n? as far as I know it only affects sql (mysql only?) backends, as with --enable-many-domains=y (default) it uses one table with all of the information, and with it =n it uses one table per domain. Someone who has actually dug through the code (Tom?, Michael?, Ken?) might be able to give you a more definite example, but from my experience that's the main difference. I think --enable-large-site (or similar) is what enables/disables the directory hashing, but don't quote me on that. -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
Can you tel me quickly what is the difference between enabled-many-domain=y and =n? it's only the one "table per domain" when "no" is enabled ? Best Regards Martin From: Jeremy Kitchen <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL Date: Mon, 7 Jun 2004 11:40:00 -0500 On Monday 07 June 2004 11:33 am, Martin Leduc wrote: > Thank you, thats working :) great. > Now I need to make a pre-production test. ok. > I would like to copy my vpopmail/domains dir and my Database to my DEVEL > server. ok. > Did I need other files? Like in the Qmail config? the users/ and control/ directories for qmail. -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
On Monday 07 June 2004 11:33 am, Martin Leduc wrote: > Thank you, thats working :) great. > Now I need to make a pre-production test. ok. > I would like to copy my vpopmail/domains dir and my Database to my DEVEL > server. ok. > Did I need other files? Like in the Qmail config? the users/ and control/ directories for qmail. -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
Thank you, thats working :) Now I need to make a pre-production test. I would like to copy my vpopmail/domains dir and my Database to my DEVEL server. Did I need other files? Like in the Qmail config? Martin From: Jeremy Kitchen <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL Date: Mon, 7 Jun 2004 11:00:59 -0500 On Monday 07 June 2004 10:13 am, Martin Leduc wrote: > Hi, > > I tried to upgrade the Vpopmail software but something is not work > correctly. We used the MySQL AUTH Module. > > If I read from the UPGRADE documentation, I read: > > --- Upgrading to 5.4 from 5.3.x or 5.2.x is straight forward. > > We dont have enabled many-domain, so we have a problem. right. > By default, the option enabled-many-domain is now enabled. as it should be. [snip confusing problem with simple workaround-ish solution] I would *highly* recommend going into your old source directory (hopefully you kept it around) and use 'vconvert' to pull your existing data from mysql into vpasswd files. Then, using the new binaries you have, use vconvert again to put the existing data back into the database in the structure it needs (I would highly recommend --enable-many-domains) That's the easiest way out of this mess for you, and shouldn't take but a minute or two. You don't even have to replace any binaries or anything, just run it where it stands. -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/
Re: [vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
On Monday 07 June 2004 10:13 am, Martin Leduc wrote: > Hi, > > I tried to upgrade the Vpopmail software but something is not work > correctly. We used the MySQL AUTH Module. > > If I read from the UPGRADE documentation, I read: > > --- Upgrading to 5.4 from 5.3.x or 5.2.x is straight forward. > > We dont have enabled many-domain, so we have a problem. right. > By default, the option enabled-many-domain is now enabled. as it should be. [snip confusing problem with simple workaround-ish solution] I would *highly* recommend going into your old source directory (hopefully you kept it around) and use 'vconvert' to pull your existing data from mysql into vpasswd files. Then, using the new binaries you have, use vconvert again to put the existing data back into the database in the structure it needs (I would highly recommend --enable-many-domains) That's the easiest way out of this mess for you, and shouldn't take but a minute or two. You don't even have to replace any binaries or anything, just run it where it stands. -Jeremy -- Jeremy Kitchen ++ Systems Administrator ++ Inter7 Internet Technologies, Inc. [EMAIL PROTECTED] ++ www.inter7.com ++ 866.528.3530 ++ 847.492.0470 int'l kitchen @ #qmail #gentoo on EFnet ++ scriptkitchen.com/qmail
[vchkpw] Upgrading from 5.2.1 to 5.4.0 with MySQL
Hi, I tried to upgrade the Vpopmail software but something is not work correctly. We used the MySQL AUTH Module. If I read from the UPGRADE documentation, I read: --- Upgrading to 5.4 from 5.3.x or 5.2.x is straight forward. We dont have enabled many-domain, so we have a problem. By default, the option enabled-many-domain is now enabled. It's ok when I specified --enabled-many-domain = n. I can do a vdominfo query. But when I try vuserinfo, this is the error: [EMAIL PROTECTED]:/home/vpopmail/bin# ~vpopmail/bin/vuserinfo [EMAIL PROTECTED] vmysql: sql error[3]: Table 'vpopmail.test.com' doesn't exist no such user [EMAIL PROTECTED] This is my ./configure options: --enable-clear-passwd=y \ --enable-valias=y \ --enable-mysql-logging=y \ --enable-sqwebmail-pass=y \ --enable-domains-dir=domains \ --enable-auth-module=mysql \ --enable-incdir=/usr/local/mysql/include/ \ --enable-libdir=/usr/local/mysql/lib/ \ --enable-many-domains=n \ --disable-users-big-dir I tried with and without --disable-users-big-dir, same result. We used mysql 4.0.20, new upgraded ;). Thanks for Help. Martin _ MSN Search, le moteur de recherche qui pense comme vous ! http://fr.ca.search.msn.com/
Re: [vchkpw] Upgrading the MySQL, I crask my vpopmail :(
On mié, 2004-05-19 at 19:22, Rick Widmer wrote: > > > Tom Collins wrote: > > > On May 19, 2004, at 12:25 PM, Luciano Bello wrote: > > > >> With the command line client, now I need to write the '-h > >> 127.0.0.1'. In vchkpw/etc/vpopmail.mysql i have > >> localhost|3306|root||vpopmail > > > > > > Try replacing 'localhost' with '127.0.0.1'. I seem to recall reading > > somewhere that MySQL would use a socket connection (in the file system) > > instead of a TCP connection when given localhost. Using 127.0.0.1 > > forces the use of TCP. > > While that is a good idea for a test, if you find it works with > 127.0.0.1 and not localhost, you should then find out what is wrong with > the socket connection. If you are running qmailadmin and MySQL on the > same machine, the socket connection via 'localhost' will be faster. > > Usually it is permission on or above the directory where the socket is > located, or a mismatch between where a distribution specific MySQL > install, and a user compiled version place the socket. Does the MySQL > command line program work with localhost connections when run by the web > server user? Is there more than one version of MySQL installed on the > machine? > > Rick No... i just have one MySQL server.
Re: [vchkpw] Upgrading the MySQL, I crask my vpopmail :(
Tom Collins wrote: On May 19, 2004, at 12:25 PM, Luciano Bello wrote: With the command line client, now I need to write the '-h 127.0.0.1'. In vchkpw/etc/vpopmail.mysql i have localhost|3306|root||vpopmail Try replacing 'localhost' with '127.0.0.1'. I seem to recall reading somewhere that MySQL would use a socket connection (in the file system) instead of a TCP connection when given localhost. Using 127.0.0.1 forces the use of TCP. While that is a good idea for a test, if you find it works with 127.0.0.1 and not localhost, you should then find out what is wrong with the socket connection. If you are running qmailadmin and MySQL on the same machine, the socket connection via 'localhost' will be faster. Usually it is permission on or above the directory where the socket is located, or a mismatch between where a distribution specific MySQL install, and a user compiled version place the socket. Does the MySQL command line program work with localhost connections when run by the web server user? Is there more than one version of MySQL installed on the machine? Rick
Re: [vchkpw] Upgrading the MySQL, I crask my vpopmail :(
Thx for your help...was really usefull Cheers Luciano El mié, 19-05-2004 a las 16:44, Tom Collins escribió: > On May 19, 2004, at 12:25 PM, Luciano Bello wrote: > > With the command line client, now I need to write the '-h > > 127.0.0.1'. In vchkpw/etc/vpopmail.mysql i have > > localhost|3306|root||vpopmail > > Try replacing 'localhost' with '127.0.0.1'. I seem to recall reading > somewhere that MySQL would use a socket connection (in the file system) > instead of a TCP connection when given localhost. Using 127.0.0.1 > forces the use of TCP. > > -- > Tom Collins - [EMAIL PROTECTED] > QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ > Info on the Sniffter hand-held Network Tester: http://sniffter.com/ > >
Re: [vchkpw] Upgrading the MySQL, I crask my vpopmail :(
On May 19, 2004, at 12:25 PM, Luciano Bello wrote: With the command line client, now I need to write the '-h 127.0.0.1'. In vchkpw/etc/vpopmail.mysql i have localhost|3306|root||vpopmail Try replacing 'localhost' with '127.0.0.1'. I seem to recall reading somewhere that MySQL would use a socket connection (in the file system) instead of a TCP connection when given localhost. Using 127.0.0.1 forces the use of TCP. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
Re: [vchkpw] Upgrading the MySQL, I crask my vpopmail :(
sorry, forget about it. vpopmail connects to mysql using a socket. check if vpopmail is accessing mysql through a tcp socket and that mysql is listening on a tcp socket aswell. IIRC, on Debian, mysql's default is UNIX socket only. Regards, Celso Celso Pinto wrote: Try to recompile vpopmail. Luciano Bello wrote: Hi! I have a Debian system. I had mysql 3.23.49-8 from my apt-get of my Woody. I downloaded and instaled, previous remove the old mysql and dumped the all databases, the mysql-standard-4.0.18-pc-linux-i686. I restore de backup-dump. All my aplication with access to the sql database work well, except vpopmail. When I try to check a mailbox from there I get an error which says, in a Outlook Express:'could not create vlog table CREATE TABLE vlog [...]'. I have this table. With the command line client, now I need to write the '-h 127.0.0.1'. In vchkpw/etc/vpopmail.mysql i have localhost|3306|root||vpopmail Any Idea? Sorry for my english Luciano Bello
Re: [vchkpw] Upgrading the MySQL, I crask my vpopmail :(
Try to recompile vpopmail. Luciano Bello wrote: Hi! I have a Debian system. I had mysql 3.23.49-8 from my apt-get of my Woody. I downloaded and instaled, previous remove the old mysql and dumped the all databases, the mysql-standard-4.0.18-pc-linux-i686. I restore de backup-dump. All my aplication with access to the sql database work well, except vpopmail. When I try to check a mailbox from there I get an error which says, in a Outlook Express:'could not create vlog table CREATE TABLE vlog [...]'. I have this table. With the command line client, now I need to write the '-h 127.0.0.1'. In vchkpw/etc/vpopmail.mysql i have localhost|3306|root||vpopmail Any Idea? Sorry for my english Luciano Bello
[vchkpw] Upgrading the MySQL, I crask my vpopmail :(
Hi! I have a Debian system. I had mysql 3.23.49-8 from my apt-get of my Woody. I downloaded and instaled, previous remove the old mysql and dumped the all databases, the mysql-standard-4.0.18-pc-linux-i686. I restore de backup-dump. All my aplication with access to the sql database work well, except vpopmail. When I try to check a mailbox from there I get an error which says, in a Outlook Express:'could not create vlog table CREATE TABLE vlog [...]'. I have this table. With the command line client, now I need to write the '-h 127.0.0.1'. In vchkpw/etc/vpopmail.mysql i have localhost|3306|root||vpopmail Any Idea? Sorry for my english Luciano Bello
RE: [vchkpw] Upgrading vpopmail
> Christian Reeves wrote: >> I am/was running vpopmail 5.2.1 and want to upgrade to 5.4.3. >> I read the FAQ about upgrading and it seems pretty straightforward. I >> backup up the recommended dir's, downloaded the latest stable release, >> compiled with the same options I did when installing the current >> running version, did make, then make stripNow, the touch times on >> /vpop/bin/* indicate the files were replaced by the newer version's >> files but I'm not so sure I got the job done. All seems to be working fine >> though. >> >> 1. How do I know definitivley that I'm runnin the newer version? >> 2. qmailadmin reports the older version on it's login screen. Is this >> a sign the upgrade didn't take? >> > > No, its a sign that you didnt recompile qmailadmin like your supposed to. that did it...thanks! Turns out ther bug still exists but Ill search the FAQ's before posting about that one.
RE: [vchkpw] Upgrading vpopmail
> Christian Reeves wrote: >> I am/was running vpopmail 5.2.1 and want to upgrade to 5.4.3. >> I read the FAQ about upgrading and it seems pretty straightforward. I >> backup up the recommended dir's, downloaded the latest stable release, >> compiled with the same options I did when installing the current >> running version, did make, then make stripNow, the touch times on >> /vpop/bin/* indicate the files were replaced by the newer version's >> files but I'm not so sure I got the job done. All seems to be working fine >> though. >> >> 1. How do I know definitivley that I'm runnin the newer version? >> 2. qmailadmin reports the older version on it's login screen. Is this >> a sign the upgrade didn't take? >> > > No, its a sign that you didnt recompile qmailadmin like your supposed to. that did it...thanks! Turns out ther bug still exists but Ill search the FAQ's before posting about that one.
RE: [vchkpw] Upgrading vpopmail
> Christian Reeves wrote: >> I am/was running vpopmail 5.2.1 and want to upgrade to 5.4.3. >> I read the FAQ about upgrading and it seems pretty straightforward. I >> backup up the recommended dir's, downloaded the latest stable release, >> compiled with the same options I did when installing the current >> running version, did make, then make stripNow, the touch times on >> /vpop/bin/* indicate the files were replaced by the newer version's >> files but I'm not so sure I got the job done. All seems to be working fine >> though. >> >> 1. How do I know definitivley that I'm runnin the newer version? >> 2. qmailadmin reports the older version on it's login screen. Is this >> a sign the upgrade didn't take? >> > > No, its a sign that you didnt recompile qmailadmin like your supposed to. that did it...thanks! Turns out ther bug still exists but Ill search the FAQ's before posting about that one.
Re: [vchkpw] Upgrading vpopmail
Christian Reeves wrote: I am/was running vpopmail 5.2.1 and want to upgrade to 5.4.3. I read the FAQ about upgrading and it seems pretty straightforward. I backup up the recommended dir's, downloaded the latest stable release, compiled with the same options I did when installing the current running version, did make, then make stripNow, the touch times on /vpop/bin/* indicate the files were replaced by the newer version's files but I'm not so sure I got the job done. All seems to be working fine though. 1. How do I know definitivley that I'm runnin the newer version? 2. qmailadmin reports the older version on it's login screen. Is this a sign the upgrade didn't take? No, its a sign that you didnt recompile qmailadmin like your supposed to. I did the upgrade to overcome a bug I've posted about but never received a response on. The bug is that when I run 'vdeldomain', it deletes the domain fine but then the permissions on /var/qmail/control/rcpthosts gets changed to 600. Weird...so I though getting the newest release would be a good place to start. Christian
Re: [vchkpw] Upgrading vpopmail
On Friday 09 April 2004 16:16, Christian Reeves wrote: > 1. How do I know definitivley that I'm runnin the newer version? # ~vpopmail/bin/vadduser -v version: 5.4.0 -- Cristiano Deana - FreeCRIS "Ho iniziato a usare FreeBSD perche' m$ usava me. ed e' spiacevole" crisBSD in irc su: irc.azzurra.org #freebsd-it #qmail-it
[vchkpw] Upgrading vpopmail
I am/was running vpopmail 5.2.1 and want to upgrade to 5.4.3. I read the FAQ about upgrading and it seems pretty straightforward. I backup up the recommended dir's, downloaded the latest stable release, compiled with the same options I did when installing the current running version, did make, then make stripNow, the touch times on /vpop/bin/* indicate the files were replaced by the newer version's files but I'm not so sure I got the job done. All seems to be working fine though. 1. How do I know definitivley that I'm runnin the newer version? 2. qmailadmin reports the older version on it's login screen. Is this a sign the upgrade didn't take? I did the upgrade to overcome a bug I've posted about but never received a response on. The bug is that when I run 'vdeldomain', it deletes the domain fine but then the permissions on /var/qmail/control/rcpthosts gets changed to 600. Weird...so I though getting the newest release would be a good place to start. Christian
Re: [vchkpw] Upgrading
fredagen den 12 december 2003 06.10 skrev Tom Collins: > On Thursday, December 11, 2003, at 05:09 PM, Rob G wrote: > > But the other question what would be the easiest way to figure out what > > switches I used to install these products in the first place. I did > > this > > about 6 months ago and now can't remember what switches I used. > > If you still have the source directory you installed from, you can find > the options you used by reading the beginning of the config.status file. Something for the FAQ? Add this too: Q: I don't know what version I have installed. A. Examine the /home/vpopmail/include/config.h file. Q. I have forgot how it was compiled. A. Examine the /home/vpopmail/include/config.h file.
Re: [vchkpw] Upgrading
On Thursday, December 11, 2003, at 05:09 PM, Rob G wrote: But the other question what would be the easiest way to figure out what switches I used to install these products in the first place. I did this about 6 months ago and now can't remember what switches I used. If you still have the source directory you installed from, you can find the options you used by reading the beginning of the config.status file. -- Tom Collins - [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
[vchkpw] Squirrel and config switches Was: Re: [vchkpw] Upgrading
> .. Also want to upgrade squirrelmail but I think >that should be pretty straight forward. It is Rob.. as long as (Courier-)IMAP is in and running, Squirrelmail seem to work quite happily with vpopmail. > But the other question what would be the easiest way > to figure out what switches I used to install these >products in the first place. Check for a 'configure.status' file in the source directory ( asuming you kept you source directrory that is.. ). This allows you to check and duplicate the previous install. Regards, Chris. __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/
Re: [vchkpw] Upgrading
Actually I forgot a couple questions to ask .. ooops .. Also want to upgrade squirrelmail but I think that should be pretty straight forward. But the other question what would be the easiest way to figure out what switches I used to install these products in the first place. I did this about 6 months ago and now can't remember what switches I used. Rob - Original Message - From: "Rob G" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, December 11, 2003 7:00 PM Subject: [vchkpw] Upgrading > Hello All, > > I am looking at upgrading to the latest stables of vpopmail and qmailadmin, > and I am just wondering what would be the recommended way of doing this? > > Regards, > Rob G > [EMAIL PROTECTED] > > > > >
[vchkpw] Upgrading
Hello All, I am looking at upgrading to the latest stables of vpopmail and qmailadmin, and I am just wondering what would be the recommended way of doing this? Regards, Rob G [EMAIL PROTECTED]
Re: [vchkpw] Upgrading from 5.3.20 to 5.3.28
Eduardo M. Bragatto wrote: What do I need to know before upgrading from this version to that one?! Is there any changes that I need to do about? I'm using CDB to store users/passes. Eduardo, A while ago I upgraded from 5.3.20 to 5.3.27 and recently to 5.3.28. The upgrade was easy and hassle-free. The only thing that kept me busy was the smtp-auth patch I applied to qmail-smtpd, and that's not vpopmail's fault. After the upgrade, I wasn't able to send out mail anymore, all I got were authentication errors. In order to authenticate with vchkpw, the program must be setuid root. After a "make install-strip", the newly installed version lost these rights. A simple "chmod 4755 ~vpopmail/bin/vchkpw && chown root.root ~vpopmail/bin/vchkpw" solved that. Regards Jochen
[vchkpw] Upgrading from 5.3.20 to 5.3.28
What do I need to know before upgrading from this version to that one?! Is there any changes that I need to do about? I'm using CDB to store users/passes. Eduardo M. Bragatto
[vchkpw] Upgrading from vpopmail 4.9.6 to something modern?
I installed vpopmail-4.9.6 with qmail on an ISP I support over three years ago. Been running great but now, after a crash, POP is reporting the client crashed. I have been unable to diagnose the problem. I've rebuilt the OS (FreeBSD-4.2-RELEASE) and kernel, but no improvement. I could build and install the latest vpopmail but recall on the lists -- probably over a year ago, maybe with the 5.x series -- that there was some conversion necessary in some files. Any pointers? I don't see anything on inter7's site nor sorceforge's release notes on how to upgrade. Obviously, I don't want to lose the virtual domains and users' mail :-( Thanks for any tips or pointers to docs.
Re: [vchkpw] upgrading from mysql 3.23 to 4.x
well at least you should follow the instructions in mysql site to convert your tables etc. I didnt do it but just read :) it is good to read. so only install would perhaps work but they suggest you to convert, since the old table formats will be absolute in 5.x version On Mon, 11 Aug 2003, Paul Theodoropoulos wrote: > has anyone made the migration with vpopmail from mysql 3.23 to 4.x? if so, > are there any 'gotchas', or is it as simple as installing the latest mysql > and restarting? > > > Paul Theodoropoulos > http://www.anastrophe.com > > > >
[vchkpw] upgrading from mysql 3.23 to 4.x
has anyone made the migration with vpopmail from mysql 3.23 to 4.x? if so, are there any 'gotchas', or is it as simple as installing the latest mysql and restarting? Paul Theodoropoulos http://www.anastrophe.com
Re: [vchkpw] RE : [vchkpw] Upgrading Vpopmail to 5.2.1 and Auth Now Fa
G'Day Alex, Yes i can telnet to host:110, but the auth for my pass always fails until i revert to the old vchkpw file... ie the new vchkpw doesn't seem to be able to read the old vpasswd.cdb file...for the domains... Nathan > What then is the problem you are having? > > can you 'telnet mail.you.com 110'? > > I did not see where you said that you having trouble authenticating with > POP. > > -alex > > - Original Message - > From: "Nathan Chan" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, December 30, 2002 7:58 PM > Subject: [vchkpw] RE : [vchkpw] Upgrading Vpopmail to 5.2.1 and Auth Now Fa > > > Alex, > > > I had to 'chown root.root /home/vpopmail/bin/vchkpw'. > > > Will check this. > > No go. My previous version of vchkpw was vpopmail:vchkpw and so was my new > version. I tried it root:root but still no go. > > Nathan > > > > > > > > > > > >
[vchkpw] RE : [vchkpw] Upgrading Vpopmail to 5.2.1 and Auth Now Fa
Alex, > I had to 'chown root.root /home/vpopmail/bin/vchkpw'. > Will check this. No go. My previous version of vchkpw was vpopmail:vchkpw and so was my new version. I tried it root:root but still no go. Nathan
Re: [vchkpw] Upgrading Vpopmail to 5.2.1 and Auth Now Fails
G'Day Alex, > 1) > I had to 'chown root.root /home/vpopmail/bin/vchkpw'. Will check this. > 2) Also, try this: > > make the 'authmodulelist=' line in > /usr/local/sqwebmail/authdaemonrc look like: > authmodulelist="authvchkpw" > > Because I think sqwebmail gets confused if authvchkpw is not first in the > list, as earlier entries take precedence for authorization, and any othe > authmodules you may have compiled may be complicating the situation. See > next suggestion. Not even worrying about sqwebmail at the moment. Normal popping in doesn't work, so i didn't even get that far as to test the sqwebmail part.. > 3) > > /usr/local/src/vpopmail-5.2.1# ./configure --help |grep sqwebmail : > " --enable-sqwebmail-pass=y|n Turn on support for sqwebmail passwords (y) > or off (n) default is no. For sqwebmail-3.0 and above use default no" > Hmm? > > Try to explicitly set all configure options, especially auth options for > both sqwebmail and vpopmail: Again not even worried about the sqwebmail part yet.. > /usr/local/src/vpopmail-5.2.1# ./configure --help > /usr/local/src/sqwebmail-3.4.0.20021223# ./configure --help > > like for sqwebmail: > ./configure --with-(only module you need probably > authvchkpw) --without-(everything you dont need) > and etc for vpopmail. > > These suggestions may help. Please let me know if they do. > > [EMAIL PROTECTED] Regards Nathan > > - Original Message - > >From: "Nathan Chan" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Monday, December 30, 2002 4:57 PM > >Subject: [vchkpw] Upgrading Vpopmail to 5.2.1 and Auth Now Fails > > > > >G'Day All, > > > >I have had a stable and working qmail + vpopmail + qmailadmin + > >sqwebmail system running for some 2 years now except for one > >little prob under sqwebmail for quota's. Upon reading some info i > >believe this quirk is now gone under sqwebmail in the new versions > >but to do that upgrade of course i need to upgrade vpopmail, which > >was fine, except that the new version won't auth anyone with the > >new vchkpw... > > > >Info for system below : > >Qmail 1.03 (of course) > >vpopmail-3.4.11-1 > > > >my configure line for the new vpopmail (5.2.1) is : > >./configure --enable-ip-alias-domains=y --enable-logging=e --enable- > >vpopuser=vpopmail --enable-md5-passwords=y --enable- > >defaultquota=20M --enable-clear-passwd=n > > > >(i have tried with enable-clear-passwd=y but no difference.) > > > >I run Qmail under tcpserver as follows : > >tcpserver -R -H 0 pop3 /var/qmail/bin/qmail-popup > >domainxyz.com.au /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail- > >pop3d Maildir& > > > >The domains all have their vpasswd/vpasswd.cdb files, but for some > >reason when i update the vchkpw it fails to auth. As soon as i > >revert no probs. > > > >Any help would be greatly appreciated. > > > >Thanks > >Nathan > > > > > >Out the 100TX, through the switch, down the cable modem, over the fiber > >optics, off the bridge, past the head end office nothing but 'Net. > > > > > > > > > > >
Re: [vchkpw] Upgrading Vpopmail to 5.2.1 and Auth Now Fails
Hello, I recently setup a vpopmail + qmail + sqwebmail box. NOTE: I may be confusing some of the following suggestions with courier-imap install issues I had. Sorry if im off here. 1) I had to 'chown root.root /home/vpopmail/bin/vchkpw'. 2) Also, try this: make the 'authmodulelist=' line in /usr/local/sqwebmail/authdaemonrc look like: authmodulelist="authvchkpw" Because I think sqwebmail gets confused if authvchkpw is not first in the list, as earlier entries take precedence for authorization, and any othe authmodules you may have compiled may be complicating the situation. See next suggestion. 3) /usr/local/src/vpopmail-5.2.1# ./configure --help |grep sqwebmail : " --enable-sqwebmail-pass=y|n Turn on support for sqwebmail passwords (y) or off (n) default is no. For sqwebmail-3.0 and above use default no" Hmm? Try to explicitly set all configure options, especially auth options for both sqwebmail and vpopmail: /usr/local/src/vpopmail-5.2.1# ./configure --help /usr/local/src/sqwebmail-3.4.0.20021223# ./configure --help like for sqwebmail: ./configure --with-(only module you need probably authvchkpw) --without-(everything you dont need) and etc for vpopmail. These suggestions may help. Please let me know if they do. [EMAIL PROTECTED] - Original Message - >From: "Nathan Chan" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Monday, December 30, 2002 4:57 PM >Subject: [vchkpw] Upgrading Vpopmail to 5.2.1 and Auth Now Fails > >G'Day All, > >I have had a stable and working qmail + vpopmail + qmailadmin + >sqwebmail system running for some 2 years now except for one >little prob under sqwebmail for quota's. Upon reading some info i >believe this quirk is now gone under sqwebmail in the new versions >but to do that upgrade of course i need to upgrade vpopmail, which >was fine, except that the new version won't auth anyone with the >new vchkpw... > >Info for system below : >Qmail 1.03 (of course) >vpopmail-3.4.11-1 > >my configure line for the new vpopmail (5.2.1) is : >./configure --enable-ip-alias-domains=y --enable-logging=e --enable- >vpopuser=vpopmail --enable-md5-passwords=y --enable- >defaultquota=20M --enable-clear-passwd=n > >(i have tried with enable-clear-passwd=y but no difference.) > >I run Qmail under tcpserver as follows : >tcpserver -R -H 0 pop3 /var/qmail/bin/qmail-popup >domainxyz.com.au /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail- >pop3d Maildir& > >The domains all have their vpasswd/vpasswd.cdb files, but for some >reason when i update the vchkpw it fails to auth. As soon as i >revert no probs. > >Any help would be greatly appreciated. > >Thanks >Nathan > > >Out the 100TX, through the switch, down the cable modem, over the fiber >optics, off the bridge, past the head end office nothing but 'Net.
[vchkpw] Upgrading Vpopmail to 5.2.1 and Auth Now Fails
G'Day All, I have had a stable and working qmail + vpopmail + qmailadmin + sqwebmail system running for some 2 years now except for one little prob under sqwebmail for quota's. Upon reading some info i believe this quirk is now gone under sqwebmail in the new versions but to do that upgrade of course i need to upgrade vpopmail, which was fine, except that the new version won't auth anyone with the new vchkpw... Info for system below : Qmail 1.03 (of course) vpopmail-3.4.11-1 my configure line for the new vpopmail (5.2.1) is : ./configure --enable-ip-alias-domains=y --enable-logging=e --enable- vpopuser=vpopmail --enable-md5-passwords=y --enable- defaultquota=20M --enable-clear-passwd=n (i have tried with enable-clear-passwd=y but no difference.) I run Qmail under tcpserver as follows : tcpserver -R -H 0 pop3 /var/qmail/bin/qmail-popup domainxyz.com.au /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail- pop3d Maildir& The domains all have their vpasswd/vpasswd.cdb files, but for some reason when i update the vchkpw it fails to auth. As soon as i revert no probs. Any help would be greatly appreciated. Thanks Nathan Out the 100TX, through the switch, down the cable modem, over the fiber optics, off the bridge, past the head end office nothing but 'Net.
[vchkpw] Upgrading from 4.9.8 to 5.3.8 (and above)
Hi, I'm going to migrate a system from qmail with vpopmail 4.9.8 with standard crypt-passwords to qmail with vpopmail 5.3.8 with md5-passwords. The 5.3.8 installation is configured with the following line: ./configure --enable-clear-passwd=n --enable-logging=e --enable-mysql-logging --enable-mysql=y This installation is up and running ok, but it's just the migration from the old system I'm a little worried about. I don't want to create new passwords for all =) If you have any hints or tips, please send me a note, and if you require more information from me, feel free to ask =) -- Geir O. Høgberg
RE: [vchkpw] Upgrading an old vpopmail install
Just to get my two cents in about the --enable-clear-passwd=n option. This does not work. I actually had to modify the configure script in order to turn this off. -Original Message- From: Bill Shupp [mailto:hostmaster@;shupp.org] Sent: Monday, November 04, 2002 12:05 PM To: [EMAIL PROTECTED] Subject: Re: [vchkpw] Upgrading an old vpopmail install On Monday, November 4, 2002, at 09:58 AM, Darek wrote: > Hey guys, > > I want to go from vpopmail-4.9.8 to probably 5.2.1, or maybe the > unstable branch. > > This is a live system and I am a bit weary about everything working > without as much as 5 minutes of downtime. The only difference that I > could see between a new version and the old is the placement of > tcp.smtp(.cdb) files. But that is pretty trivial. Everything else was > the same. > > Are there any serious differences that qmail, qmailadmin, > courier-imap, etc would care about? I know that there's been a lot of > development going on, but from a functional and practical point of > view, would qmail use vpopmail in the same exact way? There are a couple of issues: 1. 5.0+ defaults to clear passwords being on, which alters the number of fields in the vqpasswd structure (vpasswd file, table definitions, etc). There were some problems with backwards compatibility early on, but 5.2.1 should be fine. If you want to be extra cautious, use --enable-clear-passwd=n. 2. Courier-imap will need to be upgraded. Or, you can grab the latest preauchvchkpw.c and recompile your existing version. Regards, Bill
Re: [vchkpw] Upgrading an old vpopmail install
On Monday, November 4, 2002, at 09:58 AM, Darek wrote: Hey guys, I want to go from vpopmail-4.9.8 to probably 5.2.1, or maybe the unstable branch. This is a live system and I am a bit weary about everything working without as much as 5 minutes of downtime. The only difference that I could see between a new version and the old is the placement of tcp.smtp(.cdb) files. But that is pretty trivial. Everything else was the same. Are there any serious differences that qmail, qmailadmin, courier-imap, etc would care about? I know that there's been a lot of development going on, but from a functional and practical point of view, would qmail use vpopmail in the same exact way? There are a couple of issues: 1. 5.0+ defaults to clear passwords being on, which alters the number of fields in the vqpasswd structure (vpasswd file, table definitions, etc). There were some problems with backwards compatibility early on, but 5.2.1 should be fine. If you want to be extra cautious, use --enable-clear-passwd=n. 2. Courier-imap will need to be upgraded. Or, you can grab the latest preauchvchkpw.c and recompile your existing version. Regards, Bill
RE: [vchkpw] Upgrading an old vpopmail install
I personally would recommend installing on a test box so you can play with the software, and learn the new features before you just try to upgrade to live. It's a smooth transition, but always still a good idea. Regards, Tren -Original Message- From: Darek [mailto:darekm@;oakley.nyi.net] Sent: Monday, November 04, 2002 10:59 AM To: [EMAIL PROTECTED] Subject: [vchkpw] Upgrading an old vpopmail install Hey guys, I want to go from vpopmail-4.9.8 to probably 5.2.1, or maybe the unstable branch. This is a live system and I am a bit weary about everything working without as much as 5 minutes of downtime. The only difference that I could see between a new version and the old is the placement of tcp.smtp(.cdb) files. But that is pretty trivial. Everything else was the same. Are there any serious differences that qmail, qmailadmin, courier-imap, etc would care about? I know that there's been a lot of development going on, but from a functional and practical point of view, would qmail use vpopmail in the same exact way?
[vchkpw] Upgrading an old vpopmail install
Hey guys, I want to go from vpopmail-4.9.8 to probably 5.2.1, or maybe the unstable branch. This is a live system and I am a bit weary about everything working without as much as 5 minutes of downtime. The only difference that I could see between a new version and the old is the placement of tcp.smtp(.cdb) files. But that is pretty trivial. Everything else was the same. Are there any serious differences that qmail, qmailadmin, courier-imap, etc would care about? I know that there's been a lot of development going on, but from a functional and practical point of view, would qmail use vpopmail in the same exact way?
