Marten Lehmann wrote:
Hello,
In my case it is:
ldap_filter:
(&(umMailObjectStatus=enabled)(umCyrusStatus=enabled)(umLogin=%u%R))
So that it looks for [EMAIL PROTECTED]
thanks. I'm using saslauthd with the -r option now as Simon adviced but
your combination with the "enabled" status is int
Hello,
In my case it is:
ldap_filter:
(&(umMailObjectStatus=enabled)(umCyrusStatus=enabled)(umLogin=%u%R))
So that it looks for [EMAIL PROTECTED]
thanks. I'm using saslauthd with the -r option now as Simon adviced but
your combination with the "enabled" status is interesting. I also
plann
Hello,
Did you check the "-r" switch of saslauthd?
no. I used a filter like
(|([EMAIL PROTECTED])(cn=%u))
instead but using "-r" is the better way which I'm using now. Thanks!
Regards
Marten Lehmann
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu
Marten Lehmann wrote:
Hello,
I'm using Cyrus with saslauthd using ldap. When I am testing the setup
with testsaslauthd it works fine. But when I am authenticating through
cyrus (imap login) then I notice in the saslauthd logs, that cyrus seems
to split the credentials. I'm using virtual domai
> Hello,
>
> I'm using Cyrus with saslauthd using ldap. When I am testing the setup
> with testsaslauthd it works fine. But when I am authenticating through
> cyrus (imap login) then I notice in the saslauthd logs, that cyrus seems
> to split the credentials. I'm using virtual domains, so a login l
Hello,
I'm using Cyrus with saslauthd using ldap. When I am testing the setup
with testsaslauthd it works fine. But when I am authenticating through
cyrus (imap login) then I notice in the saslauthd logs, that cyrus seems
to split the credentials. I'm using virtual domains, so a login looks
l
