Hai,
I noticed this.

cat /usr/share/kopano/ldap.active-directory.cfg|grep Alias # Optional, default = kopanoAliases # Active directory: kopanoAliases # LDAP: kopanoAliases

But in my Samba4 AD, the kopanoAliases are set with otherMailbox.

@arndtw , with samba4 AD, make sure you run latest samba 4.8 or 4.9.
samba 4.7 better already n the queries, 4.8-4.9+ are multi-threaded which helps a lot and optionaly you can enable preforking in 4.9.

Look up what is indexed : ldbsearch -H $(samba -b|grep PRIVATE_DIR|awk '{ print $NF }')//sam.ldb -s base -b @INDEXLIST
Lookup BaseDN : ldbsearch -H /$(samba -b|grep PRIVATE_DIR|awk '{ print $NF }')/sam.ldb -s base -b "" defaultNamingContext
Edit : ldbedit -H $(samba -b|grep PRIVATE_DIR|awk '{ print $NF }')//sam.ldb -b CN=SCHEMA,CN=CONFIGURATION,DC=.....baseDN.

Lookup what you want to edit, and set : searchFlags: 1
Tip, ```` ldbedit -e nano -H ```… Gives you the nano editor.

And you need to run : samba-tool dbcheck --reindex on the server after the change’s
You need to run this on every DC once.

If someone is coming from Google to this page as he/she has the same error (like me g), check if you’ve incompatible versions of the python3 packages. I mixed them up with stable/unstable. After downgrading anything works fine.

By the way I wasn’t able to start kopano-search - but with the same error.

Best wishes

@fbartels

Good morning,

So after 3 weeks the initial search is supposed to be finished.

I however now have another issue, which I can’t work out.

In essence everything works, except the search in the “Deleted Items” folder is not triggered!

This is the log when I move an item from the sent items folder to the deleted items folder. The same happens for items that appear in Inbox.

Those folders are never triggered…

What do I need to do? What went wrong? Do I need to start the search all over again from scratch?

019-02-27 10:35:12,973 - index1 - INFO - syncing folder: "mrc" "Sent Items" 2019-02-27 10:35:12,974 - index1 - INFO - found previous folder sync state: 027C3D0073D19600 2019-02-27 10:35:12,982 - index1 - DEBUG - store A5096D7C3F404F6798579D650EE13FC1: deleted document with sourcekey 9995A8356BA047CD800EDEB80B480023D5CC5A00 0000 2019-02-27 10:35:14,252 - search - DEBUG - commit took 1.26 seconds (0 items) 2019-02-27 10:35:14,339 - index1 - INFO - saved folder sync state: 027C3D0075D19600 2019-02-27 10:35:14,340 - index1 - INFO - syncing folder "Sent Items" took 1.37 seconds (1 changes, 0 attachments) 2019-02-27 10:35:14,372 - index0 - INFO - syncing folder: "mrc" "Sent Items" 2019-02-27 10:35:14,374 - index0 - INFO - found previous folder sync state: 027C3D0075D19600 2019-02-27 10:35:14,420 - search - INFO - queue processed in 1.50 seconds (1 changes, ~0.66/sec) 2019-02-27 10:35:14,454 - search - INFO - saved server sync state = F77B3D000FB896009000000067B99600160000009995A83

Hi @nonic ,

I build containing a fix for this (and some other things) has yesterday been uploaded to https://download.kopano.io/supported/core:/pre-final/.

Can you give this a try and report back if the issue was resolved afterwards?

Hi @jhansen ,

since the archive isn’t immutable afaik it anyway does not qualify as a gdpr complaint archiving solution. This is btw also not what it was designed for. The archiver is more of a performance optimisation tool, where you offload old emails to slower storage (a second kopano-server process with its own database running on a different/slower setup).

The general recommendation is always to use an external mail archive (like for example Benno Mail), which is actually certified to be a compliant archiving solution.

@fbartels said in kopano-cli --list-users is empty and createuser script is not running:

t

The Debian Buster packages are not safe to use yet. Thats my personal opinion after trying these out.
A recompile also showed to many errors so its better to use kopano on stretch with the communitie packages.

Did you run kopano-cli --sync ?
If you followed a howto, please show the link of that also, that might help.
Im planning about the same but i wil use samba4 AD as backend and not plain ldap and on stretch.
There are not many good howto’s and since im setting up 2 kopano servers i’ll document everything…

When I do that I recieve:

container.getSettingsModel().set('zarafa/v1/plugins/mdm/zpush-server-version', '') undefined

After logout - login:

container.getSettingsModel().get('zarafa/v1/plugins/mdm/zpush-server-version') "2.4.3+0-0"

Hi,

NOT THE SOLUTION, cause it ignores the permissions, if you use the following parameter (Thought I solved it):

always_send_delegates = yes

Bob,

I don’t… I am a community user…

@irrlicht said in soft quota for mail clients?:

MUA (thunderbird, outlook…)

by saying MUA you are referring to clients that directly talk to your mta, is that correct? In kopano we can only enforce not sending when the soft quota is reached for clients that utilise kopano-spooler for sending out messages.

Ok many thanks fbartels !

I will upgrade my installation.

Best regards.

@fbartels said in kopano-migration-pst |NameError: name 'unicode' is not defined:

i don’t recognise the version extension, but our packaging is already at 8.7.0 for customers and 8.7.80 for the nightly downloads. I’d recommend to look for an update.

Hi @fbartels ,

thanks for your help. Its working with version 8.7.0.8-lp150.85.3

Information for package kopano-migration-pst: --------------------------------------------- Repository : Kopano Core (openSUSE_Leap_15.0) Name : kopano-migration-pst Version : 8.7.0.8-lp150.85.3 Arch : x86_64 Vendor : obs://build.opensuse.org/server:mail Installed Size : 231.7 KiB Installed : Yes Status : up-to-date Source package : kopano-8.7.0.8-lp150.85.3.src Summary : Utility to import PST files

@ckruijntjens said:

kan we also run kopano-spamd with python3.6?

Yes, but not out of the box, yet.
bg,
++umgfoin.

@fbartels thanks, this explanations from your provided link helped me.
Thatswhy i started the script in the Background python kopano-cleanup.py --user Daniel --wastebasket --days=0 & and get this output:

Deleted 3 item(s) for user 'Daniel' in folder 'Gelöschte Objekte'

The items are also really removed.

@thctlo said in Calendar / IMAP problem with meeting requests:

use sudo in the script

I would recommend otherwise. Just don’t install packages automatically, but give clear error messages to users that they need to install “tool x” to run the script.

@itserv no, no need to switch the schema. Just raise the user plugin logging to see which user has the invalid references and fix the user/group that is causing it.

Felix,

Im repeating installs based on the documation site and really its not getting easier to install it.
it laks, a clear install order, the documentation info is good, just hard to follow.
But yes, This is a big improvement https://kb.kopano.io/display/WIKI/Core
And that user did not read the “Configure SQL database” part.

@Manfred

Hi manfred. It does not resolve to a x.x.x.0 adress. ithink there is something else going on. however i can not find it.