Hello @markct ,

there is no configuration option to influence the subject of out of office messages.

Theoretically speaking all parts of the oof message go through /usr/sbin/kopano-autorespond you should be able to remove/replace these characters with e.g. sed inside of this script. Please be aware that this script will be overwritten during upgrade, so its better to create a separate copy and make the dagent use this instead of the original one (see man kopano-dagent for instructions).

Here we go.
Kopano 8.3.4 on a new fresh Ubuntu 16.04 is up and running. Got some problems upgrading the old ZarafaClient 7.1.13 up to 7.2.6 as 7.1.13 is not able to connect to Kopano-Server.
The new server got some faster harddrives and more RAM for the import of the Database. And with some tuning of MySQL i could reduce the time for the import of the 50g database from 25 hours down to 2 hours.

Another question which I would like to ask relating Microsofts Active Directory.
There is a new ADS Extension Tool. Now I have Zarafa settings and Kopano settings in my AD. How do I migrate the schema from Zarafa to Kopano? Some time ago I found a Whitepaper relating this, but I cant find it anymore.

Thanks again @fbartels, I then think I’ll dump them into /usr/local/bin/ and run them as user kopano.

Thank you, will try it that way :slight_smile:

We tracked down the issue to search folders being erroneously being created in the root of the public store, probably orphans from the migration from Zarafa to Kopano where the public store did not have a FINDROOT. The script used for deleting these orphans:

import kopano for folder in kopano.Server().public_store.root.folders(): if folder.hierarchyid==NNNNNNN and folder.prop(PR_FOLDER_TYPE).value == 2: print folder.hierarchyid findroot.delete(folder)

@olabre said in Use server date for e-mail when fetching with fetchmail:

seems like the same based on imapsync

Its not only based on imapsync, but simply a packages version of it. You can find some other migration ways in https://documentation.kopano.io/kopano_migration_manual/

@groupnet said in Unable to retrieve parents for relation groupmember: uid attribute not found:

Probably “uid” attributes for groups have been created in earlier versions

no, in my case it is a system that I just recently installed. and https://github.com/zarafa4ucs/zarafa4ucs/issues/53 indicates that the same values have been used in Zarafa as well.

Ok since dedicated Univention instances are not an option I am going to use new passwords.
Thank you for your ideas!

@joost001

No kopano KOE works only with outlokk 2013 and 2016
But as fbartels said you may backup your zarafa with kopano-backup tool from the new kopano install by pointing to the zarafa server as source and restore to the new kopano server

rg
Christian

Hi,

Thanks for your response, I check when I can update kopano core.

Best regards

OK, Thanks for explaining @fbartels.

@fbartels ok thank you for your rapid answer !

well yes, the backup was next on our task list - the way is clear either VM snapshot or full backup or mysql dump - but we did not get that far

Hi @gstfl ,

thanks for your report we actually already fixed this dependency a few days ago, but this updated version has not yet been uploaded to the download server. We’ll investigate this and will push some new downloads later today.

In the meantime: I would really not recommend to blindly installing all packages in the archive. There are quite some debug and development related packages in the archive, that are not needed for daily operation (only useful if a developers wants to debug something).

In the howto I gave a much better way to install the packages in a comment: https://www.pc-howto.com/kopano-der-neue-stern-am-groupwarehimmel-teil-1/#comment-152876

Hi @isol ,

in dagent.cfg

# The following e-mail header will mark the mail as spam, so the mail # is placed in the Junk Mail folder, and not the Inbox. # The name is case insensitive. # set to empty to not use this detection scheme. spam_header_name = X-Spam-Status # If the above header is found, and contains the following value # the mail will be considered as spam. # Notes: # - The value is case insensitive. # - Leading and trailing spaces are stripped. # - The word 'bayes' also contains the word 'yes'. spam_header_value = Yes,

Hi Bob,
im playing with kopano and AD LDAP since many days now.
Yes you are right the kopanoDynamicGroups and kopanoAddressLists are handled by kopano internally befor any postfix aktivities.
But you can play with additional virtual_alias_maps as i did.

