Re: [SOGo] authentication with kerberos

2013-01-11 Thread cmschube
Looks like you might be right.. Well.. back to LDAP I guess.. Thanks Chris From: Heiner Markert To: users@sogo.nu Cc: cmsch...@rockwellcollins.com Date: 01/11/2013 08:10 AM Subject:Re: [SOGo] authentication with kerberos Hello, this might be bug 1200: http

Re: [SOGo] authentication with kerberos

2013-01-11 Thread Heiner Markert
sufficient pam_krb5.so no_user_check validate > account sufficient pam_permit.so > [root@centos01 httpd]# > > However, when I log into SOGo, then I get the error in my > /var/log/maillog. > > Jan 10 16:19:45 centos01 dovecot: auth: Debug: pam(user,127.0.0.1): loo

Re: [SOGo] authentication with kerberos

2013-01-10 Thread cmschube
no mbox_write_locks = fcntl passdb { driver = pam } ssl_cert = To: users@sogo.nu Date: 01/10/2013 02:29 PM Subject:Re: [SOGo] authentication with kerberos can you share how did you configure sogo with kerberos ? On Thu, Jan 10, 2013 at 8:03 PM, wrote: Is there anyway for SOGO

Re: [SOGo] authentication with kerberos

2013-01-10 Thread cmschube
lure (KDC reply did not match expectations) From: Khapare Joshi To: users@sogo.nu Date: 01/10/2013 02:29 PM Subject: Re: [SOGo] authentication with kerberos can you share how did you configure sogo with kerberos ? On Thu, Jan 10, 2013 at 8:03 PM, wrote: Is there anyway for SOGO

Re: [SOGo] authentication with kerberos

2013-01-10 Thread Khapare Joshi
can you share how did you configure sogo with kerberos ? On Thu, Jan 10, 2013 at 8:03 PM, wrote: > Is there anyway for SOGO to authenticate with UPPERCASE domain names? I was > having issues with Dovecot with LDAP, so i configured it with Kerberos, > which > works great. However, when SOGO passe

[SOGo] authentication with kerberos

2013-01-10 Thread cmschube
Is there anyway for SOGO to authenticate with UPPERCASE domain names? I was having issues with Dovecot with LDAP, so i configured it with Kerberos, which works great. However, when SOGO passes the authentication piece to Dovecot, it uses a lowercase domain name.. i.e. u...@example.com instead of