The directory exists in the DB, and the sogo_folder_info indicates
"/Users/user/Calendar/personal" as path. So I tried modify the URL in
sogo-config.js to make it look through :
/Users/user/Calendar/personal
/dav/user/Calendar/personal
/Users/[email protected]/Calendar/personal
/dav/[email protected]/Calendar/personal
and each time, I've got a 404 error. The only way to make it work is to
connect first to SOGo with the browser. I even tried to force the
connection by sending a POST request to "/SOGo/connect" with the
username and password as the interface do it, but I've got this response :
SOGoRootPage Login for user '(nil)' might not have worked
Is it possible that the cache can't be initialized by Thunderbird ? I
think of that because when I type in my Browser "/SOGo/user", it say :
"object not found: SOGo => user". After logged in and out, the same URL
redirect me on the SOGo front page (maybe a security hole, by the way
?). Also, another think which make me think about a cache trouble, is
that the problem comes back after few hours of non-use (for example,
during the night) : maybe a cache drop.
Thanks for paying such attention to my troubles.
Yvan
Le 04/04/2011 08:33 AM, Stephen Ingram a écrit :
On Fri, Apr 1, 2011 at 2:17 AM, Yvan LE BOUFFANT
<[email protected]> wrote:
I've got some new information.
In fact, the problem is not about the login or email address, but, it's that
the object user does not exist, and Thunderbird is not able to make SOGo
creating this object. I hope this may help a bit more
That's a totally separate problem. Either you have an issue with your
directory or the user is not begin created properly in your DB. You
can look at the sogo_folder_info to see exactly what SOGo thinks the
username is. You can look at your directory server logs to see if it's
an LDAP issue.
Steve
--
[email protected]
https://inverse.ca/sogo/lists
