Re: libetpan and SASL

On Jul 30, 2007, at 1:23 AM, DINH Viêt Hoà wrote:

> On 7/30/07, DINH Viêt Hoà <[email protected]> wrote:
>> On 7/30/07, Horia Olaru <[email protected]> wrote:
>>>
>>> pop3_mailstorage_init calls pop3_mailstorage_init_sasl with NULL  
>>> arguments
>>> for sasl authentication and thus falls back to plaintext. In order  
>>> to use
>>> SASL authentication I should call pop3_mailstorage_init_sasl direcly
>>> providing the argumets for the SASL authentication myself. Am I  
>>> correct in
>>> assuming this? If so, then it should be the same for imap.
>
> Yes, this is correct.
>
> LIBETPAN_EXPORT
> int imap_mailstorage_init_sasl(struct mailstorage * storage,
>    const char * imap_servername, uint16_t imap_port,
>    const char * imap_command,
>    int imap_connection_type,
>    const char * auth_type,
>    const char * server_fqdn,
>    const char * local_ip_port,
>    const char * remote_ip_port,
>    const char * login, const char * auth_name,
>    const char * password, const char * realm,
>    int imap_cached, const char * imap_cache_directory);
>
> You can see that auth_type is a "char *".
> auth_type as an enum (or integer) is not present in this API call.

Is there a good place to find documentation on what to specify, and  
when to use different parameters like local_ip_port, remote_ip_port,  
auth_name vs. login, etc? Is any of this documented in Cyrus SASL? Any  
docs I should look at?

I'm also interested in using the sasl init.
--
Matt
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/