After much head scratching about why the Courier-IMAP install on my
production box wouldn't authenticate against PostgreSQL, I realised that
the main difference between my dev. and production boxes was the use of
'md5' auth type rather than clear 'password'. (Google found one other
report of this problem on one of the postgres lists).
As soon as I changed pg_hba.conf entries from 'md5' to 'password' on my
dev. box then Courier-IMAP would fail to authenticate with the d/b.
I built some test source that basically just does:
PQsetdbLogin("/tmp", "5432", NULL, NULL, "mydb", "user", "pass");
This works fine on my dev box.
After adding some debug logging to authpgsqllib.c, and still getting
nowhere, I replaced the PQsetdbLogin() in the source with my test line
above and it still fails.
I'll take a guess that some of the MD5 routines within the courier
libs are somehow clobbering the MD5 routines inside libpq causing it
to fail on MD5 authentication.
(For the moment I've switched back to 'password' but this isn't ideal as
it means I have plain text d/b passwords).
Cheers,
-Paul-
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
