* M. Stoffers <[email protected]>: > Yes, you're right. In the mean time, I did get a useful mail program > :P - I reformatted the attached Mail ;) - Sorry for inconvenience!
:) > "Patrick Ben Koetter" <[email protected]>: > > Seriously, please get a mail programm that sends useful formats. > > > > p...@rick > > > > Mirko Stoffers <[email protected]>: > >> Hi Patrick, > >> > >> hm, I cannot really see the problem with authorization: > >> My SQL database doesn't contain any authorization information > >> at all. Or do you mean that a saslauthdb could contain users There's no such thing as a "saslauthdb". It sounds as if you are mixing the Cyrus SASL "saslauthd" password verification service and the Cyrus SASL database "sasldb". > >> for different purposes (say, FTP server access) who are not Exactly. A SASL database can contain users for different purposes. It is not common to do that, but it is possible. > >> authorized for SOGo? For the latter I would recommend that > >> the authentication is done by SASL and the authorization by > >> the PostgreSQL table w/o the password field. > >> > >> However, obviously I have to accept that SOGo does not > >> currently support SASL. So I keep my configuration till SOGo > >> comes to support it ;) I wouldn't wait too long. I guess there are other features geared towards end users that stand in row first. ;) p...@rick > >> > >> Thanks > >> > >> Mirko > >> > >> "Patrick Ben Koetter" <[email protected]>: > >>> Mirko Stoffers : > >>> > >>> Hi Patrick, thanks for your reply. Yes, I also thought about > that. However, > >>> I'm not sure whether postgres is really a good source for > authentication. I > >>> think, postgres is more designed as a relational database than a > password > >>> storage, whilst the saslauthdb's only purpose is storing passwords. In > >>> practice, when I insert the entries into the postgres database > with "insert > >>> into ... md5('...') ..." the passwords are shown on the screen > in clear and > >>> saved in the history file. That's why I would prefer using a password > >>> storage (saslauthdb) for passwords. ;) Thanks, Mirko > -- > [email protected] > https://inverse.ca/sogo/lists -- state of mind Digitale Kommunikation http://www.state-of-mind.de Franziskanerstraße 15 Telefon +49 89 3090 4664 81669 München Telefax +49 89 3090 4666 Amtsgericht München Partnerschaftsregister PR 563 -- [email protected] https://inverse.ca/sogo/lists
