Kopano mailbox export
-
I have searched the forum for this topic already, but all threads I’ve found on this or similar topics are three years or older and I hope that something has changed since then (although I can’t find anything in the Kopano manual either…):
Is there any feasible way to export multiple Kopano mailboxes? I’m currently looking for a way to export and migrate 85 Kopano mailboxes to Office 365.
We could probably connect to each single mailbox with Outlook via Z-Push and export the mailboxes into PSTs or CSVs from there. But doing that for 85 mailboxes would probably take days considering each mailbox will have to sync completely first before I could export them completely.
Is there a more reasonable way of exporting mailboxes?
-
@meidner
as you go to o365 you’ll have already outlook client on the pc’
so add the kopano mialbox per user as 2nd mailaccount in outlook with activesync connection (no need of KOE)
then the user is able to migrate mails, calendar tasks and addressbook inside outlook to the new o365 accountrg
Christian -
I would recommend Outlook 2010 + zarafaclient-7.2.6-52190.msi - Exchange ActiveSync is not as complete as the native integration which still works - especially if you want to move calendar / contacts / notes data. Also no full sync required for the native zarafa client. It might take some time, so maybe use a couple of VMs to run parallel exports?
-
@gerald
But with outllook 2010 you’re unable to connect to o365 -
If it’s only mail, you could give imapsync (https://imapsync.lamiral.info/) a try. I migrated my family office mailboxes to https://mailcow.email/ using an imapsync-instance embedded in Mailcow.
However, calendar, contacts, notes etc. need to be migrated with other solutions.
It seems, people are leaving Kopano.
-
@meyca You maybe… Not me, im still very happy with kopano…
but i do get why people switch… -
Thanks for the input so far.
I was hoping there was some kind of method on the Kopano server itself to bulk export all mailboxes in one go, but that doesn’t seem to be the case.
Since it’s 85 mailboxes with around 200GB of mails to export, having to move everything manually doesn’t really sound promising too. I’m probably going to use some kind of IMAP migration tool as @meyca suggested. A colleague of mine has used Bittitan for another project.
I’m not sure yet as to how much the features like calendars and contacts have been used on the current Kopano server. That would be another problem to consider once I’ve moved all the emails over.
-
Hi there,
I successfully BULK exported mailboxes to PST with zarafa client 7.2.6-52189 and zarafa migration tool 7.1.11.46050. As far as I remember, I used Outlook 2013 (or 2016) and removed KOE first. I tried different versions of client and migration tool, the combination mentioned above worked. You need to create a .csv with the mailboxes, and voila :)
Kind Regards
KaBi -
@thctlo Can you “elaborate” a bit your opinion on why people switch off of Kopano?
Asking as I’m just in the phase of somehow “expanding” the Kopano system and migrating some more users to Kopano… Just to check if there are maybe some reasons/issues I did not considered so far…
Regards,
M.Culibrk -
@mculibk lots use the free version of Kopano, the “development” line.
me also, but not all of these are stable for production, everything is fine, untill you hit problem then.Dont get me wrong, i have not found anything else that is as good as kopano.
its only so quite lately on the forum and ah wait… … :-) i finaly see the new core packages…If you want to use kopano in production i really recommend to get a subscription.
i run a paid (at the office) and free version myself
I’m a zarafa/kopano user for over 12 years now and still a happy one.
Most sad part for me is, the lak of development in the distro’s themself but kopano is not small package. So is Kopano bad, no definilty not… its a great product if it wasnt, i would not have use it for 12 years now. Room for improvement,… like any product there is room for improvement. -
@thctlo Thanks for the info! That’s encouraging! ;)
I definitively agree on the subscription and “supported” packages.
And yes… room for improvement… ;)I’m really missing some more “centralized administration” especially related to MTA (postfix) stuff etc…
Thanks!
Regards,
MC -
@mculibk any example of what you “really” mis?
i for example use this.
If you use SQL , always create companies. you can use that field to add it automatlicy via mysql to postifx, meaning, when you add a company domain, its directly know in postfix.
(virtual_mailbox_domains = mysql:/etc/postfix/mysql/mysql-domains.cf)
this querie.
query = select value from objectproperty where propname=‘companyname’ and value=’%s’i never got the time to get into this one.
https://github.com/pietmacom/com-pietma-zarafa-postfixadmin
he did some nice things.And you can do offcourse simular in LDAP with what we did in SQL
-
@thctlo I’m using LDAP backend for managing users etc (UCS OpenLDAP or M$ ADS).
So, companies etc are “handled” centrally via LDAP. This is not “a big problem” even if it’s totally “separated” from Kopano.
I get that Kopano can use “any” MTA and that it’s “does not care about the MTA”… but… Kopano is also a “mail system” and MTA stuff actually very important in the whole picture, isn’t it?So… in “general” i totally miss the entire “MTA” part, incoming and outgoing SMTP “rules”, options, limits etc.
I know I can “handle” that with other tools… but then it’s much more difficult to have a “clear view” of the whole picture.For example… SMTP limits (sizes, rates…) for domains, users… possibility to see/check any queues etc And then the “security” part… basically you can somewhat use Fain2Ban to handle invalid logons etc… but, again, it’s a totally separate/standalone set of tools.
Basically… there is no “admin portal” at all (if we talk about GUI tools). Or a general “full collection” of admin CLI tools to handle “all” the things related to “mail” in a centralized/homogeneous manner (lot of different tools, different syntax, different rules…)
Regards
-
@thctlo Thanks for the zarafa-postfixadmin link! Did not find it before… ok… but i searched for postfix tools only (and found the “normal” postfixadmin)
-
@mculibk im a bit longer here… and sometimes my memory is working ;-)
on that ldap part and handle smtp, what your looking for, thats not really a kopano thing.
Thats more postfix itself.This is one example you can extend.
https://github.com/benningm/mtpolicyd/blob/master/examples/ldap/README.md -
@thctlo Yes… i know “that’s a postfix thing”… but I’m somehow looking at Kopano as a “complete” mail/groupware solution… and so a part of it is somehow “missing” (in my opinion).
And yes… I know… it’s open so I can actually help and make some additions to better suite my needs (and maybe others). I probably will - for example “fix” the AD extension to handle some more attributes related to MTA part etc.
And, again, thanks for the provided link! It’s definitely already usable… and as such extendable so yes! Great!
THANKS!!
(PS. I’m currently using mainly CommunigatePro which has its own (big) bucket of issues but it has a really nice “centralized” approach with lot of knobs and levers in one place, so you can manage all things mail/groupware related much easier than jumping between different programs and their different configuration options)
Best regards,
M.Culibrk -
@externa1 said in Kopano mailbox export:
@gerald
But with outllook 2010 you’re unable to connect to o365Just use Outlook 2010 (only connected to Kopano) to export to a PST file…
and then open or import the PST on a newer version of outlook connected to Office 365… -
@mculibk said in Kopano mailbox export:
Asking as I’m just in the phase of somehow “expanding” the Kopano system and migrating some more users to Kopano… Just to check if there are maybe some reasons/issues I did not considered so far…
If your users are happy with WebApp, everything is great.
Main reason I’ve had to stop using Kopano is that the Outlook ActiveSync integration is just not reliable enough and exhibits weird errors - especially bad if your mailboxes are big (>10GB) because then the resync takes forever. I’ve had people lose changes because Outlook/ActiveSync had stopped syncing and then after a force-resync changes had been lost.Also it seems like development has stopped? For commercial users there have been only minor point releases for close to three years! The puclic kopano-core still seems to see some development, but I don’t really think the company leadership has any idea where they want to end up.
-
@gerald said in Kopano mailbox export:
but I don’t really think the company leadership has any idea where they want to end up.
What bugs me, is that nearly all Kopano services (excluding Z-Push) depend on proprietary built packages and build processes for binaries and packages not being described very well.
In my eyes, this doesn’t fit the companies “digitally sovereign” claim. And this finally leads to: they do not know “where they want to end up”.
-
@gerald Thanks for the better “under the hood” info!
Indeed… I have quite some users with very large mailboxes (>30-40GB) and they insist on using Outlook…So… this info if rather “discouraging”… I’m using Kopano for a few smaller environments with smaller mailboxes and everything seems quite nice/working without issues.
Maybe I will convince them to use DeskApp instead of Outlook… but I doubt I’ll be very successful with that…What is the last version of Outlook/Office where the old Zarafa MAPI client still works? Any experience?
I did not try it because it’s being “obsoleted” and officially supported any more…
If I understood your messages… it’s still possible to use the Zarafa connector by upgrading the Outlook2010 installation? Is that right? It still works with Outlook2013 or 2016?
Any “longer term” experience with that? I know I’ll get no support from Kopano for that… but maybe it could be a “workaround/soft transition” to DeskApp… (I’d really like to ditch Outlook but users won’t let it go…)Thanks!
Regards,
MC
