This is a discussion on Re: [courier-users] webmail s_connect() error within the Courier-Imap forums, part of the Mail Servers and Related category; On Thu, Jun 16, 2005 at 10:36:12AM -0400, Ray Hernandez wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On Thu, Jun 16, 2005 at 10:36:12AM -0400, Ray Hernandez wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 .... > I run the authdaemond and it starts up ok. If I do a 'ps -ef,' I can see > that authdaemond is indeed running. If I use the authtest command with a > valid user and an incorrect password like so: > > authtest username badpassword > > I get: > Authentication FAILED: Operation not permitted > > Which is the correct behavior as far as I can tell. If I run the > authtest command with a valid user and a correct password: > > authtest username goodpassword > > I get: > Authentication succeeded. > > This is a good sign to me as it indicates that authdaemond is operating > correctly. .... > I then turn on the sqwebmail daemon and run a 'ps -ef' and verify that > sqwebmaild is in fact running, which it is. When I try to log on, > however, I get a: > > INVALID USER ID OR PASSWORD > > Please try again. > > I get this message regardless of whether I am inputting a correct > password or an incorrect password. All I can see from the logs is: .... This sounds almost like the initial problem I had getting Postfix+SASL2 to auth against courier-authdaemond. Does sqwebmaild have permission to read the authdaemond socket and enclosing directory? If not, fix that, e.g. by adding its user to the appropriate group which owns the socket and directory. > It seems as if sqwebmail is just not connecting at all to authdaemond. I > am wondering if sqwebmail is using the wrong UNIX socket or something. I > am not savvy enough to figure out which UNIX socket sqwebmail is using > to try and connect to authdaemond. I don't run SUSE so I can't help with that, but poke around in /var/run and similar directories and see if you can find it. The socket should reside in its own directory with limited access rights. -- Clifton -- Clifton Royston -- cliftonr@tikitechnologies.com Tiki Technologies Lead Programmer/Software Architect "I'm gonna tell my son to grow up pretty as the grass is green And whip-smart as the English Channel's wide..." -- 'Whip-Smart', Liz Phair ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users |