Hello all, I posted this a few days ago and didn't receive any responses. I've revised this a bit to make it a little more clear in the hope that someone can clue me in as to what's going on.. The problem I speak of below is a problem with Courier itself making the initial database connection to PostgreSQL, not a problem authenticating users. Courier can't seem to connect to a PostgreSQL server when the auth_type in pg_hba.conf for that PG server is set to "MD5"..
----- Previously Posted Message ----
I've been using Courier IMAP and PG or a while, it works wonderfully.. However there is one thing that I have yet to figure out.
In my pg_hba.conf file on my database servers the auth type was set to md5 -- when auth type is set to md5 courier's pgsql auth daemon can't connect to the database (I get "password incorrect for <user>" errors on the database server)... Now get this - I change it to crypt on the database server and it works fine...
The whole password crypt/md5 this should be handled by libpq, and the passwords passed to the libpq connection function should always be in plain text. This is the case with Courier as far as I can tell so I'm stumped as to why the md5 method doesn't work... Some users on the pg-sql lists suggested that I might be linking to an old libpq but that can't be it as there is only one install of PostgreSQL and that's never changed.. Nothing else that I'd found has trouble connecting regardless of what I set my auth_type to in pg_hba.conf so it does seem to be a Courier-specific problem...
Any ideas?
Thanks!!
-Mitch
-------------------------------------------------------
This SF.net email is sponsored by: Microsoft Visual Studio.NET comprehensive development tool, built to increase your productivity. Try a free online hosted session at:
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr0003en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
