hi bskoeln

i had the same issue after migrating from zarafa 7.2.1 to kopano. the solution in my case was to remove file /etc/mapi/zarafa.inf.

so based on this documentation: https://documentation.kopano.io/kopano_migration_manual/zcp_migration.html

remove zarafa packages: dpkg -l | egrep '(mapi|gsoap|libical|vmime|zarafa)' | awk '{ print $2 }' | xargs apt-get remove remove additional zarafa packages: apt-get remove packages installed with zarafa: apt-get remove -y -q python-itsdangerous-doc python-itsdangerous python3-itsdangerous libzcp-common-util0 libzcp-common-ssl0 libzcp-common-service0 libunwind8-dev libunwind8-dbg libunwind8 remove zarafa.inf file: rm /etc/mapi/zarafa.inf proceed with installation of kopano packages.

hope this helps someone.

regards,
daniel

Patrick, as discussed I have directed a question to Felix via chat.

I use an older version of the zarafa password change plugin but it did work.

Check internally in the code that it has the right references to the kopano commands.

If I remember correctly I may had to change in the code “zarafa-password” (or similar, can’t remember) to “kopano-password” and so on.

But the code now may be different to the version I had.

thanks @fbartels

@mcdaniels said:

As I use the nightly builds

Nightly builds are “bleeding edge”, that means you don’t necessarily improve stability, if you update regularly .

I suppose, packages built shortly following a beta-release contain more matured code than in between development-cycles. So this might be a trigger to update your packages.

Generally, if you’re dependant on a reliable setup and want to sleep well, too, I wouldn’t recommend to use these builds.

If I decide to update my installation: Do I always have to upgrade all modules to the same version?

Up to now, this wasn’t necessary. But imho there’s no guarantee that there won’t be changes requiring an update on several components.

You might watch the commits in the repositories or clone a copy of the src-tree and check current changes by git log

If you manage to build from the git-repo, you have the possibility to switch to another (more stable) branch from the repo. As stated by the Kopano-devs somewhere else, nightly builds track the master-branch.

++umgfoin.

No changes within Kopano core are required for this, could all be done within webapp because you can just define custom mapi properties. These values will not be compatible with other interfaces, like Z-Push or Outlook.

This should be possible via a WebApp plugin, but I am not the specialist to give you any concrete hints for that.

Yes, that sounds about right. Support is only on a community base and without any guarantee or sla. Software as downloadable from our servers are nightly releases, but we are also working with various distributions to get stable releases included into their repositories.

@Sunghost

Hi,

As far as I am aware, to use Kopano (e.g. webapp etc.), you do have to point your email into newly created users in Kopano.

If you want or need, you can also import the existing email into Kopano via the imap importer so that you have the full history of the emails you previously had.

You will have to use an MTA to deliver email to Kopano, either sendmail or postfix or perhaps others (I use sendmail, but I suspect I am the minority).

Yes, nothing really sensitive in those three. I have set them to public now.

PS: it’s not really a conscious process what goes into the changlog, but merely a list of the tickets assigned to the specific release (which were set to resolved of course).

Hi @nonic,

There are also possibilities with Kopano components: kopano-spooler can add a ‘disclaimer’ to your messages (https://documentation.kopano.io/kopanocore_administrator_manual/special_kc_configurations.html#kopano-spooler-plugins)

If you’re using WebApp, you can create a signature ‘template’, which is filled with the information in the Global Address Book. While this is not unchangeable, you can use this feature to create a common signature for all members of your organization. Check out https://documentation.kopano.io/user_manual_webapp/settings.html#signature-templating for details.

@fbartels said in How to download beta or final release:

@scottalanmiller who is “they” in your reply? Before releasing a beta or final for our subscription customers we internally do extensive tests for the distributions we have listed as supported.

“They” was a reference to the nightly code changes. “They” (the nightly amount of new code added) are small. Sorry if that was a strange way to say that.