Good morning everyone,

i think i’ve found this bug:

This specific user turned on absence assistant before we used kopano via zarafa mapi client, connected to ZCP 7.2.4.
He came back, got a new pc with office2016 and Kopano via z-push and disabled the feature. The message was deleted but the automatic reply was still present.
Even turning oof on and off via ‘kopano-set-oof’ didnt solve this.

Solution:
Delete all outlook-profiles
restart computer
delete the local profile (windows)
resync it from server.
create new kopano-profile
turn on oof via kopano KOE
turn off oof via kopano KOE

didnt get a message since than. - Maybe the resync from server isnt needed, but i did it to be sure and it worked.

closed for me

Coffee_is_life

ok, with the additional of information that syslog logging has to be enabled for the error to occur I was able to reproduce this isse. https://jira.kopano.io/browse/KC-643 has been created to resolve this issue.

Since you are also delivering via pipe would say this is indeed related (referenced thread is https://forum.kopano.io/topic/167/critical-bug-core-8-4-0-273-dagent-not-delivering-mails-if-plugin-manager-is-enabled/).

This appears to be fixed in 8.4 or perhaps it was already fixed in a later version than the build I was using.

I guess the upgrade must’ve forced a reindex then?

Here the “results” of searching:

User is searching for “gehringer”. When it send via “outlook” then it produce:

2017-04-20 13:35:26,765 - query - INFO - performing query: (folderid:199) AND ((mapi55:inger*) OR (mapi66:inger*) OR (mapi101:inger*) OR (mapi3098:inger*) OR (mapi3103:inger*) OR (mapi3586:inger*) OR (mapi3587:inger*) OR (mapi3588:inger*) OR (mapi4096:inger*) OR (mapi32776:inger*) OR (mapi33348:inger*) OR (mapi34052:inger*) OR (mapi35542:inger*)) AND ((mapi55:gehr*) OR (mapi66:gehr*) OR (mapi101:gehr*) OR (mapi3098:gehr*) OR (mapi3103:gehr*) OR (mapi3586:gehr*) OR (mapi3587:gehr*) OR (mapi3588:gehr*) OR (mapi4096:gehr*) OR (mapi32776:gehr*) OR (mapi33348:gehr*) OR (mapi34052:gehr*) OR (mapi35542:gehr*)) 2017-04-20 13:35:26,767 - query - INFO - Response: OK: 2017-04-20 13:35:26,767 - query - INFO - found 0 results in 0.00 seconds

Then the next search is with “gehring” and found 7 matches

2017-04-20 13:35:16,303 - query - INFO - performing query: (folderid:199) AND ((mapi55:gehring*) OR (mapi66:gehring*) OR (mapi101:gehring*) OR (mapi3098:gehring*) OR (mapi3103:gehring*) OR (mapi3586:gehring*) OR (mapi3587:gehring*) OR (mapi3588:gehring*) OR (mapi4096:gehring*) OR (mapi32776:gehring*) OR (mapi33348:gehring*) OR (mapi34052:gehring*) OR (mapi35542:gehring*)) 2017-04-20 13:35:16,305 - query - INFO - Response: OK: 236320 234556 236125 235134 235385 235115 237250 2017-04-20 13:35:16,305 - query - INFO - found 7 results in 0.00 seconds

The search on the WebApp of “geringer” results with 12 matches

2017-04-20 13:36:09,561 - query - INFO - performing query: (folderid:193 OR folderid:238413 OR folderid:238393 OR folderid:238082 OR folderid:238071 OR folderid:234065 OR folderid:234060 OR folderid:227085 OR folderid:227054 OR folderid:216 OR folderid:215 OR folderid:214 OR folderid:213 OR folderid:209 OR folderid:208 OR folderid:207 OR folderid:206 OR folderid:205 OR folderid:204 OR folderid:203 OR folderid:202 OR folderid:201 OR folderid:200 OR folderid:199 OR folderid:238404 OR folderid:238392 OR folderid:238391 OR folderid:238083 OR folderid:238080 OR folderid:234094 OR folderid:234064 OR folderid:234063 OR folderid:227104 OR folderid:238081 OR folderid:234044 OR folderid:234038 OR folderid:234035 OR folderid:234023 OR folderid:238065 OR folderid:238057 OR folderid:238036 OR folderid:238032 OR folderid:238031 OR folderid:238023 OR folderid:234097 OR folderid:234096 OR folderid:234095 OR folderid:238026) AND ((mapi55:gehringer*) OR (mapi66:gehringer*) OR (mapi101:gehringer*) OR (mapi3098:gehringer*) OR (mapi3103:gehringer*) OR (mapi3587:gehringer*) OR (mapi3588:gehringer*) OR (mapi4096:gehringer*) OR (mapi12289:gehringer*) OR (mapi14850:gehringer*) OR (mapi14853:gehringer*) OR (mapi14856:gehringer*) OR (mapi14857:gehringer*) OR (mapi14870:gehringer*) OR (mapi14874:gehringer*) OR (mapi14875:gehringer*) OR (mapi14876:gehringer*) OR (mapi14877:gehringer*) OR (mapi14878:gehringer*) OR (mapi14879:gehringer*) OR (mapi14881:gehringer*) OR (mapi14883:gehringer*) OR (mapi14884:gehringer*) OR (mapi14885:gehringer*) OR (mapi14892:gehringer*) OR (mapi14894:gehringer*) OR (mapi14895:gehringer*) OR (mapi14917:gehringer*) OR (mapi14923:gehringer*) OR (mapi14935:gehringer*) OR (mapi32776:gehringer*) OR (mapi32911:gehringer*) OR (mapi32949:gehringer*) OR (mapi32970:gehringer*) OR (mapi32971:gehringer*) OR (mapi32972:gehringer*) OR (mapi33075:gehringer*) OR (mapi33091:gehringer*) OR (mapi33107:gehringer*) OR (mapi33241:gehringer*) OR (mapi34052:gehringer*)) 2017-04-20 13:36:09,565 - query - INFO - Response: OK: 236320 234556 236125 235134 235385 235115 230658 232267 232760 231868 232458 227460 2017-04-20 13:36:09,565 - query - INFO - found 12 results in 0.00 seconds

I just upgraded to 8.4.0~344 and I can confirm this problem is now gone. Thanks!

Hello @tengeleiter ,

since the file structure is still the same wehter you use attachments on disk or on s3, I would say that you have a configuration mistake.

Edit: correction since this thread has been mentioned somewhere else. My statement about the file structure was a misconception from my side. The file structure is actually not the same. Instead all attachments are stored directly below what has been configured as ´attachment_path´.

Fun Fact: userB is some kind of shared store with several aliases (info@domain, registration@domain, …). UserA want’s to send some mails as info@domain and some others as registration@domain and so on…

@fbartels

Hi Felix,

yes did the download from ucs4 packages - trying debian 8 now - working

rg
Christian

Hi @michael ,

you can use the following howto for this https://awesome-it.de/2015/01/09/mail-address-tags-with-zarafa/. But be aware that you normally should not do manual updates to configuration files on Univention as they will get overwritten. You either have to make changes to the configuration templates or through the Univention configuration registry.

@fbartels

Ok after removing z-push webapp core and reinstalling them search works as expected,

rg
Christian

Thanks Felix.

ineed it was odd. I am pretty sure Id updated both Zarafa builds before the migrations but who knows. I guess I could have moved and Chowned. That wouldnt have fixed the errors showing same as noted in KC-104 though.
Anyway its all fixed now in both my servers.
Ray

Okay, it’s pretty embarassing but sometimes I am just dumb. I edited /etc/kopano/ldap.active-directory.cfg while /usr/share/kopano/ldap.active-directory.cfg was included in ldap.cfg.

I followed your advice now and put my settings at the end of ldpa.cfg and it works like a charm now.

Thank you for your help and sorry again for my dumbness :D

cheers

gladston3

Just delete $mydomain from mydestination.

thanks for your help. That seems to solve my problem.

Thanks,
This solve the issue!

Hello @cbnidk ,

LDAP indices are explained in the Kopano documentation and Knowledge Base.

@teka74 said in Spam is not sorted into Junk Folder:

But now it’s nearly done, a secured server, only ssl/tls access, ssl/dane email transport,
and kopano as backend !

Great to hear you are happy about your kopano system! :)

Bo

Not in WebApp, perhaps a dagent plugin can help you. Take a look at https://github.com/zarafagroupware/zarafa-tools/tree/master/plugins for examples.