Koozali.org: home of the SME Server
Obsolete Releases => SME 9.x Contribs => Topic started by: stephdl on January 31, 2016, 06:44:06 PM
-
Sogo3 is out....does someone has already played with it....that could be a great new update to the contribs.
If you have inputs
-
not already (discovered today, have just played a bit with the demo), but I see that rpms are available..
In their FAQ section I can't find anything related to upgrading, but I had no time to dig it.. maybe some templates needs to be modified, but a simple inplace upgrade could work..
-
Upgrading to v3 should be painless (no database upgrade or anything), but I haven't tested yet. The real challenge is to provide both v2 and v3 (which can share the same datastore), as IMHO, the v3 interface is still too young to be used in production alone. It can probably be installed in a simple chroot, or in a minimal container
-
Regarding this thread http://sogo.nu/news/2016/article/sogo-v300-released.html indeed I have the confirmation that it is easy to upgrade sogo, but not yet tested.
You have a separated repository so it could be a choice from the sysadmin to upgrade or not. Since inverse is well known to be like Microsoft, it means that you are the testers....they did nothing before you, please take a vm first ;)
-
SOGO has an issue with the metadata of its repo, you must download each rpm by hand
only in a vm of course, install first smeserver-sogo
for a i686
yum install http://inverse.ca/rhel-v3/6/i386/RPMS/sogo-3.0.0-1.centos6.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sogo-activesync-3.0.0-1.centos6.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sogo-ealarms-notify-3.0.0-1.centos6.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sogo-tool-3.0.0-1.centos6.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-appserver-4.9-20160127_1664.el6.1.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-cards-3.0.0-1.centos6.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-core-4.9-20160127_1664.el6.1.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-gdl1-4.9-20160127_1664.el6.1.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-gdl1-contentstore-3.0.0-1.centos6.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-gdl1-mysql-4.9-20160127_1664.el6.1.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-ldap-4.9-20160127_1664.el6.1.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-mime-4.9-20160127_1664.el6.1.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-sbjson-2.3.1-20160127_1664.el6.1.i686.rpm http://inverse.ca/rhel-v3/6/i386/RPMS/sope49-xml-4.9-20160127_1664.el6.1.i686.rpm
for x64
yum install http://inverse.ca/rhel-v3/6/x86_64/RPMS/sogo-3.0.0-1.centos6.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sogo-activesync-3.0.0-1.centos6.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sogo-ealarms-notify-3.0.0-1.centos6.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sogo-tool-3.0.0-1.centos6.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-appserver-4.9-20160127_1664.el6.1.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-cards-3.0.0-1.centos6.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-core-4.9-20160127_1664.el6.1.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-gdl1-4.9-20160127_1664.el6.1.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-gdl1-contentstore-3.0.0-1.centos6.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-gdl1-mysql-4.9-20160127_1664.el6.1.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-ldap-4.9-20160127_1664.el6.1.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-mime-4.9-20160127_1664.el6.1.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-sbjson-2.3.1-20160127_1664.el6.1.x86_64.rpm http://inverse.ca/rhel-v3/6/x86_64/RPMS/sope49-xml-4.9-20160127_1664.el6.1.x86_64.rpm
-
From what I have tested It is workable but it is just in a VM. Sure that it is a nice Webmail now, more modern and responsive
-
The new interface has some nice stuff, but not usable every day right now. For example no drag and drop for emails, not even a move option (you have to copy and then delete)
-
The new interface has some nice stuff, but not usable every day right now. For example no drag and drop for emails, not even a move option (you have to copy and then delete)
you're right and sincerely I don't understand it.. in v. 2 drag and drop is present and working
-
you're right and sincerely I don't understand it.. in v. 2 drag and drop is present and working
Salut Daniel, Hi,
The interface looks very nice, it's an approach to Office 365 web client (icons and menu) :
http://demo.sogo.nu/SOGo/so/ (user & password sogo2)
-
sure, but it lacks some features.. read above :-)
-
Hi
I hear what you are saying here, drag and drop not supported etc .., and thinking that will come etc ..
But - Do you think that Native support for Outlook is a possibility - is that a goal/possibility ( or perhaps a not a goal at all)?
there documentation contains - in the smb.conf:
realm = example.com
netbios name = sogo
passdb backend = samba4
––– Configuration required by OpenChange server –––
dsdb:schema update allowed = true
dcerpc endpoint servers = +epmapper, +mapiproxy
dcerpc_mapiproxy:server = true
dcerpc_mapiproxy:interfaces = exchange_emsmdb, exchange_nsp, exchange_ds_rfr
––– Configuration required by OpenChange server –––
so looking at realm - is that a possibility for SME to have a setting like that (or any other settings that would be required - smb.conf comes in for a quite a few extra settings)
-
But - Do you think that Native support for Outlook is a possibility - is that a goal/possibility ( or perhaps a not a goal at all)?
Native Outlook feature needs samba4, so no, it's not possible on SME for now. Anyway, this feature has so many limitations that I wouldn't count on it to be production ready anytime soon. You'd better try the ActiveSync support (requires Outlook 2013 or newer). It still has a few issues with resources consumption, but already more mature than MAPI support. Anyway, both of these features exist in SOGo 2 too, so no need to upgrade to v3 for them.
-
WOW !
I so nearly packed my case and went home
It works !
SME 9
+ SOGo
=> Plus : config setprop sogod ActiveSync enabled
Ok, so Outlook 2010 and earlier IMAP only, after that ActiveSync
and a promising looking Interface with SOGo 3
Thanks for the final tip about ActiveSync
-
I tried to do a simple yum upgrade of sogo to version 3, and then restarted sogod from /etc/init.d . But then got a "Proxy error" when trying to connect to sogo from my browser.
The sogo.log shows these errors:
Error (objc-load):libSOGo.so.2: cannot open shared object file: No such file or directory
EXCEPTION: <NSException: 0x7f16ec39d0c8> NAME:NSInvalidArgumentException REASON:NGImap4Connection(instance) does not recognize allFoldersMetadataForURL:onlySubscribedFolders: INFO:(null)
libSOGo.so.2 obviously can't be found, because of the upgrade to version 3. But I don't know which part of sogo wants to use the old library file.
I now have downgraded back to version 2.3.8-1
-
You most likely missed some sope packages updates
-
You most likely missed some sope packages updates
Very Strange, I had the same problem as Holck on my testing server, I update at the beginning of last week the Sogo Version, I had the new interface working v3, after that when I did an update, I got a "Proxy error".
Now I see that the last Sogo version on the repository is
[root@mail ~]# rpm -qa sogo
sogo-2.3.8-1.centos6.x86_64
Did Steph Rollback the Sogo version?
thank you
-
I only provide one rpm...smeserver-sogo...you need to install from official sogo repository. I don't understand what it occured and i have not really tested it in a real environment. I'm waiting some releases before to start the work.
Take a look in the yum log to see what it occured
EDIT : They have modified something, smeserver-sogo is incompatible now with sogo3
-
it seems that it is workable for a sme9 64bit but not for a 32 bit, does someone van confirm this ????
I smell the inverse bug :)
db yum_repositories set stephdl repository \
BaseURL http://mirror.de-labrusse.fr/smeserver/\$releasever \
EnableGroups no \
GPGCheck yes \
Name "Mirror de Labrusse" \
GPGKey http://mirror.de-labrusse.fr/RPM-GPG-KEY \
Visible yes \
status disabled
db yum_repositories set sogo3 repository \
BaseURL http://inverse.ca/rhel-v3/6/\$basearch \
EnableGroups yes \
GPGCheck no \
Name "Inverse SOGo Repository" \
IncludePkgs gnustep-base,libmemcached,libwbxml,sogo*,sope49* \
Visible yes \
status disabled
db yum_repositories set epel repository \
Name 'Epel - EL6' \
BaseUrl 'http://download.fedoraproject.org/pub/epel/6/$basearch' \
MirrorList 'http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=$basearch' \
EnableGroups no \
GPGCheck yes \
GPGKey http://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL \
Visible no \
status disabled
signal-event yum-modify
yum --enablerepo=stephdl,epel,sogo3,fws install smeserver-sogo
signal-event sogo-modify; config set UnsavedChanges no
-
in fact the update process is broken because they share same versions of sope between sogo2 and sogo3, but it seems that accordingly to this bug http://sogo.nu/bugs/view.php?id=3520 sope\* must be updated also. of course yum cannot do it itself, since the rpm version are the same.
then when I update from sogo3 repository, i have
yum update --enablerepo=sogo3
Mis à jour :
sogo.x86_64 0:3.0.2-1.centos6
sogo-activesync.x86_64 0:3.0.2-1.centos6
sogo-ealarms-notify.x86_64 0:3.0.2-1.centos6
sogo-tool.x86_64 0:3.0.2-1.centos6
sope49-cards.x86_64 0:3.0.2-1.centos6
sope49-gdl1-contentstore.x86_64 0:3.0.2-1.centos6
but here I have a proxy error (whatever the sme architecture)
I must reinstall all sope\* rpm
yum reinstall sope\* --enablerepo=sogo3
Installé:
sope49-appserver.x86_64 0:4.9-20160305_1664.el6.1
sope49-cards.x86_64 0:3.0.2-1.centos6
sope49-core.x86_64 0:4.9-20160305_1664.el6.1
sope49-gdl1.x86_64 0:4.9-20160305_1664.el6.1
sope49-gdl1-contentstore.x86_64 0:3.0.2-1.centos6
sope49-gdl1-mysql.x86_64 0:4.9-20160305_1664.el6.1
sope49-ldap.x86_64 0:4.9-20160305_1664.el6.1
sope49-mime.x86_64 0:4.9-20160305_1664.el6.1
sope49-sbjson.x86_64 0:2.3.1-20160305_1664.el6.1
sope49-xml.x86_64 0:4.9-20160305_1664.el6.1
then I can use sogo3 now, of course, all of this above concern an update, for a fresh installation, do
db yum_repositories set stephdl repository \
BaseURL http://mirror.de-labrusse.fr/smeserver/\$releasever \
EnableGroups no \
GPGCheck yes \
Name "Mirror de Labrusse" \
GPGKey http://mirror.de-labrusse.fr/RPM-GPG-KEY \
Visible yes \
status disabled
db yum_repositories set sogo3 repository \
BaseURL http://inverse.ca/rhel-v3/6/\$basearch \
EnableGroups yes \
GPGCheck no \
Name "Inverse SOGo Repository" \
IncludePkgs gnustep-base,libmemcached,libwbxml,sogo*,sope49* \
Visible yes \
status disabled
db yum_repositories set epel repository \
Name 'Epel - EL6' \
BaseUrl 'http://download.fedoraproject.org/pub/epel/6/$basearch' \
MirrorList 'http://mirrors.fedoraproject.org/mirrorlist?repo=epel-6&arch=$basearch' \
EnableGroups no \
GPGCheck yes \
GPGKey http://dl.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL \
Visible no \
status disabled
signal-event yum-modify
yum --enablerepo=stephdl,epel,sogo3,fws install smeserver-sogo
signal-event sogo-modify; config set UnsavedChanges no
In summary for an update to sogo3
db yum_repositories set sogo3 repository \
BaseURL http://inverse.ca/rhel-v3/6/\$basearch \
EnableGroups yes \
GPGCheck no \
Name "Inverse SOGo Repository" \
IncludePkgs gnustep-base,libmemcached,libwbxml,sogo*,sope49* \
Visible yes \
status disabled
signal-event yum-modify
yum update --enablerepo=sogo3
yum reinstall sope\* --enablerepo=sogo3
signal-event sogo-modify; config set UnsavedChanges no
As a side note, you still cannot use the drag and drop for an email, the webui is nice, but I smell still a bit young to be used
-
Hello,
Same issue here with new sogo3, can't access the mail module, Proxy Error.
nothing in bug tracker.
thx for answers
Sogo log :
Mar 16 18:03:30 sogod [31445]: [ERROR] <0x0x7f3581eae538[WOWatchDog]> No child available to handle incoming request!
Mar 16 18:03:30 sogod [31445]: <0x0x7f358218da78[WOWatchDogChild]> child 15648 exited
Mar 16 18:03:30 sogod [31445]: <0x0x7f358218da78[WOWatchDogChild]> (terminated due to signal 6)
Mar 16 18:03:30 sogod [31445]: <0x0x7f3581eae538[WOWatchDog]> child spawned with pid 18137
Mar 16 18:03:30 sogod [18137]: <0x0x7f3581e9c988[SOGoCache]> Cache cleanup interval set every 1800.000000 seconds
Mar 16 18:03:30 sogod [18137]: <0x0x7f3581e9c988[SOGoCache]> Using host(s) '127.0.0.1' as server(s)
EXCEPTION: <NSException: 0x7f35823a4408> NAME:NSInvalidArgumentException REASON:NGImap4Connection(instance) does not recognize allFoldersMetadataForURL:onlySubscribedFolders: INFO:(null)
Mar 16 18:03:30 sogod [31445]: <0x0x7f358218da78[WOWatchDogChild]> child 18137 exited
Mar 16 18:03:30 sogod [31445]: <0x0x7f358218da78[WOWatchDogChild]> (terminated due to signal 6)
Mar 16 18:03:30 sogod [31445]: <0x0x7f358218da78[WOWatchDogChild]> avoiding to respawn child before 2016-03-16 18:03:35 +0100
Mar 16 18:03:30 sogod [31445]: [ERROR] <0x0x7f3581eae538[WOWatchDog]> No child available to handle incoming request!
Mar 16 18:03:32 sogod [31445]: [ERROR] <0x0x7f3581eae538[WOWatchDog]> No child available to handle incoming request!
Mar 16 18:03:33 sogod [31445]: [ERROR] <0x0x7f3581eae538[WOWatchDog]> No child available to handle incoming request!
Mar 16 18:03:34 sogod [31445]: <0x0x7f3581eae538[WOWatchDog]> child spawned with pid 18140
Mar 16 18:03:34 sogod [31445]: <0x0x7f3581eae538[WOWatchDog]> child spawned with pid 18141
Mar 16 18:03:34 sogod [18141]: <0x0x7f3582108408[SOGoCache]> Cache cleanup interval set every 1800.000000 seconds
Mar 16 18:03:34 sogod [18141]: <0x0x7f3582108408[SOGoCache]> Using host(s) '127.0.0.1' as server(s)
EXCEPTION: <NSException: 0x7f35823a65d8> NAME:NSInvalidArgumentException REASON:NGImap4Connection(instance) does not recognize allFoldersMetadataForURL:onlySubscribedFolders: INFO:(null)
And httpd error
[Wed Mar 16 18:03:29 2016] [error] [client xx.xx.xx.xx] (20014)Internal error: proxy: error reading status line from remote server 127.0.0.1, referer: https://xx.xx.xx.xx/SOGo/so/xxxx/Mail/view
-
Which procedures did you follow.....which command lines did you do.
See my post above of yours
-
New update today, mail module is ok now.
thx
-
documentation added https://wiki.contribs.org/Sogo#Install_SOGO_3_.28ONLY_SME9.29
-
Salut Daniel, Hi,
The interface looks very nice, it's an approach to Office 365 web client (icons and menu) :
http://demo.sogo.nu/SOGo/so/ (user & password sogo2)
User & password is "sogo3"
-
Is anyone using this app for cell phone users to sync their accounts?
Can it be implemented for only a few select users or it it an all or nothing.
I looking for an easy way for remote cell phone users in the field to sync their email and calendars.
Thanks
-
documentation added https://wiki.contribs.org/Sogo#Install_SOGO_3_.28ONLY_SME9.29
Many thanks Stephane, I tested it this morning on my testing Sme 9.1 Server, I update successful from Sogo 2.x to Sogo 3.0, everything was working fine.
Then I disabled the old Sogo repository.
Hope that Sogo will re activate the drag and drop...
-
Is anyone using this app for cell phone users to sync their accounts?
Can it be implemented for only a few select users or it it an all or nothing.
I looking for an easy way for remote cell phone users in the field to sync their email and calendars.
Thanks
You might have a look at http://sogo.nu/bugs/view_all_bug_page.php (http://sogo.nu/bugs/view_all_bug_page.php). Search for activesync to get all bugs with mobiles.
My 2c
-
You might have a look at http://sogo.nu/bugs/view_all_bug_page.php. Search for activesync to get all bugs with mobiles.
Thank you I will check that out.