Categories

• Announcements

  New releases are announced here! If you have any feedback to a specific version, feel free to reply to these topics.

  Final releases

  Alpha, beta and RC releases
  164
  Topics
  511
  Posts

  

  @marty I think it would be an amazing enhancement. If I look at my own personal use, I keep flicking from one favourite folder to another all day. If they pre-load, it means that Webapp would essentially become super fast and instant for the users! A massive performance improvement… So you could set the pre-fetched folders to be the same as the favourite folders and job done…
• General Discussion

  A place to talk about whatever you want

  Development

  Projects
  151
  Topics
  683
  Posts

  

  Addendum: cd /etc/php/7.3/cli/conf.d ln -s /etc/php/7.3/mods-available/mapi.ini
• Kopano Groupware Core
  732
  Topics
  4613
  Posts

  

  Kopano-spamd is not automatically restarted after the kopano-server is restarted File “/usr/lib/python3/dist-packages/kopano/server.py”, line 806, in sync return _ics.sync(self, self.mapistore, importer, state, max_changes, window=window, begin=begin, end=end, stats=stats) File “/usr/lib/python3/dist-packages/kopano/ics.py”, line 253, in sync exporter.Config(stream, flags, importer, restriction, None, None, 0) File “/usr/lib/python3/dist-packages/MAPICore.py”, line 1906, in Config return _MAPICore.IExchangeExportChanges_Config(self, lpStream, ulFlags, lpUnk, lpRestriction, lpIncludeProps, lpExcludeProps, ulBufferSize) MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) 2019-03-19 09:36:28,577 - spamd - INFO - stopping spamd The expected behaviour is a still working Kopano-spamd service after for example a kopano-service restart for a configuration changement. Please change this.
