Koozali.org: home of the SME Server

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

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
SoGo unable to access users email after upgrade to 2.2.7-1
« on: August 15, 2014, 11:00:42 PM »
Hi I was experiencing the unable to attach files to replies issue so decided to upgrade Sogo.
I initially ran a:
yum update --disablerepo=* --enablerepo=sogo
/etc/rc7.d/S85sogod restart
as per the wiki. Upon completing this I found that though everyone could log in only the admin user could access their emails. All other functions appear to work.
Admin can expand email but users cannot.
In the logs I see:
Aug 15 21:36:03 sogod [19259]: [ERROR] <0x0xba291f24[NGImap4ConnectionManager]> IMAP4 login failed:
  host=localhost, user=xxxxxx, pwd=yes
  url=imap://xxxxxx@localhost/
  base=(null)
  base-class=(null))
  = <0x0xba174c64[NGImap4Client]: login=xxxxxx(pwd) socket=<NGActiveSocket[0x0xb9eb5d5c]: mode=rw address=<0x0xba218d34[NGInternetSocketAddress]: host=localhost port=35125> connectedTo=<0x0xba1f1eec[NGInternetSocketAddress]: host=localhost port=143>>>
Aug 15 21:36:03 sogod [19259]: <0xBA17B00C[SOGoMailAccount]:0> renewing imap4 password
Aug 15 21:36:03 sogod [19259]: [ERROR] <0x0xba291f24[NGImap4ConnectionManager]> IMAP4 login failed:
  host=localhost, user=xxxxxx, pwd=yes
  url=imap://xxxxxx@localhost/
  base=(null)
  base-class=(null))
  = <0x0xba247aec[NGImap4Client]: login=xxxxxx(pwd) socket=<NGActiveSocket[0x0xba11678c]: mode=rw address=<0x0xba21b414[NGInternetSocketAddress]: host=localhost port=35126> connectedTo=<0x0xba2fb44c[NGInternetSocketAddress]: host=localhost port=143>>>
Aug 15 21:36:03 sogod [19259]: [ERROR] <0xBA17B00C[SOGoMailAccount]:0> Could not connect IMAP4
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:36:03 GMT] "POST /SOGo/so/xxxxxx/Mail/0/mailboxes HTTP/1.1" 200 17/0 0.009 - - 0
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:36:03 GMT] "POST /SOGo/so/xxxxxx/Mail/1/mailboxes HTTP/1.1" 200 343/0 0.219 - - 0
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:36:04 GMT] "POST /SOGo/so/xxxxxx/Mail/1/folderINBOX/unseenCount HTTP/1.1" 200 13/0 0.259 - - 0
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:36:36 GMT] "GET /SOGo/so/xxxxxx/preferences HTTP/1.1" 200 15823/0 0.370 76295 79% 1M
Aug 15 21:40:59 sogod [19258]: [ERROR] <0x0xb9f8ab24[WOWatchDog]> No child available to handle incoming request!
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:40:59 GMT] "POST /SOGo/so/xxxxxx/Calendar/personal/canAccessContent HTTP/1.1" 204 0/0 0.017 - - 4K
Aug 15 21:41:00 sogod [19258]: [ERROR] <0x0xb9f8ab24[WOWatchDog]> No child available to handle incoming request!
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:00 GMT] "POST /SOGo/so/xxxxxx/Calendar/alarmslist?browserTime=1408095654 HTTP/1.1" 200 2/0 0.028 - - 176K
Aug 15 21:41:00 sogod [19258]: [ERROR] <0x0xb9f8ab24[WOWatchDog]> No child available to handle incoming request!
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:00 GMT] "POST /SOGo/so/xxxxxx/Calendar/taskslist?show-completed=0&asc=true&sort=end&filterpopup=view_today HTTP/1.1" 200 2/0 0.027 - - 32K
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:00 GMT] "POST /SOGo/so/xxxxxx/Calendar/eventslist?asc=true&sort=start&day=&filterpopup=view_today HTTP/1.1" 200 2/0 0.051 - - 184K
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:00 GMT] "POST /SOGo/so/xxxxxx/Calendar/activeTasks HTTP/1.1" 200 15/0 0.031 - - 48K
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:00 GMT] "POST /SOGo/so/xxxxxx/Calendar/monthview HTTP/1.1" 200 1200/0 0.033 6481 81% 8K
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:00 GMT] "POST /SOGo/so/xxxxxx/Calendar/eventsblocks?sd=20140728&ed=20140831&view=monthview HTTP/1.1" 200 394/0 0.023 1122 64% 56K
Aug 15 21:41:04 sogod [19259]: <0x0xba115ef4[LDAPSource]> <NSException: 0xba30fc34> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{login = "cn=xxxxxx,ou=groups,dc=keane,dc=co,dc=nz"; }
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:04 GMT] "GET /SOGo/so/xxxxxx/Mail HTTP/1.1" 302 0/0 0.015 - - 4K
Aug 15 21:41:04 sogod [19259]: [ERROR] <0x0xba291f24[NGImap4ConnectionManager]> IMAP4 login failed:
  host=localhost, user=xxxxxx, pwd=yes
  url=imap://xxxxxx@localhost/INBOX/
  base=(null)
  base-class=(null))
  = <0x0xba31269c[NGImap4Client]: login=xxxxxx(pwd) socket=<NGActiveSocket[0x0xba23599c]: mode=rw address=<0x0xba2970d4[NGInternetSocketAddress]: host=localhost port=35155> connectedTo=<0x0xba2fad3c[NGInternetSocketAddress]: host=localhost port=143>>>
