D127 together with D123 are fixing unit tests. Now the output is:

[root@kolab pykolab]# nosetests ./tests/unit
...............................Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/objectvalidation.cpp 94:   event.start() is not set
Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/xcalconversions.h 1500:   Start date is missing, but is mandatory for events
Debug: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/kolabformat.cpp 94:   Error occurred while writing.
.......................unnamed app(16962) KCalCore::ICalFormatImpl::populate: No PRODID property found
unnamed app(16962) KSystemTimeZonesPrivate::readConfig: readConfig(): local zone= "UTC"
unnamed app(16962) KSystemTimeZonesPrivate::readZoneTab: readZoneTab( "/usr/share/zoneinfo/zone.tab" )
.....unnamed app(16962) KCalCore::ICalFormatImpl::populate: No PRODID property found
.....(20:39:09) timezoneconverter.cpp(51):      Guessed timezone and found:  "" 
(20:39:09) commonconversion.cpp(44):    invalid timezone:  "None" , assuming floating time 
.unnamed app(16962) KCalCore::ICalFormatImpl::populate: No PRODID property found
.Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/utils.h 114:   bad numeric conversion: negative overflow
Error: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/utils.h 114:   bad numeric conversion: negative overflow
schema exception
:25:25 error: value '' does not match regular expression facet '(\-|\+)?\d{4}\-\d{2}\-\d{2}T\d{2}:\d{2}:\d{2}(\.\d*)?Z?'
Critical: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/xcalconversions.h 1940:   Failed to parse calendar!
Debug: /home/abuild/rpmbuild/BUILD/libkolabxml-1.2/src/kolabformat.cpp 94:   Error occurred while writing.
........................................................................S.
----------------------------------------------------------------------
Ran 140 tests in 2.898s

I've tried to create an init script, but as I don't really understand how erlang things are started / stopped, I have to give up here. That's what I achieved so far:

Assigning to @seigo for review of D108.

Back-ported https://git.cyrus.foundation/rI67bac5df9c1f667d1632b4f7bb57fb00873975aa from master.

I still can't get guam work with Cyrus Murder, although it is not clear if that depends on if guam is talking to Murder or standalone server. Guam configuration is:

So it looks like the '*' wildcard doesn't work in a mixed version murder environment (backend 2.5.6 and frontend 2.5.7) doesn't work. When all cyrus-imapd instances are of the same version - no more segfaults.

In T1062#16492, @vanmeeuwen wrote:

In T1062#16491, @adomaitis wrote:

If I run

. GETMETADATA (DEPTH infinity) "*" (/shared/vendor/kolab/folder-type)

Against 2.5.7:

Protection error: Connection reset by peer

messages log file shows:

kernel: proxyd[17138]: segfault at 7ffffff8 ip 00007f0ef1d5dab4 sp 00007ffca2cf2aa0 error 4 in libc-2.17.so[7f0ef1d15000+1b6000]

I cannot reproduce this, but I'm running this on Santiago, and you are running Maipo.

In T1062#16491, @adomaitis wrote:

I can't confirm the issue with guam still displaying groupware folders from Cyrus Murder is fixed.
Detailed description:
I have murder cluster running with cyrus-imapd-2.5.6-8.1. Frontends and Backends have commented suppress_capabilities: METADATA config option.

I can't confirm the issue with guam still displaying groupware folders from Cyrus Murder is fixed.
Detailed description:
I have murder cluster running with cyrus-imapd-2.5.6-8.1. Frontends and Backends have commented suppress_capabilities: METADATA config option.
I have added yet another frontend cyrus-imapd-2.5.7-8.1 to the cluster (from Winterfel repositories). Guam service is running on port 9143 on this new machine as well.

The fix for this is in https://git.cyrus.foundation/D86

It is the frontend that proxies a GETANNOTATION command to the backend, even though the original command is GETMETADATA.

Investigating where the issue is exactly.

Reverted jquery update in bf91666621.

That's likely what will happen if we want to release 1.2 soon. I'll see if jQuery-UI update helps, but again probably too late for such a change in 1.2.

Can you switch back to the older version?

This broke in my recent performance improvements in libkolab plugin code. https://git.kolab.org/rRPK52053f355af6c09db547f1b8d02bb9ae88abcb1c So, it's Winterfell only.

Updating the ticket to reflect the new semantics.

This must have been Debian Wheezy, Jessie already ships 1.0.14:

Wouldn't it make more sense to use [CapabilityBoundingSet=](https://www.freedesktop.org/software/systemd/man/systemd.exec.html#CapabilityBoundingSet=) instead and keep it running as guam user?

So, looks like client issue. I'll leave this open as a request to handle better such situations, i.e. to not even try to connect to SMTP and return better error.

Got it going!

The apache access log is telling me:

In T1057#15236, @sicherha wrote:

To support Trusty, we'll need a custom init script. For the other distros, we can use the existing systemd .service file.

To support Trusty, we'll need a custom init script. For the other distros, we can use the existing systemd .service file.