Re: [vchkpw] vpopmail+mysql + changing mysql servers
This could be from a number of problems, but most likely, the MySQL version has changed between boxes, or mysql is in a different place on the machine. vpopmail takes the mysql include and lib files and compiles them into the vpopmail binaries. Changing versions may require recompiling vpopmail. Other issues could be: connectivity - can the vpopmail user log into mysql? Is the username and password correct? Does the mysql user physically have access to the port? DNS - is the new machine properly set up? Do you get any errors? They would be helpful. On Monday 16 December 2002 04:59, Kent Ritchie wrote: I might be stupid to ask this, but I have looked online and in documentation, so I decided to ask here. I have a qmail+vpopmail setup, that authenticates through a remote mysql server. When I take the mysql server down and replace it with a different box, thats has all the data, users, grants etc on it that the previous box had, it no longer authenticates. I replace the old box, and it once again works... So, has anyone here ever made replacement like I am trying and failing to do?
Re: [vchkpw] vpopmail no longer using number/letter directory structure
It's the active directory structure code that causes that directory naming scheme. Is there anything in your installation that might interfere with the active directory structure code? Read about it in the INSTALL and other text files that come with the distribution. On Friday 06 December 2002 11:35, Ken Jones wrote: On Friday 06 December 2002 10:31 am, Nick Lomonte wrote: Running version 5.3.8, but ever since a few upgrades back (i dont remember how many) vpopmail has stopped adding users and domains to number/letter subdirectories like it used to. We've added hundreds of users, and it always puts them in /home/vpopmail/domains/domain.com/user instead of /home/vpopmail/domains/3/domain.com/A/user Is this no longer a feature? No. That code is still in there. Ken
Re: [vchkpw] courier-imap tends to stop authenticating after awhile
Are you using authdaemon? I believe disabling auth daemon at compile time fixes the problem too. compile with: --without-authdaemon \ --with-vchkpw when compiling courier-imap. I don't use authdaemon, and I don't have any troubles. This is an on-going list discussion. On Monday 25 November 2002 11:11, Dzuy Nguyen wrote: There is a bug in vchkpwd in vpopmail 5.2.1. Version 5.3.x seems to fix it. [EMAIL PROTECTED] wrote: I am using a qmail/vpopmail/courier-imap mail solution. After re-installing courier-imap, the first few times, imap sessions to work and authenticate, but after awhile, authentication fails and I get nothing but LOGIN FAILED messages in my maillog. A reboot of the server will fix it for a short time; however, it keeps happening. Has anyone had this occur before or have a possible solution? I am running these versions: FreeBSD 4.5-RELEASE Qmail - 1.03_1 vpopmail - 5.2 Courier-Imap - 1.5.3 Any suggestions would be helpful. Thanks, Taylor Dondich
Re: [vchkpw] courier-imap tends to stop authenticating after awhile
Yeah. I ran into the same problem. They/we should really include that in documentation somewhere. In fact, I get that problem with sqwebmail even if I DO disable authdaemon I'm not sure it's the same kind of issue though. But back to the reason I posted in the first place: I've seen plenty of people complain on the sqwebmail list that authdaemon croaks after a short time under high load. Using only the authvchkpw module and disabling authdaemon at compile time always fixed the problem. What versions are you running? On Monday 25 November 2002 12:24, Brian Kolaci wrote: authdaemond works for me, however IP Alias doesn't work since the IP information is passed via environment variables. The authdaemon protocol doesn't take into account any of the environment variables set by couriertcpd, so your missing some of the critical information. I've mentioned this on the courier list as well, however it didn't appear anyone cared... If you disable authdaemond (and have it fork/exec each login request), then it works fine. Its just not scalable (and I'm getting into that problem now when I hit about 20-25 authentications per second). Thanks, Brian Are you using authdaemon? I believe disabling auth daemon at compile time fixes the problem too. compile with: --without-authdaemon \ --with-vchkpw when compiling courier-imap. I don't use authdaemon, and I don't have any troubles. This is an on-going list discussion. On Monday 25 November 2002 11:11, Dzuy Nguyen wrote: There is a bug in vchkpwd in vpopmail 5.2.1. Version 5.3.x seems to fix it. [EMAIL PROTECTED] wrote: I am using a qmail/vpopmail/courier-imap mail solution. After re-installing courier-imap, the first few times, imap sessions to work and authenticate, but after awhile, authentication fails and I get nothing but LOGIN FAILED messages in my maillog. A reboot of the server will fix it for a short time; however, it keeps happening. Has anyone had this occur before or have a possible solution? I am running these versions: FreeBSD 4.5-RELEASE Qmail - 1.03_1 vpopmail - 5.2 Courier-Imap - 1.5.3 Any suggestions would be helpful. Thanks, Taylor Dondich Brian Galaxy Networks, Inc.
Re: [vchkpw] courier-imap tends to stop authenticating after awhile
Just out of curiosity, how many users does 20-25 authentications per second equate to for you? Thanks. On Monday 25 November 2002 12:58, Brian Kolaci wrote: You can disable it at runtime also. Just specify it in the AUTHMODULES variable in the .../etc/*.config files (mine is at authvchkpw authpam) rather than authdaemond. You don't have to go back and do a fresh compile. I was trying to use courier-imap 1.6.0, but I'm stuck at version 1.4.2. Under high loads, you *need* to have a pool of authentication servers. I also use MySQL so the database authentication needs to take place for every request. So some work needs to be done there, however I don't think its high on Sam's list. I may have to tackle it in the not too distant future, but I don't think my work would get incorporated into his distribution... Ken Bill have been willing to take patches. Thanks, Brian Yeah. I ran into the same problem. They/we should really include that in documentation somewhere. In fact, I get that problem with sqwebmail even if I DO disable authdaemon I'm not sure it's the same kind of issue though. But back to the reason I posted in the first place: I've seen plenty of people complain on the sqwebmail list that authdaemon croaks after a short time under high load. Using only the authvchkpw module and disabling authdaemon at compile time always fixed the problem. What versions are you running? On Monday 25 November 2002 12:24, Brian Kolaci wrote: authdaemond works for me, however IP Alias doesn't work since the IP information is passed via environment variables. The authdaemon protocol doesn't take into account any of the environment variables set by couriertcpd, so your missing some of the critical information. I've mentioned this on the courier list as well, however it didn't appear anyone cared... If you disable authdaemond (and have it fork/exec each login request), then it works fine. Its just not scalable (and I'm getting into that problem now when I hit about 20-25 authentications per second). Thanks, Brian Are you using authdaemon? I believe disabling auth daemon at compile time fixes the problem too. compile with: --without-authdaemon \ --with-vchkpw when compiling courier-imap. I don't use authdaemon, and I don't have any troubles. This is an on-going list discussion. On Monday 25 November 2002 11:11, Dzuy Nguyen wrote: There is a bug in vchkpwd in vpopmail 5.2.1. Version 5.3.x seems to fix it. [EMAIL PROTECTED] wrote: I am using a qmail/vpopmail/courier-imap mail solution. After re-installing courier-imap, the first few times, imap sessions to work and authenticate, but after awhile, authentication fails and I get nothing but LOGIN FAILED messages in my maillog. A reboot of the server will fix it for a short time; however, it keeps happening. Has anyone had this occur before or have a possible solution? I am running these versions: FreeBSD 4.5-RELEASE Qmail - 1.03_1 vpopmail - 5.2 Courier-Imap - 1.5.3 Any suggestions would be helpful. Thanks, Taylor Dondich Brian Galaxy Networks, Inc. Brian Galaxy Networks, Inc.
Re: [vchkpw] courier-imap tends to stop authenticating after awhile
What kind of machine is this with? Again, I'm just curious. I'll be implementing a similar setup soon, and I'm wondering where we'll max out. On Monday 25 November 2002 13:40, Brian Kolaci wrote: I have just under 2000 domains. Not sure of the number of users per domain. There's a few thousand local email addresses also (using pam). Note that the high load is only at peak times. During most of the day I see around 2-4 per second. Brian Just out of curiosity, how many users does 20-25 authentications per second equate to for you? Thanks. On Monday 25 November 2002 12:58, Brian Kolaci wrote: You can disable it at runtime also. Just specify it in the AUTHMODULES variable in the .../etc/*.config files (mine is at authvchkpw authpam) rather than authdaemond. You don't have to go back and do a fresh compile. I was trying to use courier-imap 1.6.0, but I'm stuck at version 1.4.2. Under high loads, you *need* to have a pool of authentication servers. I also use MySQL so the database authentication needs to take place for every request. So some work needs to be done there, however I don't think its high on Sam's list. I may have to tackle it in the not too distant future, but I don't think my work would get incorporated into his distribution... Ken Bill have been willing to take patches. Thanks, Brian Yeah. I ran into the same problem. They/we should really include that in documentation somewhere. In fact, I get that problem with sqwebmail even if I DO disable authdaemon I'm not sure it's the same kind of issue though. But back to the reason I posted in the first place: I've seen plenty of people complain on the sqwebmail list that authdaemon croaks after a short time under high load. Using only the authvchkpw module and disabling authdaemon at compile time always fixed the problem. What versions are you running? On Monday 25 November 2002 12:24, Brian Kolaci wrote: authdaemond works for me, however IP Alias doesn't work since the IP information is passed via environment variables. The authdaemon protocol doesn't take into account any of the environment variables set by couriertcpd, so your missing some of the critical information. I've mentioned this on the courier list as well, however it didn't appear anyone cared... If you disable authdaemond (and have it fork/exec each login request), then it works fine. Its just not scalable (and I'm getting into that problem now when I hit about 20-25 authentications per second). Thanks, Brian Are you using authdaemon? I believe disabling auth daemon at compile time fixes the problem too. compile with: --without-authdaemon \ --with-vchkpw when compiling courier-imap. I don't use authdaemon, and I don't have any troubles. This is an on-going list discussion. On Monday 25 November 2002 11:11, Dzuy Nguyen wrote: There is a bug in vchkpwd in vpopmail 5.2.1. Version 5.3.x seems to fix it. [EMAIL PROTECTED] wrote: I am using a qmail/vpopmail/courier-imap mail solution. After re-installing courier-imap, the first few times, imap sessions to work and authenticate, but after awhile, authentication fails and I get nothing but LOGIN FAILED messages in my maillog. A reboot of the server will fix it for a short time; however, it keeps happening. Has anyone had this occur before or have a possible solution? I am running these versions: FreeBSD 4.5-RELEASE Qmail - 1.03_1 vpopmail - 5.2 Courier-Imap - 1.5.3 Any suggestions would be helpful. Thanks, Taylor Dondich Brian Galaxy Networks, Inc. Brian Galaxy Networks, Inc. Brian Galaxy Networks, Inc.
[vchkpw] vpopmail+sqwebamil
Howdy list, Does anyone here know if the new version of sqwebmail (sqwebmail-3.4.0.20021026.tar.bz2) is capable of changing vpopmail passwords? I'm running FreeBSD 4.7-RELEASE and here is my sqwebmail compile sequence: --- ./configure --enable-https=auto --enable-softtimeout=600 \ --with-maxargsize=1000 \ --with-maxformargsize=1000 --with-trashquota \ --without-authpwd --without-authshadow \ --without-authpam --without-authuserdb \ --without-authmysql --without-authpgsql \ --without-authldap --without-authdaemon gmake configure-check gmake gmake check gmake install-strip gmake install-configure - I'm also running the following apache setup: Server Version: Apache/1.3.27 (Unix) PHP/4.2.3 mod_perl/1.27 mod_ssl/2.8.12 OpenSSL/0.9.6g -- Problem description: When I fill out the 'Old password' 'New password' and 'New Password Again' fields, then just press enter, I get the same page, but the password does not update. If I fill out the fields mentioned above, then click the 'Change Password' button, I get a Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. blah blah blah, which is the same error I get if the permissions are wrong on the cgi... Any ideas? I asked at the sqwebmail list, but they didn't answer... I thought that since this list gets more traffic, someone might have had the same problem here already. Thanks, Matthias
Re: [vchkpw] vpopmail development
Granted, vpopmail does a great job as is... I'd just hate to see this project die for lack of renovation someday. What's the licensing like? Could I modify the source and create another project? (Not that I want to... trust me. I've got plenty of better things to do.) Matthias On Wednesday 23 October 2002 13:41, Bill Shupp wrote: On Wednesday, October 23, 2002, at 07:03 AM, Matthias Trevarthan wrote: Howdy, Just curious: Is vpopmail still being actively developed? Yes. Is it a single developer, or is there a CVS and an open development community? I ask because I see people talking about patches a lot. If we had a CVS and an active development team, we wouldn't need patches, would we? Isn't that the strength of Open Source? The product evolves very quickly in response to it's user's needs. This gets foiled if there is only one developer... Ken Jones and Inter7 are the maintainers. I've been helping out with putting together releases and adding patches, etc.., but this decision is really up to Ken. Several people have offered to run CVS, and of course there's sourceforge. I'm not opposed to this. Regards, Bill Shupp
[vchkpw] many-domains=n large-site=y courier-imap problem
Howdy peeps, I'm testing a new install on a FreeBSD 4.6.2-RELEASE server. I'm running: Qmail vpopmail ./configure --enable-roaming-users=y --enable-clear-passwd=y --enable-logging=e --enable-log-name=vpopmail --enable-default-domain=domain.com --enable-defaultquota=500 --enable-mysql-logging=y --enable-mysql=y --enable-valias=y --enable-relay-clear-minutes=30 --enable-md5-passwords=y --enable-large-site=y --enable-ip-alias-domains=y --enable-many-domains=n courier-imap ./configure --without-ipv6 --with-trashquota This configuration worked just fine without many-domains=n. But when I added many-domains=n, courier suddenly can't authenticate. Let me repeat myself: The ONLY thing that has changed from a WORKING vpopmail-courier-imap MYSQL install is that I changed many-domains to 'n'. So, my question is, does the authvchkpw module not support multi-table domains? Will I have to rig authmysql authentication for this to work? Thanks! Matthias
Re: [vchkpw] many-domains=n large-site=y courier-imap problem
As I mentioned before, this is a test machine. I deleted all my domains and recreated them after the switch. I've only got three test domains anyway. On Friday 18 October 2002 12:55, tonix (Antonio Nati) wrote: As far as I remember, many-domains=n and many-domains=y work with different tables. So, when switching from n to y you should also convert the database to the new format. This is one of the switches you select with the first installation, and then you never change (usually). Tonino At 18/10/02 18/10/02 -0400, Matthias Trevarthan wrote: Howdy peeps, I'm testing a new install on a FreeBSD 4.6.2-RELEASE server. I'm running: Qmail vpopmail ./configure --enable-roaming-users=y --enable-clear-passwd=y --enable-logging=e --enable-log-name=vpopmail --enable-default-domain=domain.com --enable-defaultquota=500 --enable-mysql-logging=y --enable-mysql=y --enable-valias=y --enable-relay-clear-minutes=30 --enable-md5-passwords=y --enable-large-site=y --enable-ip-alias-domains=y --enable-many-domains=n courier-imap ./configure --without-ipv6 --with-trashquota This configuration worked just fine without many-domains=n. But when I added many-domains=n, courier suddenly can't authenticate. Let me repeat myself: The ONLY thing that has changed from a WORKING vpopmail-courier-imap MYSQL install is that I changed many-domains to 'n'. So, my question is, does the authvchkpw module not support multi-table domains? Will I have to rig authmysql authentication for this to work? Thanks! Matthias Inter@zioniInterazioni di Antonio Nati http://www.interazioni.it [EMAIL PROTECTED]
Re: [vchkpw] many-domains=n large-site=y courier-imap problem
Ok... I recompiled courier-imap, and now I can authenticate with [EMAIL PROTECTED], but I compiled vpopmail with --enable-ip-alias-domains=y. I should be able to authenticate with just 'user', right? I also did a vipmap -a 206.30.x.x mydomain.com. When I run vipmap without any arguments it returns what I inputed. Also, I can telnet mydomain.com 143 and I get my courier server's greeting, so I know it's running. Any ideas? Matthias On Friday 18 October 2002 12:18, Tren Blackburn wrote: It's because it links to the vpopmail library and you've now changed what's in that library. =) Tren -Original Message- From: Matthias Trevarthan [mailto:trevarthan;wingnet.net] Sent: Friday, October 18, 2002 10:16 AM To: Tren Blackburn Subject: Re: [vchkpw] many-domains=n large-site=y courier-imap problem No, I sure didn't. I didn't think that the authvchkpw authentication module internals would actually change. Let me try that On Friday 18 October 2002 12:10, Tren Blackburn wrote: After you recompiled vpopmail, did you recompile courier-imap? Any time you make changes to vpopmail you have to recompile any supporting programs (sqwebmail, qmailadmin, courier imap) Regards, Tren
[vchkpw] multi-table mysql domains
Howdy, I'm just curious, but why does the documentation frown upon multiple tables for multiple domains? Is it the per process file descriptor thing? (After all, that's not so much of a UNIX thing as a Linux thing. FreeBSD doesn't have per process limits. It has system limits, but they're tunable.) Or is it something else? I would think that throwing multiple domains and users into one table is poor database design. Not only is it more difficult to back up and administer, but I would think it would be slower! After all, if you have 10,000 users in one domain, and only 500 in another, it'd be inefficient to search for those 500 users among 10,000. Matthias
