[Kolab-devel] [issue1161] cross realm error during imap login

[Arjen Runsink]

New submission from Arjen Runsink <arjen at zeilers.net>:

Hi 
 
Quick intro, after installing kolab, packaged from CVS, 
kolab-2.0.1-0.kolab.cvs20060306 2 domains were added.  
The 1st one is the local domain, the 2nd the 'vanity' domain. 
For the vanity domain a user account was added. 
kolab-2.0.1-0.kolab.cvs20060306 
Logging in was not possible. Adding the domain, well changing on of the 
parameters for loginrealms of /etc/imapd.conf made it work. Commenting out the 
paramater too. 
 
Below is a slightly edited version of an irc conversation with the packager. 
 
22:39 < }-Tux-{> i have loginrealms:      xxxxxx.tld xxxxxx.tld     
22:39 < }-Tux-{> in my imapd.conf too     
22:39 < }-Tux-{> and everything is working fine     
22:39 < Suit> }-Tux-{: It showed my 1st domain like that     
22:39 < Suit> but never listed the 2nd     
22:40 < Suit> I logged in using the 2nd     
22:40 < Suit> failed.     
22:40 < Suit> changed one of the 2 into my 2nd domain. and all worked     
22:40 < Suit> uncommented the setting and it still worked     
22:41 < }-Tux-{> but it is working when you add the second domain?     
22:41 < }-Tux-{> if yes it's a bug     
22:41 < }-Tux-{> and you should create an issue i think     
22:42 < Suit> yes, but.. since you/we are using ldap as a backend I suspect 
that the LDAP should decide which login realms are allowed/known

----------
messages: 6715
nosy: Suit
priority: critical
status: unread
title: cross realm error during imap login
topic: kolab-2.1
________________________________________________
Kolab issue tracker <kolab-issues at intevation.de>
<https://intevation.de/roundup/kolab/issue1161>
________________________________________________