General discussion on installation and configuration of SOGo

Text archives Help


Re: [SOGo] Error 404 before using the SOGo Web interface


Chronological Thread 
  • From: Yvan LE BOUFFANT < >
  • To:
  • Subject: Re: [SOGo] Error 404 before using the SOGo Web interface
  • Date: Thu, 31 Mar 2011 14:21:50 +0200

Because of my configuration, the SOGo integrator can't make difference between my email address and my username (because my IMAP configuration requires the email address as login). I would appreciate that it propose me to enter another username BEFORE trying to reach SOGo, but it doesn't : the sogo username is fixed by :

if(useEmail)
sogoConfig['username'] = mgr.defaultAccount.defaultIdentity.email;
else
sogoConfig['username'] = mgr.defaultAccount.incomingServer.realUsername;

but, in my case, both are equals....

I don't understand how changing something in the sogo-config.js will make a difference except if there is a way to make an LDAP request to recover the login from the email address.
Did I miss something in the configurations ?

Thanks for your help

Yvan

Le 03/30/2011 04:55 PM, Stephen Ingram a écrit :
Yvan LE BOUFFANT wrote:
I only suppress the line 132 in chrome/content/global/common-dialog-overlay.js :

loginContainer.hidden = true;

That way, the login is still accessible, and I can change it (because default is email address).

So (without the help of your Web login) your Thunderbird login is not working properly at all....

You can change chrome/content/sogo-config.js such that SOGo will use whatever you want to login. However, why wouldn't you change this setup as I suggested (with an ldap search) such that you could simply login with the ldap uid (userid) and allow ldap to handle the magic of converting over to the email address in the background? This would avoid the extra entry of the login that you are trying to suppress.

Steve





Archive powered by MHonArc 2.6.18.

Top of page