• Kopano WebApp

  Plugins for Kopano WebApp
  474
  Topics
  2403
  Posts

  

  @longsleep Thank you so much for this detailed explanation! Once I have my setup running I’ll definitely return to the PIE problem and apply all the knowledge you have shared here. :) @fbartels You are right, I could have used the relevant tar files on the community server as well. That was probably my brain demanding a nap. Thanks for pointing it out! I have hit another road block by now that might have to do with kweb, so I am shamelessly plugging it in this thread. Issue: https://FQDN/api/gc returns 404 not found even though kapid and grapi are running. Steps taken: Follow the KC Admin Manual all the way to page 28 SSL certificate for the server [works] Configure and start kopano-server, including SSL, OID settings etc [works] configure and start kweb, including ACME [works] configure and test konnect [works] setup and start grapi [works] setup and start kapi [works] access /api/gc [fails] When kapid is started, the journal is populated like this: [root@testbench kapi-kvs]# systemctl status kopano-kapid ● kopano-kapid.service - Kopano API Daemon Loaded: loaded (/usr/lib/systemd/system/kopano-kapid.service; disabled; vendor preset: disabled) Active: active (running) since Wed 2019-03-20 01:47:20 CET; 46min ago Process: 2051 ExecStartPre=/usr/sbin/kopano-kapid setup (code=exited, status=0/SUCCESS) Main PID: 2053 (kapid) Tasks: 10 (limit: 2371) Memory: 80.0M CGroup: /system.slice/kopano-kapid.service └─2053 /usr/lib/kopano/kapid serve --log-timestamp=false --listen=127.0.0.1:8039 --log-level=info --plugins-path=/usr/lib/kopano/kapi-plugins --iss=https://hostname.domain.de Mär 20 02:32:11 testbench kopano-kapid[2053]: level=error msg="kvs: store initialize failed: failed to open database migration driver: attempt to write a readonly database" Mär 20 02:32:21 testbench kopano-kapid[2053]: level=error msg="kvs: store initialize failed: failed to open database migration driver: attempt to write a readonly database" Mär 20 02:32:31 testbench kopano-kapid[2053]: level=error msg="kvs: store initialize failed: failed to open database migration driver: attempt to write a readonly database" Mär 20 02:32:41 testbench kopano-kapid[2053]: level=error msg="kvs: store initialize failed: failed to open database migration driver: attempt to write a readonly database" All paths mentioned in the journal exist and are owned by kapi:kopano. At first start the error read something along the lines of “cannot open database kvs.db - file does not exist” so I have created an empty .db with sqlite kvn.db - but something seems to still be broken. The logs and journal however don’t provide any useful info to track the issue down. For reference, below is my current kapid.cfg. All folders mentioned here exist and are owned by kapi:kopano. The DB migration scripts also reside where they need to. ############################################################## # Kopano API SETTINGS # OpenID Connect Issuer Identifier. oidc_issuer_identifier= https://hostname.domain.de # Address:port specifier for where kapid should listen for # incoming connections. listen = 127.0.0.1:8039 # Disable TLS validation for all client request. # When set to yes, TLS certificate validation is turned off. This is insecure # and should not be used in production setups. #insecure = no # Comman separated list of plugin names which should be loaded. # If this is not set or the value is empty, kapid scans the plugins_path # on startup and loads all plugins found. #plugins = # Path to the location of kapi plugins. plugins_path = /usr/lib/kopano/kapi-plugins ############################################################### # Log settings # Log level controls the verbosity of the output log. It can be one of # `panic`, `fatal`, `error`, `warn`, `info` or `debug`. Defaults to `info`. log_level = info ############################################################### # Groupware REST API (grapi) Plugin settings # Path where to find Kopano Groupware REST (grapi) sockets. plugin_grapi_socket_path = /var/run/kopano-grapi ############################################################### # Pubs API (pubs) Plugin settings # Path to a key file to be used as secret for Pubs HMAC tokens. # If no secret_key file is set, a random value will be generated on # startup (not suitable for production use, since it changes on # restart). A suitable key file can be generated with # `openssl rand -out /etc/kopano/kapid-pubs-secret.key -hex 64`. #plugin_pubs_secret_key = /etc/kopano/kapid-pubs-secret.key ############################################################### # Key value store API (kvs) Plugin settings # Database backend to use for persistent storage of kvs data. A supported # backend must be set (sqlite3, mysql). Defaults to `sqlite3` if not set. plugin_kvs_db_drivername = sqlite3 # Database backend data source name. This setting depends on the storage # backend (plugin_kvs_db_drivername). A DNS is required to use the kvs plugin. # - For `sqlite3` the value should be the full path to the database file. # - For `mysql`, us a MySQL DSN in the following format: # [username[:password]@][protocol[(address)]]/dbname[?param1=value1&...&paramN=valueN] # See https://github.com/go-sql-driver/mysql#dsn-data-source-name for a # full list of supported MySQL DSN params with examples. # If not set and plugin_kvs_db_drivername is also not set a default value will # be used which uses SQLite3. plugin_kvs_db_datasource = /var/lib/kopano/kapi-kvs/kvs.db # Path where to find the database migration scripts. plugin_kvs_db_migrations = /usr/lib/kopano/kapi-kvs/db/migrations Second issue: My distro does not store webapp files directly under /usr/share but in /usr/share/webapps instead. konnect works, so generally should not be a problem. What I can not figure out is how I can point kweb to the actual kopano webapp. Any hints, please? The following paths when appended to https://FQDN/ return 404 not found /webapp/ /kopano-webapp/ /usr/share/webapps contains this: [root@testbench kapi-kvs]# ls -alh /usr/share/webapps/ insgesamt 40K drwxr-xr-x 7 http http 4,0K 20. Mär 00:22 . drwxr-xr-x 81 root root 4,0K 20. Mär 00:22 .. -rw-r--r-- 1 http http 1,2K 19. Mär 02:42 favicon.ico -rw-r--r-- 1 http http 138 19. Mär 01:37 index.html drwxr-xr-x 6 http http 4,0K 20. Mär 00:22 kopano-kdav drwxr-xr-x 3 konnect kopano 4,0K 20. Mär 00:22 kopano-konnect drwxr-xr-x 3 http http 4,0K 20. Mär 00:22 kopano-meet drwxr-xr-x 5 http http 4,0K 20. Mär 00:22 kopano-webapp -rw-r--r-- 1 http http 26 19. Mär 02:42 robots.txt drwxr-xr-x 8 http http 4,0K 20. Mär 00:22 z-push https://FQDN/ loads index.html which simply contains Hello World!.
