SoGo unable to access users email after upgrade to 2.2.7-1

Obsolete Releases > SME 8.x Contribs

<< < (3/8) > >>

ajkeane:
OK I have deleted the user using sogo-tool (on my test system) opened chrome and cleared the cache. Logged in the user and still have the same issue.

From the dovecote logs:
2014-08-17 09:08:28.619645500 imap-login: Info: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured
2014-08-17 09:08:28.619648500 imap-login: Info: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured
2014-08-17 09:08:28.992924500 imap-login: Info: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured
2014-08-17 09:08:28.992926500 imap-login: Info: Disconnected (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured

From sogo logs:
Aug 17 09:08:28 sogod [3258]: SOGoRootPage successful login from '192.168.143.198' for user 'xxxxxxx' - expire = -1 grace = -1
192.168.143.198 - - [17/Aug/2014:09:08:28 GMT] "POST /SOGo/connect HTTP/1.1" 200 27/49 0.008 - - 0
192.168.143.198 - - [17/Aug/2014:09:08:28 GMT] "GET /SOGo/xxxxxxx HTTP/1.1" 302 0/0 0.003 - - 0
192.168.143.198 - - [17/Aug/2014:09:08:28 GMT] "GET /SOGo/xxxxxxx/view HTTP/1.1" 302 0/0 0.004 - - 0
192.168.143.198 - - [17/Aug/2014:09:08:28 GMT] "GET /SOGo/so/xxxxxxx/Mail HTTP/1.1" 302 0/0 0.003 - - 0
Aug 17 09:08:28 sogod [3258]: [ERROR] <0x0x7f48e564ee28[NGImap4ConnectionManager]> IMAP4 login failed:
host=localhost, user=xxxxxxx, pwd=yes
url=imap://xxxxxxx@localhost/INBOX/
base=(null)
base-class=(null))
= <0x0x7f48e572d998[NGImap4Client]: login=xxxxxxx(pwd) socket=<NGActiveSocket[0x0x7f48e5781848]: mode=rw address=<0x0x7f48e5748138[NGInternetSocketAddress]: host=localhost port=55392> connectedTo=<0x0x7f48e5614188[NGInternetSocketAddress]: host=localhost port=143>>>
Aug 17 09:08:28 sogod [3258]: <0xE56999B8[SOGoMailFolder]:folderINBOX> renewing imap4 password
Aug 17 09:08:28 sogod [3258]: [ERROR] <0x0x7f48e564ee28[NGImap4ConnectionManager]> IMAP4 login failed:
host=localhost, user=xxxxxxx, pwd=yes
url=imap://xxxxxxx@localhost/INBOX/
base=(null)
base-class=(null))
= <0x0x7f48e552a188[NGImap4Client]: login=xxxxxxx(pwd) socket=<NGActiveSocket[0x0x7f48e57302a8]: mode=rw address=<0x0x7f48e56aa278[NGInternetSocketAddress]: host=localhost port=55393> connectedTo=<0x0x7f48e57c6c68[NGInternetSocketAddress]: host=localhost port=143>>>
Aug 17 09:08:28 sogod [3258]: [ERROR] <0xE56999B8[SOGoMailFolder]:folderINBOX> Could not connect IMAP4
192.168.143.198 - - [17/Aug/2014:09:08:28 GMT] "GET /SOGo/so/xxxxxxx/Mail/view HTTP/1.1" 200 8216/0 0.046 34580 76% 376K
Aug 17 09:08:28 sogod [3256]: [ERROR] <0x0x7f48e54d1e68[NGImap4ConnectionManager]> IMAP4 login failed:
host=localhost, user=xxxxxxx, pwd=yes
url=imap://xxxxxxx@localhost/
base=(null)
base-class=(null))
= <0x0x7f48e58357b8[NGImap4Client]: login=xxxxxxx(pwd) socket=<NGActiveSocket[0x0x7f48e5575df8]: mode=rw address=<0x0x7f48e5714ac8[NGInternetSocketAddress]: host=localhost port=55396> connectedTo=<0x0x7f48e5617dc8[NGInternetSocketAddress]: host=localhost port=143>>>
Aug 17 09:08:28 sogod [3256]: <0xE5697308[SOGoMailAccount]:0> renewing imap4 password
Aug 17 09:08:28 sogod [3256]: [ERROR] <0x0x7f48e54d1e68[NGImap4ConnectionManager]> IMAP4 login failed:
host=localhost, user=xxxxxxx, pwd=yes
url=imap://xxxxxxx@localhost/
base=(null)
base-class=(null))
= <0x0x7f48e57b5a28[NGImap4Client]: login=xxxxxxx(pwd) socket=<NGActiveSocket[0x0x7f48e5665a58]: mode=rw address=<0x0x7f48e568cbd8[NGInternetSocketAddress]: host=localhost port=55397> connectedTo=<0x0x7f48e555d5f8[NGInternetSocketAddress]: host=localhost port=143>>>
Aug 17 09:08:28 sogod [3256]: [ERROR] <0xE5697308[SOGoMailAccount]:0> Could not connect IMAP4
192.168.143.198 - - [17/Aug/2014:09:08:28 GMT] "POST /SOGo/so/xxxxxxx/Mail/0/mailboxes HTTP/1.1" 200 17/0 0.036 - - 0
192.168.143.198 - - [17/Aug/2014:09:08:29 GMT] "POST /SOGo/so/xxxxxxx/Mail/foldersState HTTP/1.1" 200 0/0 0.045 - - 0
192.168.143.198 - - [17/Aug/2014:09:08:29 GMT] "POST /SOGo/so/xxxxxxx/Calendar/alarmslist?browserTime=1408223300 HTTP/1.1" 200 2/0 0.337 - - 0

