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 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] 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.