• Kopano DeskApp
  122
  Topics
  536
  Posts

  

  actual neither the tiny nor the minimal editor can handle copied tables. great, so we’ll wait for new editors. sure, we can do this! thanks.
• Synchronising (mobile) devices via Z-Push

  General usage of Z-Push

  Z-Push when using Kopano

  Z-Push when using other backends
  345
  Topics
  2353
  Posts

  

  Finally it seems that unhooking and hooking the store of the user again solved these kind of error - crossing fingers…
• Kopano OL Extension (KOE)
  137
  Topics
  819
  Posts

  

  @afischer ah, that is the display name of the email address. we have no way to influence this. The setting only concern the display name of the contact itself.
• Kopano Meet & WebMeetings
  27
  Topics
  141
  Posts

  

  @ansib said in Kopano Meet with Kopano Web Daemon: I changed konnectd to authentication with ldap, which does not seem to work correctly. Yes, indeed at this moment (definitely for the packages in the “final” repo) Meet only really works with everything set to the Kopano backend. The goal for Meet (and the other apps you have spotted) is that they will in the future also work with other backends. @ansib said in Kopano Meet with Kopano Web Daemon: Does these three apps replace the not mobile ready webapp? yes, eventually these app will replace the current WebApp in general. These apps are not yet public, since they just exist as simple proof of concepts. But we are making good progress on them. Have a look at https://www.youtube.com/watch?v=sz2iDNHu9JI to get some impressions how these apps will look in the future.
• Kopano Mattermost

  For questions around the Mattermost packages provided by Kopano.

  12
  Topics
  69
  Posts

  

  Hi @mcdaniels , such very specific Mattermost questions are probably better suited for the Mattermost forum. You can find it at https://forum.mattermost.org/
• LibreOffice Online, Kopano Documents Editor and Kopano Documents

  Section for questions around LibreOffice Online, Kopano Documents Editor and Kopano Documents

  3
  Topics
  10
  Posts

  

  Hi Bob, thanks for the clarification. We will now go ahead and set up nextcloud, which we will link from the webapp. Kind regards, Chris
• Other Clients
  31
  Topics
  173
  Posts

  

  Hi Felix, thanks for your answer. I changed ICAL log to debug and made a test with Mozillas Thunderbird. While I create new entries within the calendar ICAL is logging every action. While I’m sending answers for invitations (accept/ deny invitation) ICAL log is silent but the MTA log and Kopanos Dagent are writing new entries. Nearly the same like they do, when they are processing new mails. So I guess Thunderbird is sending answers via SMTP trough the MTA. When I do the same with the Apple client ICAL, Dagent and MTA are not writing anything to their logs while I answer to invitations. I still think it has to be a configuration issue on the Mac. But there isnt much to configure, as mailclient and calendar both are configured und “working”. “sadly” its the only Apple client in this house =)
• Development

  Section about Kopano development. Home for talk about contributing, plugins and scripting.

  Contributing

  Scripting

  Translating Kopano

  WebApp & Plugins
  37
  Topics
  171
  Posts

  

  Hi, sorry for the late reply, i’d forget to watch my own topic :-((. With your suggestion it work’s like a charme. Is it planed to apply them automatically ? In my used version V8.6.9 here it does not. best regards and many thanks for you help Michael
• Legacy software

  Questions about Zarafa software

  31
  Topics
  160
  Posts

  

  HI @Coffee_is_life , I guess you are right :) didn’t noticed it. maybe it is a good idea to use your brain while fiddeling around with something unknown. but thats what testing system are for… In the end I maybe just slapcat the ldif file and afterwards sed ZARAFA and zarafa to kopano/KOPANO. btw. @fbartels I got a little problem the script further down too: grep: /usr/share/doc/packages/zarafa/zarafa.schema: Datei oder Verzeichnis nicht gefunden even more interesting I found the schema here: /usr/share/doc/zarafa/zarafa.schema.gz this is all a bit confusing, since I 've got no decent experience with ldap. But I haven’t broken it it, so there is still hope :) is it possible that there “extra informations” like ZARAFAQUOTAWARN where only used the yaffas and not zarafa itself? like you already said maybe I shouldn’t care so much about these schemas and just migrate and use it :) greetings 1of16