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,519
  • +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,519
  • +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,519
  • +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

  • *
  • 721
  • +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

  • *
  • 721
  • +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,519
  • +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,519
  • +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 !!!

Offline stephdl

  • *
  • 1,519
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #15 on: August 17, 2014, 05:05:22 PM »
Not sure that is related but can you remove from /etc/sogo/sogo.conf

Code: [Select]
        NGImap4ConnectionStringSeparator = ".";
and add to /etc/sogo/sogo.conf (the two ldap section please)

Code: [Select]
port = 389;
after that
Code: [Select]
/etc/init.d/memcached restart
/etc/init.d/sogod restart
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 #16 on: August 17, 2014, 11:18:08 PM »
Thanks for the update, I have tried the changes that you have suggested but have been unable to make any difference.

I have done the exact same steps as yourself on my test box.

This is a snip of what I see when I log in. As you can see the normal user cannot see their email but admins emails are viewable. http://keane.co.nz/Primary/SoGo.PNG
...

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #17 on: August 17, 2014, 11:24:55 PM »
When I run the yum update smeserver-sogo sogo --enablerepo=stephdl,epel,sogo --exclude=perl-Razor-Agent I get the following output
[root@test-server ~]# yum update smeserver-sogo sogo --enablerepo=stephdl,epel,sogo --exclude=perl-Razor-Agent
Loaded plugins: fastestmirror, smeserver
Loading mirror speeds from cached hostfile
 * base: ftp.wicks.co.nz
 * epel: mirror.iprimus.com.au
 * smeaddons: mirror.canada.pialasse.com
 * smeextras: mirror.canada.pialasse.com
 * smeos: mirror.canada.pialasse.com
 * smeupdates: mirror.canada.pialasse.com
 * updates: centos.wtl.nsw.au.glomirror.com.au
Setting up Update Process
No Packages marked for Update
[root@test-server ~]#
...

Offline stephdl

  • *
  • 1,519
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #18 on: August 17, 2014, 11:44:02 PM »
When I run the yum update smeserver-sogo sogo --enablerepo=stephdl,epel,sogo --exclude=perl-Razor-Agent I get the following output
[root@test-server ~]# yum update smeserver-sogo sogo --enablerepo=stephdl,epel,sogo --exclude=perl-Razor-Agent
No Packages marked for Update
[root@test-server ~]#
I would be sure that you are fully updated, and thus it is what I expected. What is hard to follow is that on the same thread we are talking on two problems that are not similar (from my point of view)

a) For the sme9 64 bit test server, throw it to the bin :) and retry with another server, eventually trace all your commands with the root history and give back them....This should operate...
b) For the sme8 server I don't know what is occurring, probably you had an old version of smeserver-sogo and I suspect something odd with the imap configuration (maybe smeserver-dovecot ????)
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 #19 on: August 17, 2014, 11:52:38 PM »
I have a test server at work and will try the sogo installon that and report back. From my perspective I have the exact same symptoms and issues on both servers the logs and what is displayed in the browser are identical.

Thanks for your help anyway.
...

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #20 on: August 18, 2014, 12:08:14 AM »
Well I have replicated the exact same issue on a third server.

================================================================================
 Package                   Arch    Version                       Repository
                                                                           Size
================================================================================
Installing:
 smeserver-sogo            noarch  1.1-2.el6.sme                 stephdl   33 k
