Sat, Jun 27
Fri, Jun 19
Sat, Jun 13
we are at kolab 3.4 . during creating new user Archive folder is not getting created.. Initially it was creating only Inbox. after doing repair of annotations.db from twoskip to skiplist . It again started created all folders except Archive. Need the solution.
Fri, Jun 12
May 25 2020
May 23 2020
May 22 2020
I've had this problem on debian 8,9 and 10
May 20 2020
This driver is not a high prio for us. Patches welcome.
Currently, the calendar uses the database backend:
The new_event method starts in database_driver and it starts _update_recurring. In this _update_recurring there is a calendar_recurrence object that creates Horde_Date_Recurrence on initialization where the problem is. :)
Yes, it using plugins/calendar/drivers/database/database_driver.php.
May 19 2020
Ok, I was testing a different case. However, this case also works with Kolab backend. I assume that you're using the database driver. Is it right?
Any info? :) Is there anything I can help you to resolve this bug ?
May 12 2020
Did attached screen help you repeat the error?
May 8 2020
I think that the screen from the application will explain the problem better :)
May 7 2020
It works for me with Kolab backend, although the event info dialog displays "Repeat: Every 1 month(s), forever ". When I edit the event Recurrence form looks correct and the event is displayed properly on the 3rd Thursday as defined. So, I see only a problem with the "Repeat" text not being complete.
May 6 2020
May 3 2020
Apr 29 2020
Apr 26 2020
Apr 19 2020
Thanks for your mail.
Apr 15 2020
Apr 13 2020
Can you elaborate further on what you mean by chain body?
Apr 11 2020
Apr 4 2020
Apr 1 2020
Mar 31 2020
Unfortunately missed this for 0.9.6, so I'll pick it up in the next release.
This has been resolved in packaging as far as I know.
Mar 30 2020
Here's an example of a more complex tls_config I use on my servers (using certbot + letsencrypt):
Mar 28 2020
You need to supply Guam with a valid X.509 certificate (issued by Let's Encrypt, for example) and adapt the tls_config section of /etc/guam/sys.config accordingly.
Guam should be listening on port 993, so please check if the Guam service is up and running.
Worked fine, I could't reproduce the issue. Closing this.