Hello to All:
Congratulations to the dev group on the release of 20RC8. Nice job and many thanks for all your hard work! It is certainly a fine release candidate. Happy bug hunting.

I have been running it (from CVS) on both PostgreSQL and MySQL for about two weeks plus with the pre-rollback main.c/1.64 and have had no issues. In fact, it is a superior package by a long shot.

DBMA 2.0.2 (Administrator GUI) is fully compatible, if not favouring the release-destined RC8. (DBMA is a perl/web GUI for administering DbMail.)

I would like to poll PostgreSQL operators what if any preferences exist for the encryption of USER ACCOUNT PASSWORDS.

DBMA 2.0.2 uses MD5-Digest (md5sum) by default for MySQL which is a built-in since around v4.0 but I am in a quandary with PostgreSQL which seems to rely on contribs to handle md5 selects. There also seems to be quite a range of options. I wonder what seasoned PostgreSQL folks would favour? (Is anyone using PSQL 8-beta?) I refer only to the method of storing mail user passwords in the database and not client authentication. That is not to imply that such user account encryption is essential but if you had the option, what would you choose and what contrib method do you favour?

Presently DBMA V2.0.2 defaults to 32-digit md5-digest for MySQL and plaintext for PostgreSQL, with manual options.

Substantial changes to enhance the user friendliness have been made to DBMA and to accommodate the vast range of databases, their versions, and the backward genealogy of DbMail. I invite folks to upgrade/ download a fresh copy at http://library.mobrien.com/dbmailadministrator/

DbMail Administrator (DBMA 2.0.1) is pointed toward the eventual 2.0-Stable release but is backward compatible with pre-RC7/1.2.8/9 with a minor configuration setting. Please help yourself.

Any thoughts from PostgreSQL users would be much appreciated as I could use a steer in the right direction on encryption preferences and methods folks prefer for PgSQL.

best....
Mike

Reply via email to