@fbartels

Thank you!

Regards
Richard

@schrorg

I had the same issue with the latest kopano-migrate-pst; Basically “PT_SRESTRICT” is misspelled in the defintion file which you can either correct manually or install the refering MAPI version:
For more information see:
https://forums.zarafa.com/showthread.php?13221-Import-pst-files-to-Kopano&p=57856&viewfull=1#post57856

Cheers

Version is kopano-backup_8.2.0.485-18.2_amd64.deb
on UCS4.1 with kopano 8.1 latest ucs app center version

when using kopano-backup_8.3.0~694-73.1_amd64.deb
i get mapi errors with no backup at all

2017-02-02 15:45:12,247 - backup - INFO - starting backup Thu Feb 2 15:45:12 2017: [error ] M4LMAPISession::OpenMsgStore() UnWrapStoreEntryID failed 80040107: invalid entry 2017-02-02 15:45:12,554 - backup - INFO - queued 16 store(s) for parallel backup (1 processes) 2017-02-02 15:45:12,571 - backup0 - ERROR - Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/kopano/__init__.py", line 4227, in log_exc try: yield File "/usr/lib/python2.7/dist-packages/kopano_backup/__init__.py", line 75, in main store = server.store(entryid=store_entryid) File "/usr/lib/python2.7/dist-packages/kopano/__init__.py", line 1092, in store return Store(guid=guid, entryid=entryid, server=self) File "/usr/lib/python2.7/dist-packages/kopano/__init__.py", line 1454, in __init__ mapiobj = self.server._store2(entryid) File "/usr/lib/python2.7/dist-packages/kopano/__init__.py", line 1062, in _store2 self._store_cache[storeid] = self.mapisession.OpenMsgStore(0, storeid, IID_IMsgStore, MDB_WRITE) File "/usr/lib/python2.7/dist-packages/MAPICore.py", line 1086, in OpenMsgStore def OpenMsgStore(self, *args): return _MAPICore.IMAPISession_OpenMsgStore(self, *args) MAPIErrorInvalidEntryid: MAPI error 80040107

Thank you for keeping me informed

I try to install myself the latest releases really just to help Kopano to move forward and find issues if I can.

The trouble right now is that I have to install the package, then work out what has changed or perhaps whether I should have installed it or not

Personally I think rather then in the package there should be a text file or something available with the JIRAs that have been closed and that we can inspect for that build online.

This is a lot more effective… you can work out what changed and which JIRAs were committed and then if you find a strange behaviour you can refer back.

I am really just trying to help here.

Yes, it seems not to work, thats why I created the ticket. And we were also able to solve your misconception of using an http(s) socket. So win-win I would say ;-)