Hi, > It seems to me that you want to provide the capability of _not_ sending > the 'client initial response' in the AUTH command in order to allow > interoperability with servers that support the AUTH extension but that > don't tolerate the optional client initial response argument.
Exactly that. > It seems to me that in order to achieve this you propose an option > named 'CURLOPT_MAIL_SINGLE_AUTH'. I believe that literal is a > bit misleading relative to its actual intended behavior. Yep. I must admit I was struggling for sensible [short] names ;-) > Introducing CURLOPT_MAILAUTH 'bitmasked' option would > allow to specify which authentication methods are exclusively > allowed to be used, along with any specific parametrization. For > example bitmask argument for CURLOPT_MAILAUTH could be > composed with bits such as: Being able to specify which authentication protocols is something that is already on my to do list - however, I didn't think it was something I would have time to complete for v7.22.0. > Steve, once that Daniel has commented on all this, you can > provide a single patch that provides whole functionality, at least > for the optional disabling of client-response AUTH argument. Sure. Kind Regards S. ------------------------------------------------------------------- List admin: http://cool.haxx.se/list/listinfo/curl-library Etiquette: http://curl.haxx.se/mail/etiquette.html
