[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: openwebmail + postgresql configuration



Oliver Elphick wrote:
On Mon, 2004-06-14 at 20:01, Tom Allison wrote:

I'm running my authentication through a pgsql database with passwords that are stored as md5 hashes of the password.
This authentication model is working for the dovecot imap server.

However, under openwebmail I am accessing the database through 'localhost' instead of sockets and I keep getting a postgres pg_hba.conf configuration error. The affecting line is:

host    all   all 127.0.0.1          md5

2004-06-14 21:58:22 [24670] LOG: connection received: host=127.0.0.1 port=33487 2004-06-14 21:58:22 [24670] LOG: invalid entry in pg_hba.conf file at line 89, token "md5"


You have left out the netmask field

Thank you for your reply.
I missed that one address, 127.0.0.1, uses the netmask 255.255.255.255.



dovecot accesses the database for authenction through a line that says:
local    all         all             md5
(successfully).


Right now I have to figure this out, but my openwebmail part of the question is, can I set the host to a local socket?


If the hostname is blank, rather than "localhost", you will get a Unix
socket


I can get a connection through 127.0.0.1.
(I could/should switch to sockets someday)
and I can connect from other machines as well (more typos!)
But I get clobbered with this now.

[Tue Jun 15 05:53:24 2004] openwebmail.pl: DBI connect('dbname=dbmail;host=127.0.0.1','',...) failed: fe_sendauth: no password supplied at /usr/lib/cgi-bin/openwebmail/auth/auth_pgsql.pl line 48

Because of my user information on $HOME coming from /etc/passwd, I've left these blank. I don't see that they are causing any problems with the openwebmail script. So the following are blank.

field_realname
field_uid		
field_gid		
field_home		


If I use the openwebmail params to connect, I can do it successfully from psql and from a perl (DBI) script. auth_pgsql.pl (openwebmail) complains about the lack of a password.

The problem keeps cropping up that the sqlusr parm in the config file is not loaded. The username matches /\w+/

really stuck.



Reply to: