Hey everybody, after testing i have recognized that it is not working :( So by now i am really running out of ideas. What could be the root cause for the disk error? The dump was a clean one out of the original sys like described in the manual… It would be great if someone would have some ideas and suggestions. Thanks in advance and sorry for any confusions… icey

@Manfred Well it seems like something is going wrong already here https://github.com/Z-Hub/Z-Push/blob/master/src/backend/imap/imap.php#L1248 where the flagstatus is set to ‘FollowUp’ while this (https://github.com/Z-Hub/Z-Push/blob/master/src/lib/syncobjects/syncmailflags.php#L32) line clearly states in the comment that the only options are ‘clear, complete and active’. But the idea that there are three options for a flag already does not comply with the RFC that states the flag should be binary: either it’s there or it isn’t. Let me follow that path and test.

@WalterHof said in Request for feedback: easily run Kopano through Docker: we support […] virtualization[s] I don’t think it has to be “virtualisation” OR “containerisation”, but can work hand in hand. But I agree that getting into containerisation takes some effort and may not be worth while in all environments (especially when throwing Kubernetes into the mix)

@plzk-de yes, of course I have verified the version. The 2.2.x release has also been available in meet:master for a while. So its not like this update comes out of the blue.

Today I tested the same on a Xiaomi A3 with Android 10 and the default Google Calendar app v2020.20.4-316065245 and everything works! It looks like the issue just persists on some Android Phones with a proprietary Calendar App like Samsung or some Huawai devices. I have a devices to reproduce the issue. @fbartels: does Kopano like to follow this issue or do you think, only “old” Andorid devices are affected and it doesn’t have an impact for your paying customers? Probably @boospy has more interessts to get it fixed as he has a Kopano Subscription. Best regards Matthi

Thank you for your answer. It could be that i removed https:// by myself while debugging my problem and i understand your explanation. I re-checked your lates .deb and there in both files the “https://” is present. So it seems to be ok. I will re-test with your debs and a clean install of your plugin. Thanks for your help.

@zhay MDM master (and soon version 3.1) contains a workaround for konnect.

@robsie said in Drag and drop elements and attachments: yes, we think so too :-) Yes, Linux (KDE Plasma) would be really nice.

To keep noting my progress for anyone interested or stumbling on the same. Of course Outlook is the eternal problemchild, so I figured out some extra PHP settings that make it work. Kind of Reduce SYNC_MAX_ITEMS to something like 100 in /usr/share/mydomain.nl/src/config.php Increase the max_execution_time and max_input_time for PHP to at least an hour Increase the PHP memorylimit, something like 512M or even higher Android clients work fine with ActiveSync, of cource it’s the horror that is Outlook that crashes and burns. This is quite a large mailbox, needs to be said.

I did - but i have forgotten to enable it with “enable_sso = yes”. Maybe there are too many parts and peaces for me to configure (i feel so dump). After enable sso in server.cfg it is working. Many thanks for your support!

OK, I kind of had that feeling myself. The question is then, is this something that will be possible in the future? Would the best work-around currently be to make sure you are an attendee to the meeting, that way the appointment would also show in your personal calendar, and you would get a reminder?

@Finji in the past it was that the higher versions were simply the nightly. In core versions ending with .80 (up until .99) were nightlies or beta/rc leading up to a new final. For the future in core x.0.y will be nightly and the first customer version will then be x.1.y.

Hi Marty, until when is Files 3 available? Thank you, Robert

@jengelh Since I’m struggling with crashes in conjunction with zarafaclient I would really appreciate to get installer “zarafaclient-7.2.6-52190.msi”.

Hi @WalterHof, the +38 is just an internal build reference added by our build system, from a code and packaging perspective the software in core:final and core:pre-final is identical.

Hi @KaBi, the actual backup data is stored in Berkeley DB files, which probably were corrupted when your disk ran out of space. Berkeleydb is a well used technique and there are external tools to inspect and repair these files.

Sorry to say, but in the mean time we got the first crash of the script on the server as well. Maybe it is less prone to failure as the communication is faster on the same machine? Anyway, even if the culprit would be a firewall or SSL problems, the script would always fail. However, it does it only occasionally. This is an example of failures of today (grepped ‘MAPI error’ from unit journalctl output): Jun 26 00:14:58 server04.exampledomain.net testscript[19187]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 00:42:28 server04.exampledomain.net testscript[19337]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 00:42:58 server04.exampledomain.net testscript[19445]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 00:50:28 server04.exampledomain.net testscript[19455]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 01:09:58 server04.exampledomain.net testscript[19495]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 01:33:58 server04.exampledomain.net testscript[19592]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 01:56:58 server04.exampledomain.net testscript[19692]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 01:59:59 server04.exampledomain.net testscript[19784]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 02:41:29 server04.exampledomain.net testscript[19805]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 02:44:29 server04.exampledomain.net testscript[19982]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 02:49:29 server04.exampledomain.net testscript[19996]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 03:47:30 server04.exampledomain.net testscript[20016]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 04:00:00 server04.exampledomain.net testscript[21506]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 04:36:00 server04.exampledomain.net testscript[21568]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 04:37:30 server04.exampledomain.net testscript[21742]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 04:44:30 server04.exampledomain.net testscript[21749]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 04:45:30 server04.exampledomain.net testscript[21788]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 04:49:30 server04.exampledomain.net testscript[21799]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 04:55:00 server04.exampledomain.net testscript[21814]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 04:56:31 server04.exampledomain.net testscript[21843]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 05:05:30 server04.exampledomain.net testscript[21862]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 05:13:30 server04.exampledomain.net testscript[21924]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 05:33:00 server04.exampledomain.net testscript[21968]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 05:35:30 server04.exampledomain.net testscript[22048]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 05:40:00 server04.exampledomain.net testscript[22062]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 05:51:00 server04.exampledomain.net testscript[22088]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:03:01 server04.exampledomain.net testscript[22138]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:05:00 server04.exampledomain.net testscript[22213]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:07:30 server04.exampledomain.net testscript[22224]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:23:01 server04.exampledomain.net testscript[22237]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:30:00 server04.exampledomain.net testscript[22308]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:33:30 server04.exampledomain.net testscript[22347]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:35:01 server04.exampledomain.net testscript[22362]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:36:01 server04.exampledomain.net testscript[22372]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:37:00 server04.exampledomain.net testscript[22381]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:43:00 server04.exampledomain.net testscript[22391]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:48:31 server04.exampledomain.net testscript[22430]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 06:51:01 server04.exampledomain.net testscript[22450]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 07:38:01 server04.exampledomain.net testscript[22606]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 07:45:01 server04.exampledomain.net testscript[22676]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 07:45:30 server04.exampledomain.net testscript[22716]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 07:47:00 server04.exampledomain.net testscript[22725]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) Jun 26 07:55:01 server04.exampledomain.net testscript[22734]: MAPI.Struct.MAPIErrorNetworkError: MAPI error 80040115 (MAPI_E_NETWORK_ERROR) As the ICS loop is running every second, there are not too many failures, but each of them is killing the script. The Test script we use: #!/usr/bin/python import kopano import sys import time import logging logger = logging.getLogger('TEST') format="[%(filename)-10s:%(lineno)-5s - %(funcName)35s] - %(message)s" level = logging.DEBUG logger.setLevel(level) formatter = logging.Formatter(format) sh = logging.StreamHandler() sh.setLevel(level) sh.setFormatter(formatter) logger.addHandler(sh) logger.info('Start TEST') # Delete all command line arguments: Trick to circumvent the parser of Kopano modules sys.argv = [sys.argv[0]] # Kopano Server, User and Password kopano_server = 'http://xxxx:236/kopano' kopano_user = 'xxx' kopano_password = 'xxx' kopano_folder = 'Inbox' # Set up importer class for class Importer: def update(self, item, flags): if ( flags != 0 ): logger.debug('New Mail: ' + item.entryid + ' ' + item.subject) if __name__ == '__main__': # Login to Kopano Server # Change this to kopano.server starting from Kopano 8.8 on server = kopano.Server(server_socket=kopano_server, auth_user=kopano_user, auth_pass=kopano_password) # Open store of user and inbox folder store = server.user(kopano_user).store folder = store.folder(kopano_folder) # Get current state from folder folder_state = folder.state logger.debug('Retrieved new state from folder: ' + folder_state) # Check folder each second x = 1 while ( x == 1 ): # Get new state of folder, process files since last state during this process new_state = folder.sync(Importer(), folder_state) # Set new state if necessary if new_state != folder_state: logger.debug('Retrieved new state from folder: ' + new_state) folder_state = new_state time.sleep(1) sys.exit(0)