which imap server uses kopano

kopano-gateway is the IMAP server. Mails are normally stored by kopano-server, usually in MySQL, though may internally get copied to /var/lib/kopano/attachments for faster output to IMAP clients.

pixel

Hmm, that means I have no option to transfer imap-accounts from kolab to kopano by using a tool like imapsync e.g. ?

imapsync should work. In fact, the utility “kopano-migration-imap” is based on it.

pixel

@jengelh said in which imap server uses kopano:

kopano-migration-imap

What is “kopano-migration-imap” and where can I get it?

fbartels

@pixel please have a look at https://wiki.z-hub.io/display/K4U/Migrating+to+Kopano+installed+on+Univention

pixel

I have a final question. It is possible to use the tool to migrate the mails (imap) over the lan connection? Example:

My old mails in kolab on host: kolab.local.lan
My new kopano ist on host: saturn.local.lan

I install a new vm (ucs member) host: transfer.local.lan an install the package “kopano-migration-imap” on this host, transfer the mails and kill the vm.

externa1

@pixel

Hi you don’t need a third machine you may install “kopano-migration-imap” on host: saturn.local.lan and tranfer through lan from kolab.local.lan

rg
Christian

pixel

*The package kopano-migration-imap required some dependencies that are not part of the official Univention repositories, but are available from the “unmaintained” *
…
it is possible to remove everything clean from the system when I finished?

fbartels

@pixel said in which imap server uses kopano:

it is possible to remove everything clean from the system when I finished?

that would be a more fitting question for the Univention forum.

pixel

@fbartels said in which imap server uses kopano:

that would be a more fitting question for the Univention forum.

OK I will do it. Back to my question before … it is possible to transfer with a third machine? A vm with ucs a member are ready in 15 min and after the migration I send her to nirvana :-)

fbartels

@pixel said in which imap server uses kopano:

it is possible to transfer with a third machine

yes, absolutely.

pixel

ok, vm ist up and running … the save way :-)

pixel

ok, i set the variable:

ucr set repository/online/unmaintained=yes

and:

apt update

but I can find a package:

root@ucstest:~# apt search kopano
Sortierung... Fertig
Volltextsuche... Fertig

or:

WebUI -> Packache -> search -> kopano

What’S wrong?

pixel

ok, I have to install kopano-core on the test environment before I try tu install the migration-tool . My mistake

pixel

Ok, i try to start the migration from an kolab server with:

kopano-migration-imap --noauthmd5 --host1 192.168.1.72 --user1 'user1@domain.de' --password1 '#geheim' -sep2 / --prefix2 "" --host2 192.168.1.6 --user2 user1.ganz --password2 '#geheim'

but I become:

Transfer started at Tue Sep  5 10:16:17 2017
PID is 20593
Log file is LOG_kopano-migration-imap/2017_09_05_10_16_17_user1.ganz.txt ( to change it, use --logfile path ; or use --nolog to turn off logging )
$RCSfile: kopano-migration-imap,v $ $Revision: 1.727 $ $Date: 2016/08/19 10:30:36 $ Command line used:
/usr/bin/kopano-migration-imap --noauthmd5 --host1 192.168.1.72 --user1 user1.ganz@domain.de --password1 MASKED -sep2 / --prefix2  --host2 192.168.1.6 --user2 user1.ganz --password2 MASKED
Temp directory is /tmp  ( to change it use --tmpdir dirpath )
PID file is /tmp/kopano-migration-imap.pid ( to change it use --pidfile filepath ; to avoid it use --pidfile "" )
Wrinting my PID 20593 in /tmp/kopano-migration-imap.pid
Modules version list:
Mail::IMAPClient     3.35
IO::Socket           1.38
IO::Socket::INET     1.35
IO::Socket::INET6    2.72
IO::Socket::SSL      2.002
Net::SSLeay          1.65
Compress::Zlib       2.064
Digest::MD5          2.53
Digest::HMAC_MD5     1.01
Digest::HMAC_SHA1    1.03
Term::ReadKey        2.32
File::Spec           3.48_01
Time::HiRes          1.9726
Unicode::String      2.09
IO::Tee              0.64
File::Copy::Recursive 0.38
Authen::NTLM         ?
URI::Escape          3.31
Data::Uniqid         ?
JSON                 ?
JSON::WebToken       ?
Crypt::OpenSSL::RSA  0.28
LWP                  6.08
HTML::Entities       3.69
Getopt::Long         2.42
Test::MockObject     ?
( use --no-modulesversion to turn off printing this Perl modules list )
Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
Host1: will try to use LOGIN authentication on host1
Host2: will try to use LOGIN authentication on host2
Host1: imap connexion timeout is 120 seconds
Host2: imap connexion timeout is 120 seconds
Host1: IMAP server [192.168.1.72] port [143] user [user1.ganz@domain.de]
Host2: IMAP server [192.168.1.6] port [143] user [user1.ganz]
Host1: connecting and login on host1 [192.168.1.72] port [143] with user [user1.ganz@domain.de]
Host1 banner: * OK [CAPABILITY IMAP4rev1 LITERAL+ ID ENABLE STARTTLS LOGINDISABLED] kolab.local.lan Cyrus IMAP git2.5+0-Kolab-2.5-108.3.el6.kolab_3.4 server ready
Host1: 192.168.1.72 says it has NO CAPABILITY for AUTHENTICATE LOGIN
Host1 failure: Error login on [192.168.1.72] with user [user1.ganz@domain.de] auth [LOGIN]: 2 NO Login only available under a layer

any experience with kolab?

fbartels

Hi @pixel ,

what you installed is merely a packages imapsync. so you should be able to follow examples given for imapsync, for example https://wiki.kolab.org/Imapsync

pixel

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'