On Fri, Apr 22, 2005 at 09:02:31PM -0300, Christian Willy Asmussen - Young Padovan wrote: > Jose Javier Sianes Ruiz wrote: > > >Talking in courier-imap mailist it seems there is no way, if you want to > >use 4.0.x version you need to use authdaemon. I think this is a steep > >back, configuring IMAP service with an extraservice for auth conections > >only adds a new point of fail. Yes, its more flexible but, at what price? > >My IMAP service is internal (for webmail), clients do not talk directly > >to IMAP service so I take Claudio solution: continue using version 3.0.x. > > > > > I partially agree with you concerning the "new point of fail". > The problem is that this will cause qmail-ldap to fork from > courier-imap, won't it? >
qmail-ldap used courier-imap as imap server as it was at the beginning the only serious imap server for maildirs. I honestly hate courier-imap and I would like to drop it somewhen. At the beginning there was courier-imap as easy to use qmail like imap server but then courier-mta and all this stuff came and blowed the whole thing up. Until now I did not have much time to look into binc imap and decide if it is better than courier. Btw. for me clean code and good programming style are more important then features. > For instance, maildrop now fetches it's data from authdaemon, which IMHO > is a good thing. > In a "long-term" point of view having a centralized authentication code > could result in a lot of code cleanup. > Acctually qmail-ldap could use a centralized authentication daemon but it will not be couriers authdaemon. > Is there ever going to be an integration with the new courier+authdaemon? > Currently not from my side. As I said I will first look into binc and if I like it qmail-ldap will go and tell people to use it instead. -- :wq Claudio
