Does nobody here know how to eliminate a single calendar entry by its internal ID?

@fbartels Hi Felx,
do you have any News for us about the “private/non-commercial users” licence?
The last info is about 3 weeks old.
Best regards

Just for the record: From a security standpoint you should only allow as few services/daemons as possible access to the password stored in LDAP - encrypted or not. Kopano works perfectly well using LDAP bind - so imho there is no reason to allow Kopano access to the stored password.

@fbartels said in working with huge mailboxes is close to impossible:

[…] the old zarafa client had an online mode that basically worked as a terminal for whatever was stored on the server, KOE/activesync requires all data to be downloaded to the local client first.

This was absolutely great about the old client. It was possible to have a 100GB shared Mailbox for all users that was easily accessible within the office (remote access was not so great) without the need for every single client machine to have a 100GB local copy of the shared mails. Now with Kopano/Activesync every single client PC will store a local copy of those 100GB, which will then also increase the backup storage needed for each of those clients from 30GB (normal Windows Installation) to 130GB (Win10+Mails).

And now if there are synchronsation problems you have to trigger a full resync of the 100GB. Not looking forward to doing this
Summary: everything was better in the old days
(ok, not everything. Mobile use in Outlook with activesync is soooo much better than the old zarafa cached mode)

@gstfl no. But you could use MariaDB.

The fact that there’s no logfile suggests that KOE is not even started. That could be caused by issues with the .Net and/or VSTO runtimes. You might find some additional information in the system event viewer; Outlook log entries sometimes contain an error or similar.

Solved.

The app was not “registered” in the AppStore anymore (missing “Installations” entry):

# univention-app list | grep -A3 kopano kopano-core Name: Kopano Core Latest version: 8.3.1.32 Installations: -- kopano-webapp Name: Kopano WebApp Latest version: 3.3.0.610 Installations: host.xyz.com -- kopano-webmeetings Name: Kopano WebMeetings Latest version: 3.0.0.92 Installations: -- z-push-kopano Name: Z-Push for Kopano Latest version: 2.3.7 Installations: host.xyz.com

You can register the app by the following command:

# univention-app register kopano-core

Thanks. But I realized right after, that i had simply forgotten that I had to manually add the “send-as” button, I was so sure that the “send-as” button just automatically appeared once I had configured a “send-as” identity under my Setting. So, in short, all is fine, nothing wrong with Kopano, just my mind.

@robing THANK YOU SO MUCH @robing IT FINALLY WORKS THX

Hi!

Sorry for the late answer. I did not see your post.

@fbartels said in Webapp - Certificate auth fails:

make the following changes to config.php of webapp define("DEFAULT_SERVER", "https://felix-KS-38462.lxd01.zarafa.lan:237/kopano"); // When using a single-signon system on your webserver, but Kopano Core is on another server // you can use https to access the Kopano server, and authenticate using an SSL certificate. define("SSLCERT_FILE", "/etc/kopano/ssl/admin-felix-KS-38462.pem"); define("SSLCERT_PASS", NULL); test if certificate overrides auth by loging in through webapp and giving wrong password
-> works

–> Yes, it is working.

adapt apache vhost
instead of setting up basic auth, I just hardcoded remote_user the following way SetEnv REMOTE_USER "user1"

–> I did the same test. Login with user “user1” is working. There is no “Login-window”.

test if loging still succeeds
-> it does and webapp loads completely.

–> Same for me.

If it weren’t for the fact that you can succesfully login without the basic auth I would say that there is a json parsing error in your users settings. The one way to make sure that this is not the case would be to create a new blank user and try to login with that user.
You should be able to see if it is indeed a parsing error by looking into the javascript console and maybe additionally the responses in the network tab in the developer tools of chrome.

I created a new user “user1” and tried to login with basic auth. The only error, I can see in the browser console is a 401 error for:
http://10.0.49.229/webapphttps/zarafa.php?subsystem=webapp_1502960818098

Javascriptconsole does not show anything in Chrome.

Do you have any idea, why there is the “401”-error?

Thank you for your help!!!

Regards,
Stril

@Sebastian

Nothing else is logged after Reason: (4) in the z-push-error.log file or from z-push-admin.

[ERROR] [USERKD] Ignored broken message (SyncMail). Reason: '4' Folderid: '019026a9ffa5497a8db81d23c9a23ee0703302000000' message id '019026a9ffa5497a8db81d23c9a23ee09b3113000000'

G

@Sebastian

Just emailed a session from the log to feedback@ for you.

G