Aug 15 21:41:04 sogod [19259]: <0xBA2579FC[SOGoMailFolder]:folderINBOX> renewing imap4 password
Aug 15 21:41:04 sogod [19259]: [ERROR] <0x0xba291f24[NGImap4ConnectionManager]> IMAP4 login failed:
  host=localhost, user=xxxxxx, pwd=yes
  url=imap://xxxxxx@localhost/INBOX/
  base=(null)
  base-class=(null))
  = <0x0xba3e1494[NGImap4Client]: login=xxxxxx(pwd) socket=<NGActiveSocket[0x0xba3325e4]: mode=rw address=<0x0xba28896c[NGInternetSocketAddress]: host=localhost port=35156> connectedTo=<0x0xba2fa194[NGInternetSocketAddress]: host=localhost port=143>>>
Aug 15 21:41:04 sogod [19259]: [ERROR] <0xBA2579FC[SOGoMailFolder]:folderINBOX> Could not connect IMAP4
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:04 GMT] "GET /SOGo/so/xxxxxx/Mail/view HTTP/1.1" 200 8444/0 0.083 35552 76% 0
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:04 GMT] "POST /SOGo/so/xxxxxx/Calendar/alarmslist?browserTime=1408095659 HTTP/1.1" 200 2/0 0.015 - - 0
2014-08-15 21:41:04.725 sogod[19261] WARNING: IMAP4 connection pooling is disabled!
Aug 15 21:41:04 sogod [19261]: [ERROR] <0x0xba13edec[NGImap4ConnectionManager]> IMAP4 login failed:
  host=localhost, user=xxxxxx, pwd=yes
  url=imap://xxxxxx@localhost/
  base=(null)
  base-class=(null))
  = <0x0xba1409ec[NGImap4Client]: login=xxxxxx(pwd) socket=<NGActiveSocket[0x0xba142c14]: mode=rw address=<0x0xba143084[NGInternetSocketAddress]: host=localhost port=35160> connectedTo=<0x0xba141bdc[NGInternetSocketAddress]: host=localhost port=143>>>
