@mcostan
There’s one thing that is different for me:
on my installation the script does not have any file ending and is located here:

root@myServer:~# ls -la /usr/sbin/kopano-recreate-systemfolders -rwxr-xr-x 1 root root 4518 Oct 9 12:10 /usr/sbin/kopano-recreate-systemfolders

@zkiss
Although your question is already quite old - I just hit the same point today. Means I could not remove a folder by latest WebApp from Supported Repo Source.

As a workaround - I took Outlook 2010 and old Zarafa Connector. With help of both I could remove the both folders from Users Kopano Archive Store. Since this worked out it seems actually being a bug in WebApp and I’m quite sure for those not having Outlook 2010 and old Zarafa Connector available - either fixing WepApp or using Python Script would help… If I find some time I will try to find solution for WebApp

Andreas

Hi @manfred ,

sorry for the late response. It happens on Outlook 2013/2016 with KOE 2.1.20 enabled. I’ve updated Z-Push to 2.6.1 and think the problem appeared from then on, but as there where christmas holidays nobody was working and the issue was undetected until january. Maybe it has something with 2.6.1 to do, as it also gets stuck at calendar syncs, which is reported here.
Just downgraded to Z-push 2.5.2, rebooted the server and wait what will happen in the next few hours…

Regards Peter

@thctlo

Yes i understand. i remove the oldest package. I want to thank you for your help.

Thanks a lot!

kind regards,

Chris Kruijntjens.

@tommi

Hi Tommy,

I have a same issue. if you upgrade kopano packages it breaks on the libical package.

any sollution to this???

You should be able to use postfix transport maps to achieve this.

@fbartels

adding ldap capabilities to my postfix server.
then adding lookup in ldap for users and aliases

now things work mostly as expected

usermail chief@mail.net OK
alias master-chief@mail.net OK
even with additional regex für + - delimiters like master-chief-justice@mail.net all OK

remove kopano and all related packages also.
One of them is blocking libkcpyplug due, not upgraded, or not have a “breaks” in the deb configuration.

when this happens, a packages is unable to upgrade of unable to be removed…

Make a local repo and put your deps in there and use that and install kopano again. through that repo.

the problem is, kopano lacks in the “development packages” the needed… breaks in the debian/control files is missing or not correct.

So basicly, dont install with dpkg -i *.deb

https://build.opensuse.org/package/view_file/server:mail:kopano/kopano/debian.control?expand=1

where it goes wrong in the control file.

libkcpyplug0 is build for kopano against a specific version and thats the problem when you upgrade. i needs something like breaks > version < version.

Hi @negrusti
Do you have an an anser to your question reagarding Gzip?
I’m tryiing to move as well to an S3 compatible storage (wasabi) and I’m wondeing, if I have to unzip first all attachments, How to doit?

Hi @fbartels,
thank a lot for you hint! This solved the issue!
or some reason the postfix user had been changed without me noticing it. As of the error message i had the impression the kopano SYSTEM user is somehow corrupt!
thanks again for your quick solution!!
(in parallel i’m trying to switch to lmtp after heaving the family read their mails again :) )
Regards
Florian

@tgm
start reading here :
https://forum.kopano.io/topic/1332/migration-from-db-to-openldap?_=1608114563424

offcourse… i did a bit back searching because most should be in the kopano forum already, but i see some external links dont work anymore.

The full setups you need to go through.

# # source : https://stash.kopano.io/projects/KC/repos/kopano-ads-source/browse/samba/kopano-samba-ads # In /etc/samba/smb.conf change/allow schema updates sudo sed -i 's/sdb:schema update allowed = no/sdb:schema update allowed = yes/g' /etc/samba/smb.conf sudo systemctl samba-ad-dc reload # If you install the ldiff from the DC itself. sudo bash kopano_schema_add.sh DC=INTERNAL,DC=DOMAIN,DC=TLD ./ldiff/ -v -H /var/lib/samba/private/sam.ldb -writechanges # or if you do a remote install in ldap (AD). #sudo bash kopano_schema_add.sh DC=INTERNAL,DC=DOMAIN,DC=TLD ./ldiff/ -H ldaps://hostname.your.domain.tld -UAdministrator%YourStrongPass -writechanges # Wait^^ after its finished give the ad time to sync if you have multple DC's. # revert the schema update allowed. sudo sed -i 's/sdb:schema update allowed = yes/sdb:schema update allowed = no/g' /etc/samba/smb.conf sudo systemctl samba-ad-dc reload

So thats adding the kopano Schema.

Now lookup what to index :
https://documentation.kopano.io/kopanocore_administrator_manual/configure_kc_components.html#configure-ldap-indices-in-openldap
( DO NOT use : cat optimize-index.ldif | ldapmodify -Y EXTERNAL -H ldapi:/// ) thats for LDAP. )

Adding the indexing to samba-AD-DC’s.
For the case of Samba AD we are editing a schema based database. Take into account that directly editing @INDEXLIST will not work, as @INDEXLIST is generated from the schema. We will need to edit the schema to ensure indexing on the desired attributes:

Now, verify which records al indexed.
ldbsearch -H /var/lib/samba/private/sam.ldb -s base -b @INDEXLIST

Then first find the base DN for your setup:
ldbsearch -H /var/lib/samba/private/sam.ldb -s base -b "" defaultNamingContext

Then edit the schema, using ldbedit and set searchFlags attribute to 1 on the attribute entry you want to index:
( examples, adjust with your values )
ldbedit -H /var/lib/samba/private/sam.ldb -b CN=SCHEMA,CN=CONFIGURATION,DC=S-AD1,DC=INTERNAL,DC=DOMAIN,DC=TLD

and change : searchFlags: 0 to : searchFlags: 1

when all is done.
stop samba and start samba. ( just to make sure things are ok )
now run : samba-tool dbcheck --reindex
this might take a while, wait untill its finish.

Repeat this on all AD-DC’s.

And its done, personaly i reboot the AD-DC to be sure its still fine after reboots and i check as last the index list to see its all applied : ldbsearch -H /var/lib/samba/private/sam.ldb -s base -b @INDEXLIST

Enjoy.