Installing for dependencies:
 gnustep-base              x86_64  1.23.0-1                      sogo     1.6 M
 gnustep-filesystem        noarch  2.6.2-1.el6                   epel     8.0 k
 gnustep-make              x86_64  2.6.2-1.el6                   epel     265 k
 lasso                     x86_64  2.3.6-1.centos6               sogo     664 k
 libevent                  x86_64  1.4.13-4.el6                  base      66 k
 libmemcached              x86_64  0.49-1                        sogo     131 k
 libobjc                   x86_64  4.4.7-4.el6                   base      90 k
 memcached                 x86_64  1.4.4-3.el6                   base      68 k
 sogo                      x86_64  2.2.7-1.centos6               sogo     3.1 M
 sogo-tool                 x86_64  2.2.7-1.centos6               sogo      37 k
 sope49-appserver          x86_64  4.9-20140730_1664.el6.1       sogo     885 k
 sope49-cards              x86_64  2.2.7-1.centos6               sogo     168 k
 sope49-core               x86_64  4.9-20140730_1664.el6.1       sogo     320 k
 sope49-gdl1               x86_64  4.9-20140730_1664.el6.1       sogo     157 k
 sope49-gdl1-contentstore  x86_64  2.2.7-1.centos6               sogo      56 k
 sope49-gdl1-mysql         x86_64  4.9-20140730_1664.el6.1       sogo      32 k
 sope49-ldap               x86_64  4.9-20140730_1664.el6.1       sogo      48 k
 sope49-mime               x86_64  4.9-20140730_1664.el6.1       sogo     279 k
 sope49-sbjson             x86_64  2.3.1-20140730_1664.el6.1     sogo      17 k
 sope49-xml                x86_64  4.9-20140730_1664.el6.1       sogo     193 k
 xmlsec1                   x86_64  1.2.19-3.el6                  epel     172 k
 xmlsec1-openssl           x86_64  1.2.19-3.el6                  epel      74 k

Transaction Summary
================================================================================
Install      23 Package(s)

Total download size: 8.4 M
Installed size: 39 M
Is this ok [y/N]: y
Downloading Packages:
(1/23): gnustep-base-1.23.0-1.x86_64.rpm                 | 1.6 MB     00:05
(2/23): gnustep-filesystem-2.6.2-1.el6.noarch.rpm        | 8.0 kB     00:00
(3/23): gnustep-make-2.6.2-1.el6.x86_64.rpm              | 265 kB     00:00
(4/23): lasso-2.3.6-1.centos6.x86_64.rpm                 | 664 kB     00:02
(5/23): libevent-1.4.13-4.el6.x86_64.rpm                 |  66 kB     00:00
(6/23): libmemcached-0.49-1.x86_64.rpm                   | 131 kB     00:00
(7/23): libobjc-4.4.7-4.el6.x86_64.rpm                   |  90 kB     00:00
(8/23): memcached-1.4.4-3.el6.x86_64.rpm                 |  68 kB     00:00
(9/23): smeserver-sogo-1.1-2.el6.sme.noarch.rpm          |  33 kB     00:00
(10/23): sogo-2.2.7-1.centos6.x86_64.rpm                 | 3.1 MB     00:06
(11/23): sogo-tool-2.2.7-1.centos6.x86_64.rpm            |  37 kB     00:00
(12/23): sope49-appserver-4.9-20140730_1664.el6.1.x86_64 | 885 kB     00:02
(13/23): sope49-cards-2.2.7-1.centos6.x86_64.rpm         | 168 kB     00:00
(14/23): sope49-core-4.9-20140730_1664.el6.1.x86_64.rpm  | 320 kB     00:00
(15/23): sope49-gdl1-4.9-20140730_1664.el6.1.x86_64.rpm  | 157 kB     00:00
(16/23): sope49-gdl1-contentstore-2.2.7-1.centos6.x86_64 |  56 kB     00:00
(17/23): sope49-gdl1-mysql-4.9-20140730_1664.el6.1.x86_6 |  32 kB     00:00
(18/23): sope49-ldap-4.9-20140730_1664.el6.1.x86_64.rpm  |  48 kB     00:00
(19/23): sope49-mime-4.9-20140730_1664.el6.1.x86_64.rpm  | 279 kB     00:00
(20/23): sope49-sbjson-2.3.1-20140730_1664.el6.1.x86_64. |  17 kB     00:00
(21/23): sope49-xml-4.9-20140730_1664.el6.1.x86_64.rpm   | 193 kB     00:00
(22/23): xmlsec1-1.2.19-3.el6.x86_64.rpm                 | 172 kB     00:00
(23/23): xmlsec1-openssl-1.2.19-3.el6.x86_64.rpm         |  74 kB     00:00
--------------------------------------------------------------------------------
Total                                           332 kB/s | 8.4 MB     00:25
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : sope49-xml-4.9-20140730_1664.el6.1.x86_64                   1/23
  Installing : sope49-core-4.9-20140730_1664.el6.1.x86_64                  2/23
  Installing : sope49-gdl1-4.9-20140730_1664.el6.1.x86_64                  3/23
  Installing : xmlsec1-1.2.19-3.el6.x86_64                                 4/23
  Installing : xmlsec1-openssl-1.2.19-3.el6.x86_64                         5/23
  Installing : lasso-2.3.6-1.centos6.x86_64                                6/23
  Installing : sope49-gdl1-mysql-4.9-20140730_1664.el6.1.x86_64            7/23
  Installing : sope49-gdl1-contentstore-2.2.7-1.centos6.x86_64             8/23
  Installing : sope49-ldap-4.9-20140730_1664.el6.1.x86_64                  9/23
  Installing : sope49-mime-4.9-20140730_1664.el6.1.x86_64                 10/23
  Installing : sope49-appserver-4.9-20140730_1664.el6.1.x86_64            11/23
  Installing : sope49-cards-2.2.7-1.centos6.x86_64                        12/23
  Installing : gnustep-filesystem-2.6.2-1.el6.noarch                      13/23
  Installing : gnustep-make-2.6.2-1.el6.x86_64                            14/23