The special_result_attribut is used for recursion, but it must be a DN or LDAP URL.
The kopanoFilter Attribute used by kopano is only a query fragment, and can not directly be used with special_result_attribut :-(

Assuming our kopanoDynamicGroup named grp-London has a kopanoFilter like this with email grp-london@<your-domain>

(physicalDeliveryOfficeName=London)

we expect something like this as URL result to use with special_result_attribut

ldap://<your-server-ip>:389/ou=users,dc=<your>,dc=<domain>?mail?sub?(physicalDeliveryOfficeName=London)

unfortunately we can not use URI with kopanoFilter :-(

My Workaround:
When using the dangerous ADSI-Editor you can change the attribute url of your kopanoDynamicGroup to use as our LDAP URI

And here is what we use in virtual_alias_maps
Our testfile ldap-kopano-dynGroup.cf

server_host = ldap://<your-server-ip> server_port = 389 search_base = dc=<your>,dc=<domain> version = 3 bind = yes bind_dn = <your-bind-dn> bind_pw = <your-bind-password> query_filter = (&(objectclass=kopanoDynamicGroup)(kopanoAccount=1)(|(mail=%s)(otherMailbox=%s))) result_attribute = sn leaf_result_attribute = mail special_result_attribute = url

running the command
postmap -v -q grp-london@<your-domain> /etc/postfix/ldap-kopano-dynGroup.cf

should now show the ldap queries and results we expect from within postfix.

Simply copy ldap-kopano-dynGroup.cf to ldap-kopano-addrList.cf and change the objectClass to kopanoAddrList to get the same for Addresslists.
You can also combine the query_filter to match both

Have fun
Tom
PS: as far as i know, there is no option to rewrite the results of special_result_attribute to prepend a string to kopanoFilter with something like result_format = ldap:// … … … %s

Hi Felix,

thank you for your reply.
I’ve tried your solution rebuilding the searchfoldes, but nothing happend.

Here is the log:

Sun Sep 3 21:20:44 2017: [warning] Shutting down Sun Sep 3 21:20:44 2017: [notice ] Still waiting for 8 worker threads to exit Sun Sep 3 21:20:45 2017: [info ] Shutdown all current sessions Sun Sep 3 21:22:49 2017: [info ] Audit logging not enabled. Sun Sep 3 21:22:49 2017: [info ] Starting kopano-server version 8.4.90 (pid 49225) Sun Sep 3 21:22:49 2017: [info ] Using epoll events Sun Sep 3 21:22:49 2017: [notice ] Listening for TCP connections on port 236 Sun Sep 3 21:22:49 2017: [info ] Coredump status left at system default. Sun Sep 3 21:22:49 2017: [notice ] Listening for priority pipe connections on /var/run/kopano/prio.sock Sun Sep 3 21:22:49 2017: [notice ] Listening for pipe connections on /var/run/kopano/server.sock Sun Sep 3 21:22:49 2017: [notice ] Connection to database 'kopano' succeeded Sun Sep 3 21:22:49 2017: [notice ] Querying database for searchfolders. This may take a while. Sun Sep 3 21:22:49 2017: [notice ] Loading search folders. Sun Sep 3 21:22:49 2017: [notice ] Done loading search folders. Sun Sep 3 21:22:49 2017: [crit ] Starting rebuild of search folders... This may take a while. Sun Sep 3 21:22:49 2017: [crit ] Rebuilding searchfolders of store 3 Sun Sep 3 21:22:52 2017: [crit ] Rebuilding searchfolders of store 29 Sun Sep 3 21:22:53 2017: [crit ] Rebuilding searchfolders of store 55 Sun Sep 3 21:22:53 2017: [crit ] Rebuilding searchfolders of store 81 Sun Sep 3 21:22:54 2017: [info ] Finished rebuild. Sun Sep 3 21:22:54 2017: [notice ] Startup succeeded on pid 49228 Sun Sep 3 21:22:54 2017: [error ] setSyncStatus(): collision Sun Sep 3 21:25:39 2017: [info ] Audit logging not enabled. Sun Sep 3 21:28:09 2017: [info ] Starting kopano-server version 8.4.90 (pid 49541) Sun Sep 3 21:28:09 2017: [info ] Using epoll events Sun Sep 3 21:28:09 2017: [notice ] Listening for TCP connections on port 236 Sun Sep 3 21:28:09 2017: [info ] Coredump status left at system default. Sun Sep 3 21:28:09 2017: [notice ] Listening for priority pipe connections on /var/run/kopano/prio.sock Sun Sep 3 21:28:09 2017: [notice ] Listening for pipe connections on /var/run/kopano/server.sock Sun Sep 3 21:28:09 2017: [notice ] Connection to database 'kopano' succeeded Sun Sep 3 21:28:09 2017: [notice ] Querying database for searchfolders. This may take a while. Sun Sep 3 21:28:09 2017: [notice ] Loading search folders. Sun Sep 3 21:28:09 2017: [notice ] Done loading search folders. Sun Sep 3 21:28:09 2017: [notice ] Startup succeeded on pid 49541 Sun Sep 3 21:28:11 2017: [error ] setSyncStatus(): collision Sun Sep 3 21:36:33 2017: [error ] Previous message logged 100 times Sun Sep 3 21:36:33 2017: [error ] setSyncStatus(): collision Sun Sep 3 21:44:56 2017: [error ] Previous message logged 100 times Sun Sep 3 21:44:56 2017: [error ] setSyncStatus(): collision Sun Sep 3 21:53:18 2017: [error ] Previous message logged 100 times Sun Sep 3 21:53:18 2017: [error ] setSyncStatus(): collision Sun Sep 3 22:00:04 2017: [error ] Previous message logged 80 times Sun Sep 3 22:00:04 2017: [info ] Start scheduled softdelete clean up Sun Sep 3 22:00:05 2017: [info ] Softdelete done: removed 0 stores, 0 folders, and 0 messages Sun Sep 3 22:00:05 2017: [error ] setSyncStatus(): collision Sun Sep 3 22:08:26 2017: [error ] Previous message logged 100 times Sun Sep 3 22:08:26 2017: [error ] setSyncStatus(): collision Sun Sep 3 22:13:00 2017: [error ] Previous message logged 54 times ....

Han

Ok, it works.For migrate from kolab3 -> kopano:

-Backup your Kolab3
-Export Adressbook&Calendar with Kolab-Webmail
-Delete the Kolab-Groupware-Folder (Calendar, Files, Journal …)

kopano-migration-imap --host1 [Kolab-IP]--user1 'primary.mail@adress.de' --password1 '#geheim' --ssl1 --authmech1 PLAIN -sep2 / --prefix2 "" --host2 [Kopano-IP] --user2 'user2' --password2 '#geheim'

Hi,

Thanks for your help with this issue. If your changes included the ones I posted in my diff then it surely compiles on OpenBSD and there will be one less patch (58 total) needed for Kopano in my tree.

Paul