2014-08-15 21:41:04.727 sogod[19261] Note(NGImap4Connection): using '.' as the IMAP4 folder separator.
Aug 15 21:41:04 sogod [19261]: <0xBA13C964[SOGoMailAccount]:0> renewing imap4 password
Aug 15 21:41:04 sogod [19261]: [ERROR] <0x0xba13edec[NGImap4ConnectionManager]> IMAP4 login failed:
  host=localhost, user=xxxxxx, pwd=yes
  url=imap://xxxxxx@localhost/
  base=(null)
  base-class=(null))
  = <0x0xba14cdec[NGImap4Client]: login=xxxxxx(pwd) socket=<NGActiveSocket[0x0xba14d194]: mode=rw address=<0x0xba14d1d4[NGInternetSocketAddress]: host=localhost port=35161> connectedTo=<0x0xba14cebc[NGInternetSocketAddress]: host=localhost port=143>>>
Aug 15 21:41:04 sogod [19261]: [ERROR] <0xBA13C964[SOGoMailAccount]:0> Could not connect IMAP4
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:04 GMT] "POST /SOGo/so/xxxxxx/Mail/0/mailboxes HTTP/1.1" 200 17/0 0.018 - - 252K
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:04 GMT] "POST /SOGo/so/xxxxxx/Mail/1/mailboxes HTTP/1.1" 200 343/0 0.243 - - 24K
xxx.xxx.xxx.xxx - - [15/Aug/2014:21:41:05 GMT] "POST /SOGo/so/xxxxxx/Mail/1/folderINBOX/unseenCount HTTP/1.1" 200 13/0 0.263 - - 48K

After this I have also updated my yum repo's and update Sogo completely so I now have:
smeserver-sogo.noarch                        1.1-2.el5.sme             installed
smeserver-sogo-thunderbird.noarch            1.0.1-1.el5.nh            installed
sogo.i386                            2.2.7-1.el5                       installed
sogo-tool.i386                       2.2.7-1.el5                       installed

I have also installed Dan's Dovecote contrib.

This is my sogo.config

/*
 * ------------------------------------------------------------
 *            !!DO NOT MODIFY THIS FILE!!
 *
 *  Manual changes will be lost when this file is regenerated.
 *
 *  Please read the developer's guide, which is available
 *  at http://www.contribs.org/development/
 *
 *  Copyright (C) 1999-2006 Mitel Networks Corporation
 * ------------------------------------------------------------
 */
{
        NGUseUTF8AsURLEncoding = YES;
        OCSFolderInfoURL = "mysql://sogo:XXXXXXXXXXXXXXXXXXXX@localhost/sogo/sogo_folder_info";
        OCSSessionsFolderURL = "mysql://sogo:XXXXXXXXXXXXXXXXXXXX@localhost/sogo/sogo_sessions_folder";
        SOGoACLsSendEMailNotifications = NO;
        SOGoAppointmentSendEMailNotifications = YES;
        SOGoAppointmentSendEMailReceipts = YES;
        SOGoAuthenticationMethod = LDAP;
        SOGoDraftsFolderName = Drafts;
        SOGoEnablePublicAccess = YES;
        SOGoFoldersSendEMailNotifications = NO;
        SOGoIMAPServer = localhost;
        SOGoMailDomain = xxxxxxx.xx.xx;
        SOGoMailingMechanism = smtp;
        SOGoProfileURL = "mysql://sogo:XXXXXXXXXXXXXXXXXXXX@localhost/sogo/sogo_user_profile";
        SOGoSMTPServer = localhost;
        SOGoSentFolderName = Sent;
        SOGoSuperUsernames = (
            admin
        );
        SOGoTimeZone = Pacific/Auckland;
        SOGoTrashFolderName = Trash;
        WOWorkersCount = 3;
        SOGoMailAuxiliaryUserAccountsEnabled = YES;
    SOGoMailCustomFromEnabled = YES;

        SOGoSieveServer = sieve://localhost:4190;
        SOGoSieveScriptsEnabled = YES;
        SOGoVacationEnabled = YES;
        SOGoForwardEnabled = YES;
        NGImap4ConnectionStringSeparator = ".";

        SOGoUserSources = (

            {
                CNFieldName = cn;
                IDFieldName = uid;
                UIDFieldName = uid;
                baseDN = "ou=Users,dc=xxxxxxx,dc=xx,dc=xx";
                canAuthenticate = YES;
                displayName = "Users";
                hostname = localhost;
                id = users;
                isAddressBook = YES;
                port = ;
                type = ldap;
            },
            {
                CNFieldName = cn;
                IDFieldName = cn;
                UIDFieldName = cn;
                baseDN = "ou=Groups,dc=xxxxxxx,dc=xx,dc=xx";
                canAuthenticate = YES;
                displayName = "Groups";
                hostname = localhost;
                id = groups;
                isAddressBook = YES;
                port = ;
                type = ldap;
            }
        );
        WOMessageUseUTF8 = YES;
        WOParsersUseUTF8 = YES;
        WOPort = 127.0.0.1:20000;
        WOUseRelativeURLs = YES;
}

