>> I only wish to put my case forward for this feature (and don't wish to >> cause >> an argument over whether it's a good or bad feature). If the development >> team (MrSam?) think it is inappropriate or it simply isn't high enough on >> the list of priorities at the moment then I accept that decision. > > Ok, you've put your case forward. It's not that this isn't a high > priority; > it's rather a question of available time and the required effort.
> First, an approach needs to be made on incorporating the additional > information into the communication protocol used by authdaemon; and do so > in > a manner that does not break anything else. Other stuff uses authdaemon, I > understand that Cyrus SASL library knows about it. Then, each individual > authentication module that might use it, which seems to be mysql and > postgres, needs to be individually developed and tested. I don't believe > LDAP's query syntax is flexible enough to incorporate something like this. > > As you can easily understand, I have other things that take precedence, so > I > can't tell you with any certainty when this will get done. That, I'm > afraid, > the way things are. > I can see that there would be quite a lot of work to implement and test this functionality, and understand that other things must take precedence. But, it's good to know that it is on the list for some time in the future. Thanks. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
