[SOGo] Any experiences with TbSync w/ CalDAV & CardDAV Provider?
Hi! As most Linux distros began to roll out Thunderbird 78 recently and given the fact that sogo-connector for this version was (and perhaps is) a little bit problematic to use (to say it politely) I started to experiment with the TbSync and CalDAV & CardDAV Provider Thunderbird add-ons. See https://github.com/jobisoft/TbSync and https://github.com/jobisoft/DAV-4-TbSync/ So far the results are encouraging: the add-ons seem to work fine with SOGo for both calendar and contacts. Given the SOGo DAV base-URL, the add-ons find the user's calendar and address-book subscriptions automatically. Synchronisation seems to work fine in both directions. With TbSync users have to configure the SOGo account themselves. Users have to provide the correct SOGo CalDAV and CardDAV URLs as well as username and password in the TbSync admin GUI. After that, TbSync automatically detects all calendars and address books the user has subscribed to in SOGo. It even detects the colors assigned to each calendar. For a smaller organization with only a few users this is IMHO way easier for the admin as it is with the sogo-connector concept, where the admin has to provide a customized sogo-connector XPI file (we had that dicussion on this list a few weeks ago...) I did limited testing with a few calendars and address-books, though and can't say anything about large-scale installations. Therefore I'd like to ask if anyone can share good or bad experiences with these Thunderbird add-ons: Did you try these add-ons as alternative to sogo-connector? For how many users / calendars / address books? Are you happy with it? Did you find any problems? Thanks! - andreas -- Andreas Haumer | mailto:andr...@xss.co.at *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 OpenPGP_signature Description: OpenPGP digital signature
Re: [SOGo] Installing SOGo in an mutliserver environment
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Am 20.03.2017 um 16:08 schrieb michael.goldfin...@inhouse.wko.at: >> Am 20.03.2017 um 13:37 schrieb michael.goldfin...@inhouse.wko.at: >>> Hello, >>> >>> I try to achieve the goal to install SOGo in an multiserver environment. I >>> have 3 Servers available >>> >>> 1)Database-Server >>> >>> 2)Web-Server >>> >>> 3)Mail-Server Al Servers running CentOS in the current version. The >>> Database Server is running MariaDB and Postgresql, the Webserver is running >>> nginx with php-fpm, the Mail-Server is a minimal setup of CentOS 7. >>> >>> I want to install SOGo in a way that the DB is hold on the Database Server, >>> the Website is delivered through the Webserver and the rest is running on >>> the Email-Server. Is that kind of setup even possible and is there a >>> documentation about that? >>> >> >> Sure, this is a simple setup. But why MariaDB and Postgresql? > > We use some software that runs exclusively on MariaDB or Postgesql. Currently > we try reduce this to the most common base, so you can assume that in the > near future MariaDB ist the only Database on the server left. > We run several SOGo installations with DB-Server (PostgreSQL), Mail-Server (Cyrus IMAP) and SOGo-Server separated on different machines. On the SOGo server we always have apache installed (as proxy to SOGo on port 2/tcp) On some installations we additionally have a public webserver (apache) in front (as reverse-proxy, in a DMZ). On our installations we have CentOS and OpenSUSE running. Works and scales quite well! Especially with SOGo you have any freedom to choose your setup in a way it optimally fits your requirements. - - andreas - -- Andreas Haumer | mailto:andr...@xss.co.at *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iD8DBQFYz/W7xJmyeGcXPhERAvLgAKCFSrkuDo/pSK0Yc9vOQe4ncass6ACeKDks Lcpu1H365DLowa27vqXLrhM= =L5DV -END PGP SIGNATURE- -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] SOGo-1.3.8a or 1.3.8b on OpenSuse 11.3 64 Bit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Today I tried to upgrade SOGo on an OpenSuse 11.3 64Bit Server.
This server was running sogo-1.3.5a with a PostgreSQL
database backend for several months now without problems.
I used the OpenSuse packages from the home:/oeufdure:/SOGO/openSUSE_11.3
repository and tried to upgrade the packages found in the x86_64 repo.
The following packages got installed:
gnustep-base-1.20.1-1.1
gnustep-make-2.4.0-1.1
libmemcached-0.43-3.1
sogo-1.3.8a-131.6
libGDLContentStore4_9-1.3.8a-131.6
sope49-appserver-4.9-20110552.1
sope49-gdl1-postgresql-4.9-20110552.1
libGDLAccess4_9-4.9-20110552.1
libNGLdap4_9-4.9-20110552.1
libNGMime4_9-4.9-20110552.1
sope49-core-4.9-20110552.1
libNGCards4_9-1.3.8a-131.6
libSBJson2-2.3.1-20110552.1
sogo-devel-1.3.8a-131.6
sogo-ealarms-notify-1.3.8a-131.6
sogo-tool-1.3.8a-131.6
sogo-slapd-sockd-1.3.8a-131.6
sope49-xml-4.9-20110552.1
Now sogod doesn't start anymore! :-((
It runs in an endless loop logging the following messages
to the sogo log file:
version 1.3.8 (build abuild@build21 201108151422) -- starting
vmem size check enabled: shutting down app when vmem 384 MB
0x0x815530[WOWatchDog] listening on 127.0.0.1:0
0x0x815530[WOWatchDog] watchdog process pid: 30290
0x0x7f34e68378a0[WOWatchDogChild] watchdog request timeout not set
0x0x815530[WOWatchDog] preparing 1 children
0x0x815530[WOWatchDog] child spawned with pid 30291
|SOGo| WARNING: no component request handler key is specified, this
probably means that share/ngobjweb/Defaults.plist could not get loaded
(permissions?)
[we-rm] Note: component path caching is disabled!
0x0x7d7b00[WEStringTableManager] Note: label caching is disabled (slow!).
2011-09-03 22:37:25.101 sogod[30289] EOAdaptor: cannot find adaptor
bundle: 'PostgreSQL'
0x0x815530[WOWatchDog] an exception occured in runloop NSException:
0x883570 NAME:NSInvalidArgumentException REASON:Tried to add nil value
for key 'dbserver:5432:sogo:sogo' to dictionary INFO:{}
0x0x8385d0[WOWatchDogChild] child 30291 exited
0x0x8385d0[WOWatchDogChild] avoiding to respawn child before
2011-09-03 22:37:30 +0200
0x0x815530[WOWatchDog] child spawned with pid 30292
|SOGo| WARNING: no component request handler key is specified, this
probably means that share/ngobjweb/Defaults.plist could not get loaded
(permissions?)
[we-rm] Note: component path caching is disabled!
0x0x7d7b00[WEStringTableManager] Note: label caching is disabled (slow!).
2011-09-03 22:37:30.103 sogod[30289] EOAdaptor: cannot find adaptor
bundle: 'PostgreSQL'
0x0x815530[WOWatchDog] an exception occured in runloop NSException:
0x884e60 NAME:NSInvalidArgumentException REASON:Tried to add nil value
for key 'dbserver:5432:sogo:sogo' to dictionary INFO:{}
0x0x815530[WOWatchDog] Terminating with signal 15
0x0x8385d0[WOWatchDogChild] sending terminate signal to pid 30292
0x0x8385d0[WOWatchDogChild] child 30292 exited
0x0x815530[WOWatchDog] all children exited. We now terminate.
Note the warnings and errors. sogod seems to be unable to find
the PostgreSQL adaptor bundle, but it seems to be installed:
# ll /usr/lib64/GNUstep/GDLAdaptors-4.9/PostgreSQL.gdladaptor/
total 156
- -rwxr-xr-x 1 root root 148704 Aug 15 16:14 PostgreSQL
drwxr-xr-x 2 root root 4096 Sep 3 22:13 Resources
- -rw-r--r-- 1 root root 50 Aug 15 16:14 stamp.make
I also can't understand what the following message means,
but it seems to be related:
0x0x815530[WOWatchDog] an exception occured in runloop NSException:
0x884e60 NAME:NSInvalidArgumentException REASON:Tried to add nil value
for key 'dbserver:5432:sogo:sogo' to dictionary INFO:{}
I tried to rebuild the sogo-1.3.8a package from the source rpm
but this fails with the following errors:
ERROR: link target doesn't exist (neither in build root nor in installed
system):
/usr/lib64/libSOGo.so -
/usr/GNUstep/SOGo/SOGo.framework/Versions/Current/libSOGo.so
Add the package providing the target to neededforbuild and Requires
ERROR: link target doesn't exist (neither in build root nor in installed
system):
/usr/lib64/libSOGo.so.1 -
/usr/GNUstep/SOGo/SOGo.framework/Versions/Current/libSOGo.so.1
Add the package providing the target to neededforbuild and Requires
ERROR: link target doesn't exist (neither in build root nor in installed
system):
/usr/lib64/libSOGo.so.1.3.8 -
/usr/GNUstep/SOGo/SOGo.framework/Versions/Current/libSOGo.so.1.3.8
Add the package providing the target to neededforbuild and Requires
INFO: relinking /usr/lib/GNUstep/SOGo/SOGo.framework/libSOGo.so -
Versions/Current/libSOGo.so (was ./Versions/Current/libSOGo.so)
INFO: relinking /usr/lib/GNUstep/SOGo/SOGo.framework/SOGo -
Versions/Current/SOGo (was ./Versions/Current/SOGo)
error: Bad exit status from /var/tmp/rpm-tmp.u8pqhH (%install)
It seems te build process gets the GNUstep directories wrong. :-(
I'm currently running out of ideas of how to fix this mess, but
I need to get this running until monday morning! Help please!
Thanks!
- - andreas
- --
Andreas Haumer
Re: [SOGo] SOGo-1.3.8a or 1.3.8b on OpenSuse 11.3 64 Bit
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! Aarghhh! I found the error: Yast played tricks on me! Am 04.09.2011 00:00, schrieb Andreas Haumer: Hi! Today I tried to upgrade SOGo on an OpenSuse 11.3 64Bit Server. This server was running sogo-1.3.5a with a PostgreSQL database backend for several months now without problems. I used the OpenSuse packages from the home:/oeufdure:/SOGO/openSUSE_11.3 repository and tried to upgrade the packages found in the x86_64 repo. The following packages got installed: gnustep-base-1.20.1-1.1 gnustep-make-2.4.0-1.1 [...] In the minutes after I sent my mail I re-checked the GNUstep packages and found out, that the packages got installed from the original OpenSuse repository. Those packages have a different release number (though the version number is the same) and seem to install a different GNUstep environment than the packages from the home:/oeufdure:/SOGO/openSUSE_11.3 repository! I changed the packages to: gnustep-base-1.20.1-111.1 gnustep-make-2.4.0-47.1 from the home:/oeufdure:/SOGO/openSUSE_11.3 repository and now it works! SOGo runs fine and I could even build the SOGO-1.3.8b packages with the specfile from the 1.3.8a source-RPM! Sorry for the noise, I think it's time for bed now... - - andreas - -- Andreas Haumer | mailto:andr...@xss.co.at *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFOYqlYxJmyeGcXPhERAhdiAJwI3uixX6+3tUYIvr/lDHHkozgggQCglU2c f6+saOFXCVJxkVpNtQVPeWs= =2eQn -END PGP SIGNATURE- -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] EMail reminders do not work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
Milos Wimmer schrieb:
On Mon, 22 Nov 2010, Andreas Haumer wrote:
Nov 21 12:35:01 sogo-ealarms-notify [18844]:
[ERROR]0x0x8278560[SOGoEMailAlarmsManager] alarm number mismatch
for record: {c_alarm_number = 0; c_name =
2DDA-4CE90300-1-73A11E00.ics; c_path =
/Users/xss/Calendar/personal; c_recurrence_id = 0; c_uid =
2DDA-4CE90300-1-73A11E00; }
I already found bug #922 in the SOGo bugtracking system.
The description of this bug mentions a value != 0 for field
c_recurrence_id to be the cause of the problem, but in my
case this field is always 0!
Also bug #922 should be fixed in SOGo-1.3.4 but I see this
problem with SOGo-1.3.4 (I double-checked this: SOGo shows
version number 1.3.4 in the logs on startup)!
I can confirm this problem.
I found the same trouble on my system.
Good, I'm not alone... ;-)
Let me ask you some questions to see if there are any
similarities which might give us a hint for further bug
hunting:
* Did you compile the application from sources yourself or do
you use a binary package from the sogo website?
I did compile SOPE and SOGo myself from the official 1.3.4 sources.
* Do you use a 32 or a 64 bit system?
I'm using a 32 bit system
I don't currently know if anything else might be relevant.
- - andreas
- --
Andreas Haumer | mailto:andr...@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFM66H+xJmyeGcXPhERAnXiAJ9n8scoRnFJPt3okRMq0d2ekYbyVwCfWhj1
2w36cjtvDI2HE/8xJfxpkHk=
=LMBL
-END PGP SIGNATURE-
--
users@sogo.nu
https://inverse.ca/sogo/lists
Re: [SOGo] EMail reminders do not work
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Clay!
Thanks for your reply!
Am 22.11.2010 22:06, schrieb Clay Wright:
On 11/21/2010 06:09 AM, Andreas Haumer wrote:
I'm testing SOGo for some time now and it works fine, but it seems
I can't get email based reminders to work.
[...]
Nov 21 12:35:01 sogo-ealarms-notify [18844]:
[ERROR]0x0x8278560[SOGoEMailAlarmsManager] alarm number mismatch
for record: {c_alarm_number = 0; c_name =
2DDA-4CE90300-1-73A11E00.ics; c_path =
/Users/xss/Calendar/personal; c_recurrence_id = 0; c_uid =
2DDA-4CE90300-1-73A11E00; }
Hello Andreas. Are you using SOGo 1.3.4? There was a bug in the previous
version that could result in this issue.
http://www.sogo.nu/bugs/view.php?id=922
I already found bug #922 in the SOGo bugtracking system.
The description of this bug mentions a value != 0 for field
c_recurrence_id to be the cause of the problem, but in my
case this field is always 0!
Also bug #922 should be fixed in SOGo-1.3.4 but I see this
problem with SOGo-1.3.4 (I double-checked this: SOGo shows
version number 1.3.4 in the logs on startup)!
I think I have a different issue here.
- - andreas
- --
Andreas Haumer | mailto:andr...@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iD8DBQFM6t8pxJmyeGcXPhERApDxAJ9UUWei8kkPUzonXB35SFlNZuN5OwCgvqBl
xSJ/JoeaRN1u09PGIyHbWfU=
=Zm45
-END PGP SIGNATURE-
--
users@sogo.nu
https://inverse.ca/sogo/lists
[SOGo] EMail reminders do not work
not sure it's the same problem (this bug should be fixed in SOGo-1.3.4 anyway) Any idea? - - andreas - -- Andreas Haumer | mailto:andr...@xss.co.at *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFM6QwTxJmyeGcXPhERAlN3AKCydVLi5Fa/6FEoQHLQ+ej4jsetJgCgtXS3 Jef5MXMrlUPhsk+BZrLb+EE= =zfOB -END PGP SIGNATURE- -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Compilation problem with SOGo-1.3.2 and 1.3.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi! I'm running SOGo-1.3.1 successfully on a Linux server for some time now. Today I tried to upgrade to SOGO-1.3.2 and/or SOGo-1.3.3, but failed with the following compilation error: [...] make[2]: Entering directory `/work/packages/SOGo-1.3.3/SoObjects/Appointments' Making all for wobundle Appointments... gcc SOGoEMailAlarmsManager.m -c \ -MMD -MP -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -D_REENTRANT -fPIC -DDEBUG -fno-omit-frame-pointer -Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -march=i586 -fno-strict-aliasing -fgnu-runtime -fconstant-string-class=NSConstantString -I.. -I../.. -I../../SOPE -I../../SOPE/ -I. -I/home/andreas/GNUstep/Library/Headers -I/usr/GNUstep/Local/Library/Headers -I/usr/GNUstep/System/Library/Headers \ -o obj/Appointments.obj/SOGoEMailAlarmsManager.m.o SOGoEMailAlarmsManager.m:321: error: conflicting types for `alarmNbr' SOGoEMailAlarmsManager.m:321: error: previous declaration of `alarmNbr' make[3]: *** [obj/Appointments.obj/SOGoEMailAlarmsManager.m.o] Error 1 [...] I get the same error for both SOGo-1.3.2 and SOGo-1.3.3, but not with SOGo-1.3.1 (which does not contain this file) SOPE-1.3.2 and SOPE-1.3.3 compile just fine. On this Linux system I have gcc-3.3.4, gnustep-base-1.20.1 and gnustep-make-2.4.0 So far I could not identify the source of the error myself (but then, I'm only a C, C++ and Java developer without any knowledge of the abysms of Objective-C ;-) Any idea? Thanks! - - andreas - -- Andreas Haumer | mailto:andr...@xss.co.at *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMwWjJxJmyeGcXPhERAsyBAJ9Ooe4wuQJEwxxh/7kZ5aLyrQy/ywCfQiw7 laYAySkYr47daPKfDGZ43r4= =Z4rG -END PGP SIGNATURE- -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Compilation problem with SOGo-1.3.2 and 1.3.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
To follow-up my previous mail...
Andreas Haumer schrieb:
Hi!
I'm running SOGo-1.3.1 successfully on a Linux server for
some time now. Today I tried to upgrade to SOGO-1.3.2 and/or
SOGo-1.3.3, but failed with the following compilation error:
[...]
make[2]: Entering directory `/work/packages/SOGo-1.3.3/SoObjects/Appointments'
Making all for wobundle Appointments...
gcc SOGoEMailAlarmsManager.m -c \
-MMD -MP -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_RUNTIME=1
-DGNUSTEP_BASE_LIBRARY=1 -D_REENTRANT -fPIC -DDEBUG -fno-omit-frame-pointer
-Wall -DGSWARN -DGSDIAGNOSE -Wno-import -g -march=i586 -fno-strict-aliasing
-fgnu-runtime -fconstant-string-class=NSConstantString -I.. -I../..
-I../../SOPE -I../../SOPE/ -I. -I/home/andreas/GNUstep/Library/Headers
-I/usr/GNUstep/Local/Library/Headers -I/usr/GNUstep/System/Library/Headers \
-o obj/Appointments.obj/SOGoEMailAlarmsManager.m.o
SOGoEMailAlarmsManager.m:321: error: conflicting types for `alarmNbr'
SOGoEMailAlarmsManager.m:321: error: previous declaration of `alarmNbr'
make[3]: *** [obj/Appointments.obj/SOGoEMailAlarmsManager.m.o] Error 1
[...]
I get the same error for both SOGo-1.3.2 and SOGo-1.3.3, but
not with SOGo-1.3.1 (which does not contain this file)
SOPE-1.3.2 and SOPE-1.3.3 compile just fine.
I did some further investigation into the issue and I think I found the
bug: it's not in SOGoEMailAlarmsManager.m but rather in the header file
SOPE/GDLContentStore/GCSAlarmsFolder.h
As I said I'm not a Objective-C programmer, but to me it seems
in the declaration of method(?) writeRecordForEntryWithCName
there is a parameter mis-named: alarmNbr is used twice as parameter
name, seemingly with different types (NSNumber * vs. NSCalendarDate *)
When I apply the following patch:
andr...@test5:/work/packages/SOGo-1.3.3/SOPE/GDLContentStore {1066} % diff -u
GCSAlarmsFolder.h~ GCSAlarmsFolder.h
- --- GCSAlarmsFolder.h~ 2010-10-19 18:35:28.0 +0200
+++ GCSAlarmsFolder.h 2010-10-22 15:38:38.0 +0200
@@ -56,7 +56,7 @@
forUID: (NSString *) uid
recurrenceId: (NSCalendarDate *) recId
alarmNumber: (NSNumber *) alarmNbr
- - andAlarmDate: (NSCalendarDate *) alarmNbr;
+ andAlarmDate: (NSCalendarDate *) alarmDate;
- (void) deleteRecordForEntryWithCName: (NSString *) cname
inCalendarAtPath: (NSString *) path;
SOGo-1.3.3 compiles fine (though I haven't run it yet. I also have not
tested the patch for SOGo-1.3.2, yet).
Could anyone confirm this (or correct me, if I'm wrong), please?
One question remains: why does this construct compile for anybody else but me?
Thanks!
- - andreas
- --
Andreas Haumer | mailto:andr...@xss.co.at
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFMwZYFxJmyeGcXPhERAgqDAKCMFgjKUMXWxg2LVgrAlgR77ZtOaQCfU9Kx
xxQFdIR3OFtWn01LGYM54yo=
=GUsl
-END PGP SIGNATURE-
--
users@sogo.nu
https://inverse.ca/sogo/lists
