Bruce Cheng wrote:
> 2008/8/1 Alessandro Vesely <vesely@...>:
>>> I have the question on "DEFAULT_DOMAIN" of Authlib settings. We can
>>> log in as 'user' without domains to COURIER-IMAP SERVER, but we can
>>> not log in as 'user' without domains to SASL authentication, we have
>>> to log in as 'user@...' to SASL authentication.
>> IIRC, DEFAULT_DOMAIN is only used by the MySQL backend. It provides a
>> default domain in case the logging in user didn't supply one.
> Yes, I know that.
I thought it was obvious, but your question was not very clear :-)
>>> If I post the wrong list, please correct me.
>> Well, this is the correct list for courier-imap, Authlib and Maildrop.
>> However, Postf and Cyrus are not related with Courier.
> Excuse me for that, but I have the question on Authlib. Because I set
> Cyrus-SASL auth via Authdaemon using mysql backend, if I can use log
> in as only 'user' without domains to courier-IMAP SERVER via
> authdaemon using mysql backed, why can't I use the same way for
> Cyrus-SASL ? I just don't know why, maybe I have something wrong in my
I don't know the details of Cyrus configuration, but if it eventually
calls the same function that provides courier-imap authentication, it
should also result in the same DEFAULT_DOMAIN setting, read from
authmysqlrc: If that module weren't able to access that file, it
wouldn't be able to generate an SQL query either.
If you enable DEBUG_LOGIN in authdaemonrc, you can confirm whether the
same module is being called for Cyrus-SASL.
Another possibility is that Cyrus itself detects the lack of a @
before calling the relevant authentication function.