There are no issues with email other than in SoGo and syncing with my mobile devices etc is all working.

Does anyone know where I should look next to fix this issue?

Thanks
Tony
...

guest22

Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #1 on: August 15, 2014, 11:52:47 PM »
Stephane! we have a customer for you... ;-)

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #2 on: August 16, 2014, 07:51:29 AM »
Hi

As an update I decided to build an SME9_64 Server and have the exact same problem on it. Not sure where to go now.

Thanks

Tony
...

Offline stephdl

  • *
  • 1,514
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #3 on: August 16, 2014, 10:09:04 AM »
A bit far from my home...

- when you speak that you have rebuild a new server...i imagine that you did a full backup and restore

- You have tried to upgrade only sogo, did you have tried to upgrade smeserver-sogo

Yum update --enablerepo=sogo,stephdl

See http://wiki.contribs.org/Koozali_Foundation
irc : Freenode #sme_server #sme-fr

!!! Please write your knowledge to the Wiki !!!

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #4 on: August 16, 2014, 10:36:13 AM »
I actually did a full new install of SME9 on new hardware and then updated and installed SoGo. I did not restore any data etc I only created a single new users for testing purposes. Funnily enough I have found that I am able to send an email but the window does not close. I cannot see any folders or mail.

For my production server I have tried an upgrade as you have said but that has not fixed the issue.

Tony
...

Offline stephdl

  • *
  • 1,514
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #5 on: August 16, 2014, 12:44:18 PM »
Sme9 64 or 32 bit ????

What is the output of

Rpm -qa smeserver-sogo sogo

Do you can update more from epel

Yum update --enablerepo=stephdl,sogo,epel

edit : what is the window that you cannot close....is it a problem of your web browser.....can you reproduce it with another web browser
« Last Edit: August 16, 2014, 02:28:21 PM by stephdl »
See http://wiki.contribs.org/Koozali_Foundation
irc : Freenode #sme_server #sme-fr

!!! Please write your knowledge to the Wiki !!!

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #6 on: August 16, 2014, 10:13:59 PM »
64 as stated above.

sogo-2.2.7-1.centos6.x86_64
smeserver-sogo-1.1-2.el6.sme.noarch

Using username "root".
root@test.keane.co.nz's password:
Last login: Sun Aug 17 07:59:41 2014 from pc-00198.test.keane.co.nz
[root@test-server ~]# yum update --enablerepo=stephdl,sogo,epel
Loaded plugins: fastestmirror, smeserver
Loading mirror speeds from cached hostfile
 * base: mirror.internode.on.net
 * epel: epel.syd.au.glomirror.com.au
 * smeaddons: mirror.canada.pialasse.com
 * smeextras: mirror.canada.pialasse.com
 * smeos: mirror.canada.pialasse.com
 * smeupdates: mirror.canada.pialasse.com
 * updates: mirror.rackcentral.com.au
