Hello everybody,
I'm started to develop a very simple Admintool in php for my own.
But all the documentation is still for DBMail 2.2 and older.
Is it possible to update the documentation, especialy the ER-Model?
Best,
Claas
--
View this message in context:
http://old.nabble.com/Missing-docu
Has anybody an idea, to get SASL to work with encrypted passwords in the
database?
I used Cyrus SASL and it seems to be impossible.
--
View this message in context:
http://old.nabble.com/Cyrus-SASL-tp33763416p33763416.html
Sent from the dbmail users mailing list archive at Nabble.com.
Am 03.05.2012 16:19, schrieb cl445:
>
> Hello everybody,
>
> I'm started to develop a very simple Admintool in php for my own.
> But all the documentation is still for DBMail 2.2 and older.
> Is it possible to update the documentation, especialy the ER-Model?
what exactly are you missing?
i
> Has anybody an idea, to get SASL to work with encrypted passwords in
> the database?
> I used Cyrus SASL and it seems to be impossible.
That is SASL related not DBMail, anyway I think not, you must have clear
text passwd's in the DB for that,
___
DBma
Am 03.05.2012 16:22, schrieb cl445:
> Has anybody an idea, to get SASL to work with encrypted passwords in the
> database?
> I used Cyrus SASL and it seems to be impossible
it is technically not possible doing CRAM-MD5 without
acess to the unencrypted passwords - keep in mind that
the different
Yes you are right, but i need to access the dbmail_user table and there
are some undocumented fields, eg. the sieve_size fields.
Am 03.05.2012 16:22, schrieb Reindl Harald:
Am 03.05.2012 16:19, schrieb cl445:
Hello everybody,
I'm started to develop a very simple Admintool in php for my own
Okay, so the problem is, that SASL needs to encrypt the password for its
own and because of that i'm forced to store the passwords unencrypted?
Am 03.05.2012 16:24, schrieb Reindl Harald:
Am 03.05.2012 16:22, schrieb cl445:
Has anybody an idea, to get SASL to work with encrypted passwords in
AFAIK yes
Am 03.05.2012 16:58, schrieb Claas Kähler:
> Okay, so the problem is, that SASL needs to encrypt the password for its own
> and because of that i'm forced to
> store the passwords unencrypted?
>
> Am 03.05.2012 16:24, schrieb Reindl Harald:
>>
>> Am 03.05.2012 16:22, schrieb cl445:
>>>