Thanks Valentin,

In the browser I'm using the unix account name : francois.monnet (withou @domain_name)

See below the compilation parameters :

./configure --prefix=/usr/local/webmail --with-cachedir=/var/cache/webmail --enable-imagedir=/home/httpd/igamail --enable-cgibindir=/home/httpd/igamail/cgi-bin
make clean
make configure-check
make
make check
umask 022
make install-strip
make install-configure


And the website is www.igamail.net

Thanks !

Francois


On both the machines (redhat 8, OK and redhat 9, not OK) I do'nt use vpopmail. At 13:48 14/08/2003 +0300, Valentin Ionescu wrote:
Just to be sure,...

Are your user added with vpopmail's vadduser or they are system users ?
In the browser, are you using [EMAIL PROTECTED] or just username (without
the @domain.com part)?
Could you post here the exact parameters that you used when compiling
vpopmail and sqwebmail?

Valentin Ionescu

----- Original Message -----
From: "NOC (EUROFMC)" <[EMAIL PROTECTED]>
To: "Cowle, Leon" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: 14 August, 2003 13:15
Subject: RE: [sqwebmail] Sqwebmail and Redhat 9


> Thanks for your precious help, Leon. > > I look at pams parameters too... > > Cheers, > Francois > At 11:11 14/08/2003 +0100, Cowle, Leon wrote: > >And /etc/pam.d/webmail is present and contains: > > > >[EMAIL PROTECTED] pam.d]# more webmail > >#%PAM-1.0 > ># > ># $Id: sqwebmail-system-auth.pamconf,v 1.1 2001/02/02 07:06:36 mrsam Exp $ > ># > ># Copyright 1998-2001 Double Precision, Inc. See COPYING for > ># distribution information. > ># > ># This is a sample authpam configuration file that uses pam_stack > ># (circa linux-pam 0.72). > > > >auth required pam_nologin.so > >auth required pam_stack.so service=system-auth > >account required pam_stack.so service=system-auth > >session required pam_stack.so service=system-auth > > > >That's where my handy suggestions would end... But I think we've made SOME > >progress by getting the right authdaemon running. > > > >--Leon. > > > >-----Original Message----- > >From: NOC (EUROFMC) [mailto:[EMAIL PROTECTED] > >Sent: Thursday, August 14, 2003 10:59 AM > >To: Cowle, Leon > >Cc: '[EMAIL PROTECTED]' > >Subject: RE: [sqwebmail] Sqwebmail and Redhat 9 > > > > > >Yes it's listed in the running daemons list (with ps -auxw, i.e) : > > > >root 23314 1 0 09:38 ? 00:00:00 > >/usr/local/webmail/libexec/authlib/authdaemond.plain start > >root 23319 23314 0 09:38 ? 00:00:00 > >/usr/local/webmail/libexec/authlib/authdaemond.plain start > > > >At 10:55 14/08/2003 +0100, Cowle, Leon wrote: > > >Stupid question.... Did you stop and restart the authdaemon process? Is > > >the authdaemond.plain now listed in a ps -ef output...? > > > > > >--Leon. > > > > > >-----Original Message----- > > >From: NOC (EUROFMC) [mailto:[EMAIL PROTECTED] > > >Sent: Thursday, August 14, 2003 10:47 AM > > >To: Cowle, Leon; 'Brian Candler' > > >Cc: '[EMAIL PROTECTED]' > > >Subject: RE: [sqwebmail] Sqwebmail and Redhat 9 > > > > > > > > >Thanks for all Leon. > > > > > >I've modified authdaemonrc with version=autdaemond.plain, ...but that's > > >still the same problem... > > > > > >Any more ideas ? > > > > > >Cheers, > > > > > >Francois > > >At 10:30 14/08/2003 +0100, Cowle, Leon wrote: > > > >Never too old to learn... I humbly stand corrected. > > > > > > > >Thanks Brian! > > > > > > > >--Leon. > > > > > > > >-----Original Message----- > > > >From: Brian Candler [mailto:[EMAIL PROTECTED] > > > >Sent: Thursday, August 14, 2003 10:14 AM > > > >To: Cowle, Leon > > > >Cc: 'NOC (EUROFMC)'; 'Valentin Ionescu'; 'Juha Saarinen'; > > > >'[EMAIL PROTECTED]' > > > >Subject: Re: [sqwebmail] Sqwebmail and Redhat 9 > > > > > > > > > > > >On Thu, Aug 14, 2003 at 10:08:30AM +0100, Cowle, Leon wrote: > > > > > Francois, > > > > > > > > > > Did you see my posting.....? > > > > > > > > > > <snip> > > > > > You can also check if it is starting authdaemond.plain instead of > > > > > authdaemond.mysql/authdaemond.pgsql/authdaemond.ldap -- might be > > > > > useful to force it to start the .plain one for troubleshooting > > > > > purposes (comment out the relevant lines in > > > > > /path/to/sqwebmail/libexec/authlib/authdaemond)... > > > > > <snip> > > > > > > > >There is a better way to force one particular authdaemond variant to > > > >be > > > >run: just set > > > > > > > >version="authdaemond.plain" > > > > > > > >(or whichever version you want) in authdaemonrc. > > > > > > > > > > > > > > > > > > --Leon. > > > > > > > > > > -----Original Message----- > > > > > From: NOC (EUROFMC) [mailto:[EMAIL PROTECTED] > > > > > Sent: Thursday, August 14, 2003 10:02 AM > > > > > To: Valentin Ionescu; Juha Saarinen > > > > > Cc: [EMAIL PROTECTED] > > > > > Subject: Re: [sqwebmail] Sqwebmail and Redhat 9 > > > > > > > > > > > > > > > Thanks for this information Valentin. > > > > > > > > > > ...but I've ever the same problem. > > > > > > > > > > I've noted this fact : > > > > > - in Redhat 8, it is authdaemond.plain wich runs > > > > > - in Redhat 9, it is authdaemond.ldap wich runs... > > > > > I've however runned ...../authdaemond start .. > > > > > > > > > > Francois > > > > > At 11:04 14/08/2003 +0300, Valentin Ionescu wrote: > > > > > >It's not a problem with RH9 because I started using > > > > > >qmail+vpopmail+sqwebmail about two months ago and my first > > > > > >qmail+vpopmail+platform was > > > > > >Linux Red Hat 9. > > > > > > > > > > > >Besides the problem with authdaemon that gives that "invalid > > > > > >login id or password" everything was a success. In order to > > > > > >override this problem I've added a crontab entry that restarts > > > > > >authdaemond every 1 minute. > > > > > > > > > > > >BTW, at my place I was encountering the invalid login in the next > > > > > situation: > > > > > > -login with a [EMAIL PROTECTED] > > > > > > -authenticate ok > > > > > > -logout > > > > > > -then, anyone who would try to login using a shorter > > > > > >username was facing the invalid login message. > > > > > > And the only way to give him acceess to his email through > > > > > >sqwebmail was to restart authdaemon. > > > > > > From what I've seen on this list it's a vpopmail issue and I > > > > > >don't know if they solved'it yet. > > > > > > > > > > > > > > > > > >----- Original Message ----- > > > > > >From: "NOC (EUROFMC)" <[EMAIL PROTECTED]> > > > > > >To: "Juha Saarinen" <[EMAIL PROTECTED]> > > > > > >Cc: <[EMAIL PROTECTED]> > > > > > >Sent: 14 August, 2003 10:38 > > > > > >Subject: Re: [sqwebmail] Sqwebmail and Redhat 9 > > > > > > > > > > > > > > > > > > > Thanks Juha, but that is not the problem : the sqwebmail cgi > > > > > > > is OK > > > > > > > : > > > > > > > I obtain the login dialog. > > > > > > > > > > > > > > ...and service sqwebmail not exists in fact. > > > > > > > > > > > > > > I confirm that authdaemond runs. > > > > > > > > > > > > > > No, it is really a problem with Redhat 9 : sqwebmail has been > > > > > > > installed with the same manner on a Redhat 8 machine and runs > > > > > > > very well... > > > > > > > > > > > > > > Francois Monnet > > > > > > > > > > > > > > At 19:30 14/08/2003 +1200, Juha Saarinen wrote: > > > > > > > > > > > > > > >Check the permissions on the sqwebmail binary in your cgi > > > > > > > >directory > > > > > > > >-- should be -r-sr-sr-x. Also check that the sqwebmail > > > > > > > >authentication daemon is started ('service sqwebmail start' > > > > > > > >as root or with sudo). > > > > > > > > > > > > > > > >-- > > > > > > > >Juha Saarinen > > > > > > > > > > > > > > >On Thu, 14 Aug 2003, NOC (EUROFMC) wrote: > > > > > > > > > > > > > > > > > Hi everybody, > > > > > > > > > > > > > > > > > > With the helpes of Jim an Brian I've installed sqwebmail > > > > > > > > > with success > > > > > >... > > > > > > > > > on Redhat 8.0 > > > > > > > > > > > > > > > > > > On Redhat 9, the compilation and install was correct, but > > > > > > > > > when I'll > > > > > >log to > > > > > > > > > the webmail, all logins are refused. > > > > > > > > > > > > > > > > > > A compatibility problem between authdaemond and Redhat 9 > > > > > > > > > ? > > > > > > > > > > > > > > > > > > Any idea ? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > > -- > > > > > -- > > > > > -------- > > > > > This message is intended only for the personal and confidential use of > > >the > > > > > designated recipient(s) named above. If you are not the intended > > > >recipient of > > > > > this message you are hereby notified that any review, > > > > > dissemination, distribution or copying of this message is strictly > > > > > prohibited. This communication is for information purposes only > > > > > and should not be regarded > > > >as > > > > > an offer to sell or as a solicitation of an offer to buy any > > > > > financial product, an official confirmation of any transaction, or > > > > > as an official statement of Lehman Brothers. Email transmission > > > > > cannot be guaranteed to > > > >be > > > > > secure or error-free. Therefore, we do not represent that this > > > >information is > > > > > complete or accurate and it should not be relied upon as such. > > > > > All information is subject to change without notice. > > > > > > > > > > > > > > > > > > > > > > >--------------------------------------------------------------------- > > > >-- > > > >------- > > > >This message is intended only for the personal and confidential use of > >the > > > >designated recipient(s) named above. If you are not the intended > >recipient > > >of > > > >this message you are hereby notified that any review, dissemination, > > > >distribution or copying of this message is strictly prohibited. This > > > >communication is for information purposes only and should not be > > > >regarded > > >as > > > >an offer to sell or as a solicitation of an offer to buy any > > > >financial product, an official confirmation of any transaction, or as > > > >an official statement of Lehman Brothers. Email transmission cannot > > > >be guaranteed to > > >be > > > >secure or error-free. Therefore, we do not represent that this > > > >information > > >is > > > >complete or accurate and it should not be relied upon as such. All > > > >information is subject to change without notice. > > > > > > > > > > > >----------------------------------------------------------------------- > > >------- > > >This message is intended only for the personal and confidential use of the > > >designated recipient(s) named above. If you are not the intended recipient > >of > > >this message you are hereby notified that any review, dissemination, > > >distribution or copying of this message is strictly prohibited. This > > >communication is for information purposes only and should not be regarded > >as > > >an offer to sell or as a solicitation of an offer to buy any financial > > >product, an official confirmation of any transaction, or as an official > > >statement of Lehman Brothers. Email transmission cannot be guaranteed to > >be > > >secure or error-free. Therefore, we do not represent that this information > >is > > >complete or accurate and it should not be relied upon as such. All > > >information is subject to change without notice. > > > > > >--------------------------------------------------------------------------- --- > >This message is intended only for the personal and confidential use of the > >designated recipient(s) named above. If you are not the intended recipient of > >this message you are hereby notified that any review, dissemination, > >distribution or copying of this message is strictly prohibited. This > >communication is for information purposes only and should not be regarded as > >an offer to sell or as a solicitation of an offer to buy any financial > >product, an official confirmation of any transaction, or as an official > >statement of Lehman Brothers. Email transmission cannot be guaranteed to be > >secure or error-free. Therefore, we do not represent that this information is > >complete or accurate and it should not be relied upon as such. All > >information is subject to change without notice. > > >




Reply via email to