Re: [SOGo] IMAP error

[(HT) Simon Walter]

On 09/11/2013 07:30 PM, labolinux wrote:

Hello,
we set up our SOGo and every is working. The only thing left is to get
the INBOX working.
 we get,anytime a user login, this error in /var/log/sogo/sogo.log :

Sep 11 14:06:44 sogod [18220]: 0x9DAB1618[SOGoMailAccount]:0 
renewing imap4 password
Sep 11 14:06:47 sogod [18220]: [ERROR] 
0x0x7f359d9f2258[NGImap4ConnectionManager] IMAP4 login failed:

  host=88.190.217.223, user=n...@sonerep.com, pwd=yes
url=imap://noc%40sonerep.com@88.190.217.223/
  base=(null)
  base-class=(null))
  = 0x0x7f359d9e0ed8[NGImap4Client]: login=n...@sonerep.com(pwd) 
socket=NGActiveSocket[0x0x7f359d8d1e38]: mode=rw 
address=0x0x7f359d82b808[NGInternetSocketAddress]: 
host=88-190-217-223.rev.poneytelecom.eu port=40040 
connectedTo=0x0x7f359d964b68[NGInternetSocketAddress]: 
host=88.190.217.223 port=143
Sep 11 14:06:47 sogod [18220]: [ERROR] 0x9DAB1618[SOGoMailAccount]:0 
Could not connect IMAP4
41.207.172.245 - - [11/Sep/2013:14:06:47 GMT] POST 
/SOGo/so/admin/Mail/0/mailboxes HTTP/1.1 200 17/0 6.031 - - 0
41.207.172.245 - - [11/Sep/2013:14:06:49 GMT] POST 
/SOGo/so/admin/Mail/foldersState HTTP/1.1 200 0/0 0.004 - - 0


WE tried to resolve it by setting SOGoForceIMAPLoginWithEmail to YES, 
but still the same message in the log file.


You might try looking at / posting the relevant portion of your IMAP 
server log to find out why the login is failing.

--
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] object not found: SOGo = UID [revisited, SOLVED (at least for me)]

[Igor Vitorac]

Whenever you play with sogo (or its configuration), always restart 
memcached as well, i.e. every time you restart sogod restart also memcached.




Marcel Waldvogel wrote, On 10/09/2013 16:51:

Hello

[This is in case anyone is running into the problem in the future. Maybe the 
friendly guys at inverse will also fix the root cause of this problem.]

After a restart of my database server, trying to login resulted in the 404 error object not found: 
username, where username was the user's login name. Trying to restart sogod did not help, 
neither did another restart of postgresql. The log did not show new error messages, either (see below), the 
LDAP solution from the object not found thread in January did not help either.. Looking at the log, 
it seemed that some users could still log in.

After some playing around, restarting memcached brought the solution, the 
system is running fine as ever.

@inverse: Could it be that if some requests are aborted due the DB shutdown, an 
invalid value is stored in memcached?

-Marcel

2013-09-10 16:27:35.259 sogod[24674] WARNING(-[NSNull(misc) count]): called 
NSNull -count (returns 0) !!!
111.111.111.111 - - [10/Sep/2013:16:27:35 GMT] GET /SOGo/so/ HTTP/1.1 200 
4438/0 0.021 12450 64% 0
2013-09-10 16:27:39.257 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): 
called selector objectForKey: on NSNull !
2013-09-10 16:27:39.259 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): 
called selector setObject:forKey: on NSNull !
2013-09-10 16:27:39.259 sogod[24674]   didn't set return value for type 'v'
Sep 10 16:27:39 sogod [24674]: SOGoRootPage successful login from '111.111.111.111' 
for user 'username' - expire = -1  grace = -1
111.111.111.111 - - [10/Sep/2013:16:27:39 GMT] POST /SOGo/connect HTTP/1.1 
200 27/47 0.049 - - 0
2013-09-10 16:27:39.549 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): 
called selector objectForKey: on NSNull !
2013-09-10 16:27:39.551 sogod[24674] ERROR(-[NSNull(misc) forwardInvocation:]): 
called selector setObject:forKey: on NSNull !
2013-09-10 16:27:39.551 sogod[24674]   didn't set return value for type 'v'
111.111.111.111 - - [10/Sep/2013:16:27:39 GMT] GET /SOGo/so/username 
HTTP/1.1 404 24/0 0.006 - - 0
2013-09-10 16:33:23.476 sogod[24674] File NSKeyValueCoding.m: 913. In 
-[NSObject(KeyValueCoding) valuesForKeys:] This method is deprecated, use 
-dictionaryWithValuesForKeys:




--
users@sogo.nu
https://inverse.ca/sogo/lists