SOLVED (myself):

The Solution:

File: libs/dbmail_mysql/user.py
Diff:
226,229c226,227
<                 if settings.SQL_DEFAULT_PASSWD_SCHEME == 'PLAIN':
<                     columns['encryption_type'] = ''
<                 else:
<                     columns['encryption_type'] = settings.SQL_DEFAULT_PASSWD_SCHEME.lower()
---
>                 columns['encryption_type'] = settings.SQL_DEFAULT_PASSWD_SCHEME.lower()
>

File: libs/settings.py
Diff:
112c112
< SQL_DEFAULT_PASSWD_SCHEME = 'PLAIN'
---
> SQL_DEFAULT_PASSWD_SCHEME = 'MD5'

And how it works:
libs/settings.py and its setting SQL_DEFAULT_PASSWD_SCHEME does set the encryption of dbmailadmin which is used for setting passwords for created users.

However, dbmailadmin has a lil bug because dbmail3.x does not know encryption_type "plain" anymore. if you want plain password that field in sql table dbmail_users MUST be "".

thats why i had to fix the directive in libs/dbmail_mysql/user.py
The problam was that dbmailadmin wrote into encryption_type "plain" because it did simply use the SQL_DEFAULT_PASSWD_SCHEME-value without recognizing that dbmail3 has changed its behavour to dbmail2.

Why this was so important:
If you use sasl authentication for postfix with dbmail via mysql the stored password in dbmail_users MUST be plaintext!!! otherwise authentication via smtp WONT work.

Anyhow, problem solved.

Suggestion:
please fix this in the community version and maybe put in into the documentation or better create a setting into settings.ini so ppl with less skills dont run into frustration by trying to solve that issue.

best regards

Simon

You are right if u use sasl authentication daemon.
BUT
If u use DBMail and Postfix it just makes no real sense to make things complicated by using a poor documentated sasldaemon especialy if you want to use it in combination with dbmail3 and dbmailadmin and you dont need sasls usually. the comon dbmail-way is to use a sql statement (see exim, see postfix, ...) for smtp-authentication. the problem with postfix that itself want to compare the stored password with the one told by the client, but cant if the stored one is a crypted password.

however, the bug in dbmailadmin has been fixed, and proper authentication for smtp works now like a charme... again.
and thats just without any sasl daemon running - as it should be. only by comparing directly to db stored pwds.

btw: if u find a way to force postfix (without any external daemons) to hash transmitted pwd for comparing them to encrypted passwords, i may give it a try. for now, there is no way postfix could do that (without a seperate sasl daemon).

regards

Simon

maybe. but, im not using cyrus and why should i? that package btw does no even exist on ubuntu.
however, im using strictly dbmail and postfix. avoiding unneccessary daemons is a must.

what wiki u talkin about? link? i have not seen one tutorial in the wild which describes how to use md5 encrypted password in dbmail with postfix without external processing (e.g. sasl daemon). well, gimme that link please and i gonna look into it. although i got to admit that i dont expect much, since i would be pretty wondering if it has something i havent read yet. but how knows.

anyhow. working now. dbmailadmin's bug has been fixed. there is still a minor bug in the dashboard (messages 0) but that one has to wait. first i have to complete the mta.

best regards

Simon