@cbnidk the pipeline has been cleaned, and the nightly builds are once again being published!

@anotherandy
thank you.
best regards

Hi fbartels,

Ok, i understand :)

I will do it.

Thanks,

Best Regards.

Hello @fbartels ,

thank your for your answer and your suggestion.
These are the not really satisfying result of two further tests:

Test A:
Created a private appointment in my calendar an invited thee employee and the meeting room.
Result: The appointment is visible for the invited employee. The appointment does not appear in the rooms calendar althought the settings are:

Auto-accept meeting req:yes
Decline dbl meetingreq: yes
Decline recur meet.req: yes

Test B:
Created a private appointment in the meeting rooms calendar and invited the employee and me.
Result: The appointment is visible for me, for the employee and marked as private in the meeting’s room calendar for everyone (closer, but no ideal)

Thanks for your help,

Stefan

@thomash did fixed the ACLs and did you set tne Path also in the MTA?

@fbartels
THX!!!
with your Links I was able to understand the Searchfilter.
The Solution was to change my ldap.cfg at line ldap_emailaliases_attribute = kopanoAliases toldap_emailaliases_attribute = otherMailbox like described in the postfix configuartion for ADS. The tag “kopanoAliases” only works with LDAP not with ADS.

P.S. i would say it can be marked as solved

Thx Felix.
We are currently running Z-Push 2.6.2 and Kopano 8.7.19.
I will ask the support and report back.

Hi @fbartels

Thank you for your answer.

I followed the recommendations from the performances tuning section of manual :
innodb_buffer_pool_size = 8G
innodb_log_file_size = 2G
innodb_log_buffer_size = 512M
max_allowed_packet = 32M

Do you have any suggestion on where to improve tuning or where to look to see what could cause the bottleneck ?

Thanks

@marty
Shebang in script: #!/usr/bin/python3

So should be running with python3. Maybe I missed out something. Are there additional modules to install with python?

kopano is running on SLES 12 SP5. Maybe someone has a tip what I could do to get search in public folders running for users.

Ulrich

@sky-x
Hey there
I got the exact same problem.
I have 7492 close-wait currently.

the version I use currently:
CORE_VERSION=10.0.6.13

@longsleep

Thanks, that did it!

@madpatrick

I rarely use those scripts, so I have no idea.
You might just want to try it on a test user and see what happens.

My guess is you have to use the Dutch name in your case.

@lantz Fantastic! :)

Happy to help.

@handyman Are you testing this with a normal account, or does the user you test with have kopanoAdmin privileges?

Admins always see all accounts, including the ones that are marked as ‘hidden’.

@micro why /var2/ and not just /var/

@chipsuk No worries. FYI this fix has just been merged, so it should show up in the next nightly.

@jank Did you find a solution for this problem?
And how did you manage to fix this?

Is the core-11.0.0.6 package fixed? Shouldn’t it be core-10.0.6?

@handyman with kopano-storeadm it is possible to unhook stores from users and hook them inside public folders. But I dunno if this is working the way which you want to realize. And I dunno if the automatism for ressource booking is still working afterwards.

@pixel I just set up spamd on Ubuntu and found that there’s a bug so that kopano-spamd creates the ham folder with root permissions so doesn’t have access to it after dropping priviledges. So the folder permissions have to be set manually to the correct user:group.