stephdl                                                                                                                                          | 1.9 kB     00:00
stephdl/primary_db                                                                                                                               |  77 kB     00:01
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package GeoIP.x86_64 0:1.4.8-1.el6 will be updated
---> Package GeoIP.x86_64 0:1.5.1-5.el6 will be an update
---> Package libffi.x86_64 0:3.0.5-3.2.el6 will be updated
---> Package libffi.x86_64 0:3.0.10-1 will be an update
---> Package oidentd.x86_64 0:2.0.8-1.el6.rf will be updated
---> Package oidentd.x86_64 0:2.0.8-8.el6 will be an update
---> Package perl-Razor-Agent.x86_64 0:2.85-1.el6.rf will be updated
--> Processing Dependency: perl-Razor-Agent = 2.85-1.el6.rf for package: razor-agents-2.85-1.el6.rf.x86_64
---> Package perl-Razor-Agent.x86_64 0:2.85-6.el6 will be an update
---> Package pptpd.x86_64 0:1.3.4-2.el6.sme will be updated
---> Package pptpd.x86_64 0:1.4.0-3.el6 will be an update
---> Package python-paste.noarch 0:1.7.4-2.el6 will be updated
---> Package python-paste.noarch 0:1.7.5.1-1.centos6 will be an update
---> Package python-simplejson.x86_64 0:2.0.9-3.1.el6 will be updated
---> Package python-simplejson.x86_64 0:2.5.2-1.centos6 will be an update
--> 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
[root@test-server ~]#

If on the _64 server in SoGo I try to write and email and I then click send the email is sent but the write email pop up window does not close automatically on send I have to click close.
...

Offline stephdl

  • *
  • 1,514
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #7 on: August 16, 2014, 10:34:20 PM »
What is your webbrowser and the os that you use....not sure that smeserver-sogo is in fault
See http://wiki.contribs.org/Koozali_Foundation
irc : Freenode #sme_server #sme-fr

!!! Please write your knowledge to the Wiki !!!

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #8 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.
« Last Edit: August 16, 2014, 10:42:00 PM by ajkeane »
...

Offline nicolatiana

  • *
  • 710
  • +0/-0
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #9 on: August 16, 2014, 10:46:39 PM »
From:
https://www.mail-archive.com/users@sogo.nu/msg18182.html
Quote
I had the same issue. The cause 1 : a misconfigured user account (imap server wrong). After deleting this user with sogo-tool SOGo was up and running. The cause 2: IE11 connecting to SOGo lost connection and the session keep hanging. After the user cleared the cache of the IE the issue was gone.
Take a look to dovecot log too (now with FWS Dovecot2 install /val/log/dovecot/current must be populated) to see login error from imap side too.
If you try with a test server it's essential you create as close as possible to the original (an 8/32 I suppose), if not this can result a bit confusing for debugging.

I took a look to a couple of my working installs sogo.conf: the only difference is in
Quote
port = 389;

instead of your
Quote
port = ;
in user sources; that means a missing LDAP port.
Anymore I don't think this is relevant.
« Last Edit: August 16, 2014, 10:49:40 PM by nicolatiana »
Consulente di Smeserver.it -  Soluzioni e supporto su Sme server in Italia.

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #10 on: August 16, 2014, 11:18:57 PM »
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
...

Offline nicolatiana

  • *
  • 710
  • +0/-0
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #11 on: August 17, 2014, 12:02:38 AM »
Quote
imap-login: Info: Disconnected (no auth attempts):

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


Consulente di Smeserver.it -  Soluzioni e supporto su Sme server in Italia.

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #12 on: August 17, 2014, 12:32:17 AM »
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.
...

Offline stephdl

  • *
  • 1,514
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #13 on: August 17, 2014, 03:16:11 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

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: [Select]
yum update smeserver-sogo sogo --enablerepo=stephdl,epel,sogo --exclude=perl-Razor-Agent
See http://wiki.contribs.org/Koozali_Foundation
irc : Freenode #sme_server #sme-fr

!!! Please write your knowledge to the Wiki !!!

Offline stephdl

  • *
  • 1,514
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #14 on: August 17, 2014, 03:24:58 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.

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.
« Last Edit: August 17, 2014, 04:37:59 PM by stephdl »
See http://wiki.contribs.org/Koozali_Foundation
irc : Freenode #sme_server #sme-fr

!!! Please write your knowledge to the Wiki !!!