install-info: warning: no info dir entry in `/usr/share/info/gnustep-make.info'
  Installing : libobjc-4.4.7-4.el6.x86_64                                 15/23
  Installing : gnustep-base-1.23.0-1.x86_64                               16/23
  Installing : libevent-1.4.13-4.el6.x86_64                               17/23
  Installing : memcached-1.4.4-3.el6.x86_64                               18/23
  Installing : sope49-sbjson-2.3.1-20140730_1664.el6.1.x86_64             19/23
  Installing : libmemcached-0.49-1.x86_64                                 20/23
  Installing : sogo-2.2.7-1.centos6.x86_64                                21/23
  Installing : sogo-tool-2.2.7-1.centos6.x86_64                           22/23
  Installing : smeserver-sogo-1.1-2.el6.sme.noarch                        23/23
Loading sogo_mysql_create_database into mysql [  OK  ]
Loading sogo_mysql_update_privileges into mysql [  OK  ]
Loading sogo_upgrade into mysql [  OK  ]
Migrating existing database networks
Migrating existing database spamassassin
Migrating existing database yum_available
Migrating existing database accounts
Migrating existing database hosts
Migrating existing database yum_installed
Migrating existing database configuration
Migrating existing database yum_repositories
Migrating existing database backups
Migrating existing database domains
Migrating existing database mailpatterns
Migrating existing database yum_updates
  Verifying  : libmemcached-0.49-1.x86_64                                  1/23
  Verifying  : sogo-tool-2.2.7-1.centos6.x86_64                            2/23
  Verifying  : sope49-ldap-4.9-20140730_1664.el6.1.x86_64                  3/23
  Verifying  : sope49-sbjson-2.3.1-20140730_1664.el6.1.x86_64              4/23
  Verifying  : gnustep-make-2.6.2-1.el6.x86_64                             5/23
  Verifying  : libevent-1.4.13-4.el6.x86_64                                6/23
  Verifying  : libobjc-4.4.7-4.el6.x86_64                                  7/23
  Verifying  : sope49-gdl1-mysql-4.9-20140730_1664.el6.1.x86_64            8/23
  Verifying  : xmlsec1-openssl-1.2.19-3.el6.x86_64                         9/23
  Verifying  : sope49-appserver-4.9-20140730_1664.el6.1.x86_64            10/23
  Verifying  : sope49-gdl1-4.9-20140730_1664.el6.1.x86_64                 11/23
  Verifying  : xmlsec1-1.2.19-3.el6.x86_64                                12/23
  Verifying  : lasso-2.3.6-1.centos6.x86_64                               13/23
  Verifying  : sogo-2.2.7-1.centos6.x86_64                                14/23
  Verifying  : sope49-gdl1-contentstore-2.2.7-1.centos6.x86_64            15/23
  Verifying  : gnustep-filesystem-2.6.2-1.el6.noarch                      16/23
  Verifying  : smeserver-sogo-1.1-2.el6.sme.noarch                        17/23
  Verifying  : sope49-cards-2.2.7-1.centos6.x86_64                        18/23
  Verifying  : gnustep-base-1.23.0-1.x86_64                               19/23
  Verifying  : sope49-core-4.9-20140730_1664.el6.1.x86_64                 20/23
  Verifying  : memcached-1.4.4-3.el6.x86_64                               21/23
  Verifying  : sope49-mime-4.9-20140730_1664.el6.1.x86_64                 22/23
  Verifying  : sope49-xml-4.9-20140730_1664.el6.1.x86_64                  23/23

Installed:
  smeserver-sogo.noarch 0:1.1-2.el6.sme

Dependency Installed:
  gnustep-base.x86_64 0:1.23.0-1
  gnustep-filesystem.noarch 0:2.6.2-1.el6
  gnustep-make.x86_64 0:2.6.2-1.el6
  lasso.x86_64 0:2.3.6-1.centos6
  libevent.x86_64 0:1.4.13-4.el6
  libmemcached.x86_64 0:0.49-1
  libobjc.x86_64 0:4.4.7-4.el6
  memcached.x86_64 0:1.4.4-3.el6
  sogo.x86_64 0:2.2.7-1.centos6
  sogo-tool.x86_64 0:2.2.7-1.centos6
  sope49-appserver.x86_64 0:4.9-20140730_1664.el6.1
  sope49-cards.x86_64 0:2.2.7-1.centos6
  sope49-core.x86_64 0:4.9-20140730_1664.el6.1
  sope49-gdl1.x86_64 0:4.9-20140730_1664.el6.1
  sope49-gdl1-contentstore.x86_64 0:2.2.7-1.centos6
  sope49-gdl1-mysql.x86_64 0:4.9-20140730_1664.el6.1
  sope49-ldap.x86_64 0:4.9-20140730_1664.el6.1
  sope49-mime.x86_64 0:4.9-20140730_1664.el6.1
  sope49-sbjson.x86_64 0:2.3.1-20140730_1664.el6.1
  sope49-xml.x86_64 0:4.9-20140730_1664.el6.1
  xmlsec1.x86_64 0:1.2.19-3.el6
  xmlsec1-openssl.x86_64 0:1.2.19-3.el6

Complete!

==============================================================
WARNING: You now need to run BOTH of the following commands
to ensure consistent system state:

signal-event post-upgrade; signal-event reboot
...

Offline stephdl

  • *
  • 1,519
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #21 on: August 18, 2014, 12:33:13 AM »
a bit of history on your server


installed from which version
is it a restored server


I have just installed from scratch a sme9 64 bit and it works :)

Edit: maybe you have an issue with a locale, could you try to use another locale (en-us) with a fresh install
Edit: tested with a locale in english and it works as expected....No more ideas...Try with a fresh install in a virtual environment, something odd with your configuration.

What are the contribs installed before?
« Last Edit: August 18, 2014, 12:59:17 AM 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 #22 on: August 18, 2014, 12:58:26 AM »
The server at work is a fresh install of SME9_64 on an IBM server with phpmyadmin installed which I use for web development. Neither of the test servers have had anything restored to them but are clean installs.

I will try using a different locale tonight as I am currently at work and unable to try this here today.

...

Offline stephdl

  • *
  • 1,519
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #23 on: August 18, 2014, 01:03:47 AM »
The server at work is a fresh install of SME9_64 on an IBM server with phpmyadmin installed which I use for web development. Neither of the test servers have had anything restored to them but are clean installs.

I will try using a different locale tonight as I am currently at work and unable to try this here today.

With consideration the only common point is maybe your web-browser. Did you have done all your tests with the same guest computer to manage Sogo????

With Windows, all is possible.
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 #24 on: August 18, 2014, 01:13:04 AM »
I have tried logging in using 4 different PC's all windows 7 or 8.1 fully patched. I have tried I.E. Firefox and Chrome on all PC's and have tried clearing the cache in the browsers as well.

Are you saying that the issue is the browser not passing the log in credentials properly to the server if that is the case then how can admin log in and see their emails. (as shown in the screen shot supplied above) This issue only affect users added after the server is built. It does to affect any email outside of SoGo I.E. Normal webmail and connection from Thunderbird still work as expected.

All of the syncing etc on my production server still works it only affect the viewing of emails.

The issue is to do with authentication from what I see in both sogo's and dovecotes logs and all installations I have done are identical in the error that I get proof of which I have supplied above.
...

Offline ajkeane

  • ****
  • 187
  • +0/-0
    • http://keane.co.nz
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #25 on: August 18, 2014, 07:26:58 AM »
Locale for the servers is:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=

Do you want me to try a different one?
...

Offline stephdl

  • *
  • 1,519
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #26 on: August 18, 2014, 07:37:26 AM »
I have tried logging in using 4 different PC's all windows 7 or 8.1 fully patched. I have tried I.E. Firefox and Chrome on all PC's and have tried clearing the cache in the browsers as well.

Are you saying that the issue is the browser not passing the log in credentials properly to the server if that is the case then how can admin log in and see their emails. (as shown in the screen shot supplied above) This issue only affect users added after the server is built. It does to affect any email outside of SoGo I.E. Normal webmail and connection from Thunderbird still work as expected.

All of the syncing etc on my production server still works it only affect the viewing of emails.

The issue is to do with authentication from what I see in both sogo's and dovecotes logs and all installations I have done are identical in the error that I get proof of which I have supplied above.

Well, thanks for testing that Tony. I have no more Idea of what you are experiencing. Moreover it is hard to debug something that it works out of the box on my side....Can you create an account and send me by email the credentials and url please.

I have just tested on my sme9 and I can  use new accounts created after the installation, no problem on this aspect.
See http://wiki.contribs.org/Koozali_Foundation
irc : Freenode #sme_server #sme-fr

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

Offline stephdl

  • *
  • 1,519
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #27 on: August 18, 2014, 01:43:24 PM »
Well I have 'le cul bordé de nouille' and I'm get sorted of that issue in creating a group in the server-manager with one user inside. Then after that each new user created can use the sogo email panel.

I don't know if some of you are used sogo without sme group created in the server-manager ??????

For your information the server is set in server/gateway but tony experienced the same issue also with a server-only.

below the snippet of log of what occurred after that I created the group with one user inside....IF some guru can explain that, I will be interested !!!

Code: [Select]
Aug 18 23:03:34 reports /etc/e-smith/web/panels/manager/cgi-bin/groups[8878]: /home/e-smith/db/accounts: OLD family=(undefined)
Aug 18 23:03:34 reports /etc/e-smith/web/panels/manager/cgi-bin/groups[8878]: /home/e-smith/db/accounts: NEW family=group|Description|test|Members|stephane
Aug 18 23:03:34 reports esmith::event[8879]: Processing event: group-create family
Aug 18 23:03:34 reports esmith::event[8879]: Running event handler: /etc/e-smith/events/group-create/S04group-create-unix
Aug 18 23:03:34 reports /etc/e-smith/events/group-create/S04group-create-unix[8880]: /home/e-smith/db/configuration: OLD MinUid=5005
Aug 18 23:03:34 reports /etc/e-smith/events/group-create/S04group-create-unix[8880]: /home/e-smith/db/configuration: NEW MinUid=5006
Aug 18 23:03:34 reports /etc/e-smith/events/group-create/S04group-create-unix[8880]: /home/e-smith/db/accounts: OLD family=group|Description|test|Members|stephane
Aug 18 23:03:34 reports /etc/e-smith/events/group-create/S04group-create-unix[8880]: /home/e-smith/db/accounts: NEW family=group|Description|test|Gid|5005|Members|stephane
Aug 18 23:03:34 reports /etc/e-smith/events/group-create/S04group-create-unix[8880]: /home/e-smith/db/accounts: OLD family=group|Description|test|Gid|5005|Members|stephane
Aug 18 23:03:34 reports /etc/e-smith/events/group-create/S04group-create-unix[8880]: /home/e-smith/db/accounts: NEW family=group|Description|test|Gid|5005|Members|stephane|Uid|5005
Aug 18 23:03:34 reports esmith::event[8879]: useradd: warning: the home directory already exists.
Aug 18 23:03:34 reports esmith::event[8879]: Not copying any file from skel directory into it.
Aug 18 23:03:35 reports esmith::event[8879]: Group family successfully added!
Aug 18 23:03:35 reports esmith::event[8879]: User family successfully added!
Aug 18 23:03:35 reports esmith::event[8879]: User family successfully modified!
Aug 18 23:03:35 reports esmith::event[8879]: User stephane successfully modified!
Aug 18 23:03:35 reports esmith::event[8879]: User admin successfully modified!
Aug 18 23:03:35 reports esmith::event[8879]: User www successfully modified!
Aug 18 23:03:35 reports esmith::event[8879]: S04group-create-unix=action|Event|group-create|Action|S04group-create-unix|Start|1408359814 383786|End|1408359815 937729|Elapsed|1.553943
Aug 18 23:03:35 reports esmith::event[8879]: Running event handler: /etc/e-smith/events/actions/generic_template_expand
Aug 18 23:03:36 reports esmith::event[8879]: expanding /var/qmail/control/badrcptto
Aug 18 23:03:36 reports esmith::event[8879]: expanding /var/service/qpsmtpd/config/goodrcptto
Aug 18 23:03:36 reports esmith::event[8879]: generic_template_expand=action|Event|group-create|Action|generic_template_expand|Start|1408359815 938122|End|1408359816 126234|Elapsed|0.188112
Aug 18 23:03:36 reports esmith::event[8879]: Running event handler: /etc/e-smith/events/group-create/S20qmail-update-group
Aug 18 23:03:36 reports esmith::event[8879]: S20qmail-update-group=action|Event|group-create|Action|S20qmail-update-group|Start|1408359816 126647|End|1408359816 271425|Elapsed|0.144778
Aug 18 23:03:36 reports esmith::event[8879]: Running event handler: /etc/e-smith/events/group-create/S56update-domain-group-maps
Aug 18 23:03:36 reports esmith::event[8879]: No rid or sid specified, choosing a RID
Aug 18 23:03:36 reports esmith::event[8879]: Got RID 11011
Aug 18 23:03:36 reports esmith::event[8879]: Successfully added group test to the mapping db as a domain group
Aug 18 23:03:36 reports esmith::event[8879]: S56update-domain-group-maps=action|Event|group-create|Action|S56update-domain-group-maps|Start|1408359816 271964|End|1408359816 628492|Elapsed|0.356528
Aug 18 23:03:36 reports esmith::event[8879]: Running event handler: /etc/e-smith/events/actions/adjust-services
Aug 18 23:03:36 reports esmith::event[8879]: adjusting supervised smbd (sighup)
Aug 18 23:03:36 reports esmith::event[8879]: adjusting supervised smbd (up)
Aug 18 23:03:36 reports esmith::event[8879]: adjust-services=action|Event|group-create|Action|adjust-services|Start|1408359816 628867|End|1408359816 745185|Elapsed|0.116318
Aug 18 23:03:36 reports esmith::event[8879]: Running event handler: /etc/e-smith/events/group-create/S95ldap-update-simple
Aug 18 23:03:37 reports esmith::event[8879]: S95ldap-update-simple=action|Event|group-create|Action|S95ldap-update-simple|Start|1408359816 745705|End|1408359817 71901|Elapsed|0.326196
Aug 18 23:08:28 reports esmith::event[8950]: Processing event: password-modify stephane
Aug 18 23:08:28 reports esmith::event[8950]: Running event handler: /etc/e-smith/events/actions/generic_template_expand
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/dhcpd.conf
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/rssh.conf
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/pptpd.conf
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/proftpd.conf
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/ftpusers
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/ppp/options.pptpd
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/ppp/ip-down.local
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/ppp/ip-up.local
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/raddb/radiusd.conf
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/raddb/users
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/e-smith/pam/accounts.allow
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/e-smith/pam/accounts.deny
Aug 18 23:08:28 reports esmith::event[8950]: expanding /etc/e-smith/pam/users.allow
Aug 18 23:08:28 reports esmith::event[8950]: generic_template_expand=action|Event|password-modify|Action|generic_template_expand|Start|1408360108 323086|End|1408360108 929620|Elapsed|0.606534
Aug 18 23:08:28 reports esmith::event[8950]: Running event handler: /etc/e-smith/events/password-modify/S25count-active-user-accounts
Aug 18 23:08:29 reports esmith::event[8950]: S25count-active-user-accounts=action|Event|password-modify|Action|S25count-active-user-accounts|Start|1408360108 930045|End|1408360109 20590|Elapsed|0.090545
Aug 18 23:08:29 reports esmith::event[8950]: Running event handler: /etc/e-smith/events/actions/adjust-services
Aug 18 23:08:29 reports esmith::event[8950]: adjusting supervised radiusd (sigterm)
Aug 18 23:08:29 reports esmith::event[8950]: adjusting supervised radiusd (up)
Aug 18 23:08:29 reports esmith::event[8950]: adjust-services=action|Event|password-modify|Action|adjust-services|Start|1408360109 21115|End|1408360109 122741|Elapsed|0.101626
Aug 18 23:08:29 reports esmith::event[8950]: Running event handler: /etc/e-smith/events/password-modify/S95ldap-update-simple
Aug 18 23:08:29 reports esmith::event[8950]: S95ldap-update-simple=action|Event|password-modify|Action|S95ldap-update-simple|Start|1408360109 123107|End|1408360109 464495|Elapsed|0.341388
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 #28 on: August 18, 2014, 10:27:33 PM »
Kudos to Stephane who has found a solution to this issue, thank you for all your work in isolating the fault and finding a fix.

Anyone else that finds they have these issues here is the resolution:

Create a group
Reset the users password
Add user to the group

The user should now be able into SoGo and see their email.

Thanks again to Stephane for tracking this down. Much appreciated.

Cheers
Tony
...

guest22

Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #29 on: August 18, 2014, 10:37:44 PM »
Determination. What a gift!

Offline nicolatiana

  • *
  • 721
  • +0/-0
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #30 on: August 19, 2014, 09:16:01 AM »
This is not obviously a regular behaviour of Sogo; I'll investigate in SOGo forum if this is a known issue or something affecting only the sme install.
Maybe we can add it as a warning in wiki page concerning SOGo.

Nicola

P.S.: le cul bordé de nouille = avere un culo grosso come una casa  :-D
Consulente di Smeserver.it -  Soluzioni e supporto su Sme server in Italia.

Offline nicolatiana

  • *
  • 721
  • +0/-0
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #31 on: August 19, 2014, 09:39:31 AM »
Added:
http://wiki.contribs.org/Sogo#Mixed_warnings

Please check if I get the correct interpretation.

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 #32 on: August 19, 2014, 10:34:12 AM »
Nicola

That looks good to me.

Cheers
Tony
...

Offline stephdl

  • *
  • 1,519
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #33 on: August 19, 2014, 05:32:00 PM »
Your Italian translation is really close than mine, funny to see foreign expressions  :lol:

In order to be serious one minute and no more, I would share some thoughts

-why the admin user wasn't affected : maybe the admin user is not a full ldap user ????
-why this bug occured : I have no ideas and I would to try to recreate it
-which events I could add to sogo-modify in order to solve automatically this bug :
group-create or group-modify
password-modify
or maybe simply call an action S95ldap-update-simple

Look the /var/log/messages snippet i did

The goal is 'clear' for me, I would avoid to see again that bug
See http://wiki.contribs.org/Koozali_Foundation
irc : Freenode #sme_server #sme-fr

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

Offline nicolatiana

  • *
  • 721
  • +0/-0
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #34 on: August 19, 2014, 06:13:49 PM »
- admin is assigned by default to root/admin group;
- I've found some issue in SOGo bugtracker concerning ldap group but nothing really similar to our issue; I'll dig again;

But . . . . . the issue affects only not grouped users or all of them until there's at least one not grouped ? I hope the first.

A user not in a group is an unusual condition, I'll focus how to work-around this; maybe all is originated by the fact that we do not really use LDAP for user auth for Samba, Mail & company.

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

Offline stephdl

  • *
  • 1,519
  • +0/-0
    • Linux et Geekeries
Re: SoGo unable to access users email after upgrade to 2.2.7-1
« Reply #35 on: August 19, 2014, 06:55:57 PM »
- admin is assigned by default to root/admin group;
- I've found some issue in SOGo bugtracker concerning ldap group but nothing really similar to our issue; I'll dig again;
Thanks to dig nicola

Quote
But . . . . . the issue affects only not grouped users or all of them until there's at least one not grouped ? I hope the first.
In fact Tony is a lucky man, Three servers affected by the same bug

One sme8  production server with smeserver (and sogo ?) upgraded to my rpm but with existent group(s) and users. I believe in microsoft worksgroup (in  server and gateway ?)
One sme8 server at home, first installation of smeserver-sogo, without group and users. I believe in microsoft master of domains  (in  server and gateway ?)
One sme9 test server , first installation of  smeserver-sogo, without group and users.  I believe in microsoft worksgroup in  server and gateway.

There is not shared configuration :( : @Tony can you confirm these configurations

Quote
A user not in a group is an unusual condition, I'll focus how to work-around this; maybe all is originated by the fact that we do not really use LDAP for user auth for Samba, Mail & company.

Yes you are right I would that all users are in a group, it makes me sense, but I'm not sure that it is the cause. I need the feedback of Daniel, it is my Ldap man and moreover one of my sme guru.

Of course if someone gets the solution, please shout :)

Nicola
[/quote]
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 #36 on: August 19, 2014, 10:07:14 PM »
Just to confirm what my setup is:
You were almost correct.

One sme8  production server (at Home) with smeserver (and sogo ?) upgraded to my rpm but with existent group(s) and users. In microsoft master of domains (in  server and gateway ?)
One sme9 test server , first installation of  smeserver-sogo, without group and users.  In microsoft workgroup in  server only mode. (This is the server that will replace my current home production server)
One sme9 server at work, first installation of smeserver-sogo, without group and users. In microsoft workgroup inside a full windows AD domain  (in  server and gateway ?)

If you need further clarification just ask.

Cheers
Tony
...