[vchkpw] qmailadmin
i just installed qmailadmin 1.0.6 but i can't list the users on the domain anymore. No users left to view, please return to the previous page inter7 website states that it could be a vpopmail's clear password problem. i have went through all the users using vmoduser -C user@domain yet qmailadmin still can't show the users. anyone has a clue? sample line from vpasswd file === jinchin:hdT5yJdtGgb:1:0:Quek Jin Chin:/home/vpopmail/domains/mydomain.com/jinchin:20M:
[vchkpw] Not in rcpt.hosts
Hi I added ywesee.com with vadddomain and [EMAIL PROTECTED] with vadduser. When I now try to send a message to any Email-address I get: sorry this host is not in my rcpt-list. Any ideas what I am doing wrong. Thanks for your help. Zeno
[vchkpw] Qmailadmin and AutoResponder
Hi, I have installed on my email server qmailadmin-1.0.6, vpopmail 5.3.9 and qmail 1.0.3. I would disable the autorespond feature in qmailadmin, so I've compiled it with these parameters: ./configure--enable-autoresponder-bin=n --enable-maxautoresponders=0 . but when i log in as normal user and i set the autoresponder, the program will create the files .qmail and vacation/message in the user directory, in according with the definitions of autoresponder. There is a way to turn off definitively this feature? I do not want autoresponders because many users in this system are subscribed to mailing-lists Thanks in advance Alessandro A.
[vchkpw] vadduser batch file
Hi, In testing a conversion from a system user sendmail/qpopper set up to a cdb vpopmail set up, I noticed if I tried to batch multiple 'vadduser' entries, it would sometimes fail writing the cdb file and would build a cdb with only the last few entries, and overwrite the live vpasswd.cdb file. This is obviously a problem :) Is there any way to safeguard against this? The plain text vpasswd file is unaffected, so any vpasswd/vadduser/vdeluser command subsequentially entered will rebuild the database properly, but we intend to have many batch entries later on to synchronize with another external database, and we dont want this happening in the middle of the day, even for a few minutes.. I could easily add a 'sleep x' statement in the batch file between commands, but for large batch entries, this would overlap with the next batch run, since we hope to run the sync once per minute. Also, what would be a safe value for 'x' if this was the only solution? Any suggestions on this? In responding, please keep in mind that we'd like to maintain CDB as opposed to external databases(we already have enough problems synchronizing the current DB2/MSSQL databases :). I'd like to avoid having to run an LDAP or MySQL server. Thanks in advance, - Andre Fortin, CCNA Systems Administrator Technician Persona Communications, Northern Division 500 Barrydowne Rd. Sudbury, Ontario [EMAIL PROTECTED] Tel.: (705)560-1560 ext. 266
[vchkpw] courier-imap tends to stop authenticating after awhile
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
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
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
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
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
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
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
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.
RE: [vchkpw] simplest way to forward mail?
Thanks a bunch, that's exactly what I needed. Valias doesn't really look to be documented anywhere. -- Nathan Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 -Original Message- From: George Tosh [mailto:[EMAIL PROTECTED]] Sent: Friday, November 22, 2002 3:51 PM To: Neulinger, Nathan Cc: [EMAIL PROTECTED] Subject: Re: [vchkpw] simplest way to forward mail? The easiest way to do a database forward is to modify the valias table. If you want to forward mail for [EMAIL PROTECTED] to [EMAIL PROTECTED] In the valias table insert jdoe in the alias field and nowhere.com in the domain field. Now in the valias_line field insert [EMAIL PROTECTED] This should redirect the email accordingly. George Tosh System Administrator Aeneas Internet Services (731) 554-9200 - Original Message - From: Neulinger, Nathan [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, November 22, 2002 10:58 AM Subject: [vchkpw] simplest way to forward mail? Is there any pure-database mechanism within vpopmail for doing forwards, or is using .qmail files the only mechanism? Running latest development release w/ all mysql support enabled. -- Nathan Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216
RE: [vchkpw] Webmail Client
IMP: http://www.horde.org/imp/ Squirrel Mail: http://www.squirrelmail.org SqWebMail: http://www.inter7.com/sqwebmail/ I use IMP and I think it's great. A lot of people like squirrelmail though. I've found that SqWebMail is the fastest of the three, but it doesn't look as cool. -Original Message- From: Joe Oaks [mailto:[EMAIL PROTECTED]] Sent: Sunday, November 24, 2002 11:50 AM To: Vchkpw Subject: RE: [vchkpw] Webmail Client Endymion Mailman, http://www.endymion.com/products/mailman Joe -Original Message- From: rm [mailto:[EMAIL PROTECTED]] Sent: Sunday, November 24, 2002 11:55 AM To: vchkpw mailing list Subject: Re: [vchkpw] Webmail Client On Sun, 2002-11-24 at 13:14, Joe Oaks wrote: Preface I know this is off topic but have asked the webmail clients authors, with no luck? and I'm out of options now :( I have a webmail client installed on my server, and I have inquired of them why it is not working with the virtual domains. I am running RedHat 7.3, qmail-1.03, vpopmail-5.2.1, qmailadmin-1.0.5, and now that I have the virtual domains setup and working great I can't get the webmail client to work. First domain, trells.com set to ip 207.168.116.66 Second domain, mmz.org set to ip 207.168.116.85 Third and fourth, etc... The webmail clients are setup with there own url's and can be gotten to, http://webmail.trells.com and http://webmail.mmz.org under trells.com, I can login and get all my mail just fine, however under mmz.org I try to login and I get authorization failed, now comes the weird part, I can pop both via Outlook with no problems :/ I am in dire need of getting a webmail client that work with vpopmail do you guys know any? I am currently looking into squirrelmail, please let me know if any of you have a different one that works like this :) Joe Sqwebmail works fine for us. What client are you using? rm
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.
Re: [vchkpw] courier-imap tends to stop authenticating after awhile
Okay, update to my problem. Due to suggestions, I have upgraded certain peices of software. I am now running: FreeBSD 4.7-RELEASE Qmail 1.03_1 Vpopmail 5.3.9_1 SquirrelMail 1.2.8 Courier-Imap 1.5.3 All above programs have been installed from the ports tree in fbsd. Also due to suggestions, I have modifed the authdaemonrc file for courier-imap to the following: authmodulelist=authvchkpw authpam I rebooted the server, and so far people are able to login, we'll see in about an hour if people can still continue logging in. Like I said, imap logins just fail after a certain amount of time. I'm also going to check if pop3 authentication fails as well. Thanks for all the suggestions, I'll keep you posted. Taylor Dondich
RE: [vchkpw] Webmail Client
Thanks for all your responds, both personal and to the list, this gives me a great start and some great homework. Joe -Original Message- From: Clayton Weise [mailto:[EMAIL PROTECTED]] Sent: Monday, November 25, 2002 12:11 PM To: Vchkpw Subject: RE: [vchkpw] Webmail Client IMP: http://www.horde.org/imp/ Squirrel Mail: http://www.squirrelmail.org SqWebMail: http://www.inter7.com/sqwebmail/ I use IMP and I think it's great. A lot of people like squirrelmail though. I've found that SqWebMail is the fastest of the three, but it doesn't look as cool. -Original Message- From: Joe Oaks [mailto:[EMAIL PROTECTED]] Sent: Sunday, November 24, 2002 11:50 AM To: Vchkpw Subject: RE: [vchkpw] Webmail Client Endymion Mailman, http://www.endymion.com/products/mailman Joe -Original Message- From: rm [mailto:[EMAIL PROTECTED]] Sent: Sunday, November 24, 2002 11:55 AM To: vchkpw mailing list Subject: Re: [vchkpw] Webmail Client On Sun, 2002-11-24 at 13:14, Joe Oaks wrote: Preface I know this is off topic but have asked the webmail clients authors, with no luck? and I'm out of options now :( I have a webmail client installed on my server, and I have inquired of them why it is not working with the virtual domains. I am running RedHat 7.3, qmail-1.03, vpopmail-5.2.1, qmailadmin-1.0.5, and now that I have the virtual domains setup and working great I can't get the webmail client to work. First domain, trells.com set to ip 207.168.116.66 Second domain, mmz.org set to ip 207.168.116.85 Third and fourth, etc... The webmail clients are setup with there own url's and can be gotten to, http://webmail.trells.com and http://webmail.mmz.org under trells.com, I can login and get all my mail just fine, however under mmz.org I try to login and I get authorization failed, now comes the weird part, I can pop both via Outlook with no problems :/ I am in dire need of getting a webmail client that work with vpopmail do you guys know any? I am currently looking into squirrelmail, please let me know if any of you have a different one that works like this :) Joe Sqwebmail works fine for us. What client are you using? rm
[vchkpw] courier-imap STILL stops authenticating after awhile
Well, I attempted to correct the issue; however, courier-imap still tends to muck up authentication after awhile (about an hour or so). Is there any way to have courier-imap give a bit more verbose error messaging. All I see is LOGIN FAILED. I don't know whhy. Also, people keep saying that there's supposed to be a /usr/local/libexec/courier-imap/authlib/authvchkpw file or something, I don't have that, but authentication works for AWHILE. Then it takes a dump. Anyone have any suggestions? :( Taylor