I am only making changes on my test system at this point in time (a clean install on SME9_64 with one user created and SoGo installed) as I do not want to introduce any further issue son my production system. I was surprised that I have been able to replicate the issue across both SME8 and 9. If I had been able to get a system that worked on SME9 I would just migrate to it and say enough is enough.

I will try adding the port number but will be surprised if that helps.

Thanks for your help

Tony

nicolatiana:

--- Quote ---imap-login: Info: Disconnected (no auth attempts):
--- End quote ---

it seems that sogo is not passing any login credentials to Dovecot. At the moment no more ideas. Will give a look tomorrow.

You may try to sniff with tcpflow to get some more information about the login attempt

Nicola

ajkeane:
I will see what I can get using wireshark.

It surprises me that the log in works for the admin user though. It seems very strange to me.

Adding port 389 did not make any difference.

stephdl:

--- Quote from: ajkeane on August 16, 2014, 10:13:59 PM -----> Finished Dependency Resolution
Error: Package: razor-agents-2.85-1.el6.rf.x86_64 (@anaconda-base-201406271835.x86_64/9.0)
Requires: perl-Razor-Agent = 2.85-1.el6.rf
Removing: perl-Razor-Agent-2.85-1.el6.rf.x86_64 (@anaconda-base-201406271835.x86_64/9.0)
perl-Razor-Agent = 2.85-1.el6.rf
Updated By: perl-Razor-Agent-2.85-6.el6.x86_64 (epel)
perl-Razor-Agent = 2.85-6.el6
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

--- End quote ---

Indeed that behaviour is confirmed, I don't know if it is a bug, we ought to fill a bug report. Maybe some gurus can let some ideas or guidances.

If you want to exclude that package

--- Code: ---yum update smeserver-sogo sogo --enablerepo=stephdl,epel,sogo --exclude=perl-Razor-Agent
--- End code ---

stephdl:

--- Quote from: ajkeane on August 16, 2014, 10:37:41 PM ---The window not closing appears to be an issue in Firefox. It closes in Chrome.
I have tested this on windows 8.1 and 7. In Chrome, Firefox and I.E.

Surely this line in the sogo log says differently:
Aug 17 08:40:11 sogod [3258]: [ERROR] <0x0x7f48e564ee28[NGImap4ConnectionManager]> IMAP4 login failed:
It looks to me that I am unable to log into IMAP for some reason. Of course this is only an issue for users not admin.

--- End quote ---

I cannot reproduce your behaviour on sme9 even with a window 7 guest and firefox 31, It works as expected, I can use email menu, send invitation...no warnings in logs

What I did :

Fresh install of sme9dev64
full update
reconfiguration and reboot
install of smeserver-sogo
reconfiguration and reboot
enjoy

Edit : Thanks for the ldap missed port it is a bug that I will correct it in the next version I would to port. Indeed for now I have just built the nethesis version without huge customisation. The only one available is the architecture detection.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version