Re: [vchkpw] Problems Upgrading from 5.3.20 to 5.3.24

2003-08-18 Thread cyko
Quoting [EMAIL PROTECTED] [EMAIL PROTECTED]: I was successfully running vpopmail-5.3.20. I decided to upgrade to vpopmail-5.3.24 and now I'm getting the following bounce messages: [snip] [EMAIL PROTECTED]: vmysql: sql error[3]: Sorry, no mailbox here by that name. vpopmail (#5.1.1)

RE: [vchkpw] Problems Upgrading from 5.3.20 to 5.3.24

2003-08-18 Thread Tom Walsh
::I think I may have found the problem. Was there a structural ::change from 5.3.20 ::to 5.3.24 in the mysql database? :: ::Just to see if I could create a new domain and have it work, I did the ::following: :: ::[EMAIL PROTECTED]:/usr/local/vpopmail/bin# ./vadddomain blah.com ::Please enter

RE: [vchkpw] Problems Upgrading from 5.3.20 to 5.3.24

2003-08-18 Thread cyko
Quoting Tom Walsh [EMAIL PROTECTED]: ::I think I may have found the problem. Was there a structural ::change from 5.3.20 ::to 5.3.24 in the mysql database? :: ::Just to see if I could create a new domain and have it work, I did the ::following: :: ::[EMAIL

Re: [vchkpw] Problems Upgrading from 5.3.20 to 5.3.24

2003-08-18 Thread Evren Yurtesen
what was the parameters you used last time to configure vpopmail? before the upgrade? for version 5.3.20 ? Evren On Mon, 18 Aug 2003 [EMAIL PROTECTED] wrote: I was successfully running vpopmail-5.3.20. I decided to upgrade to vpopmail-5.3.24 and now I'm getting the following bounce

Re: [vchkpw] Problems Upgrading from 5.3.20 to 5.3.24

2003-08-18 Thread Evren Yurtesen
Perhaps you didnt upgrade qmailadmin, if you even do a reinstall it might get broken again. Qmailadmin statically compiles in some vpopmail conf files inside... On Mon, 18 Aug 2003 [EMAIL PROTECTED] wrote: Quoting [EMAIL PROTECTED] [EMAIL PROTECTED]: I was successfully running

Re: [vchkpw] Problems Upgrading from 5.3.20 to 5.3.24

2003-08-18 Thread Evren Yurtesen
AH I SEE you should recompile without enable clear passwords (which doesnt seem to be in your configure options anyhow, weird) or perhaps if it is enabled automatically for some weird reason in newer versions you just have to add the disabling option perhaps the only difference is that you dont