On Fri, 4 Jun 2004, Simon Matter wrote:
I'm using both versions on different servers and I can say they both work
very well for me. The pam way is more flexible if you have more than one
place where users are stored, say LDAP and MySQL, or you want to restrict
logins by other means like time or wha
On Fri, 4 Jun 2004, Wang Penghui wrote:
> Simon Matter wrote:
>
> >The only problem I see with pam_ldap is with the cyrus-imapd virtual
> >domains. AFAIK it doesn't work for more than one domain because PAM
> >doesn't know about realms.
> >
> >
> I have got your mean, if i want to add the virtual
Simon Matter wrote:
The only problem I see with pam_ldap is with the cyrus-imapd virtual
domains. AFAIK it doesn't work for more than one domain because PAM
doesn't know about realms.
I have got your mean, if i want to add the virtual domains support to
cyrus-imapd,
I have no choice to use sasl
> Hi,
>
> I have been working on a Mail System for several days.
> I used Postfix + Cyrus-IMAPd + Cyrus-SASL + OpenLDAP.
> LDAP Database is the accounts container.
> And the system should support virtual domains.
> All the processes which accesses the LDAP database thru saslauthd.
>
> I am using th
Hi,
I have been working on a Mail System for several days.
I used Postfix + Cyrus-IMAPd + Cyrus-SASL + OpenLDAP.
LDAP Database is the accounts container.
And the system should support virtual domains.
All the processes which accesses the LDAP database thru saslauthd.
I am using the saslauthd's ldap