Migrating Linux/cyrrus IMAP into Lion server dovecot

emailimapserver.app

We changing our internal infrastructure and replacing old Linux server with an OS X Lion server. One crucial thing is email – need migrate it without interruption.
Currently we have Linux/Cyrrus, with zilion of stored emails for tens of local users.

Here: How setup Mail.app IMAP to migrate Mail Server is recommennded doing it via local mail client, what is ok for external imap-server for one user, but not practical for the full server-migrate.

What is the recommended way migrate the whole mail-handling from Linux cyrrus/postfix into OS X Lion dovecot? Know anyone some scripts (preferable perl) what can help with the migrating?

My current idea:

setup DNS, Users, and email handling on the Lion server
stop the mailserver on the Linux
migrate all emails (with some script)
change MX record from Linux to Lion
start using Lion

Any guides, caveats and/or any helpful comments?

Best Answer

There's a Cyrus2Dovecot migration tool developed by Freie Universität Berlin.

Cyrus2Dovecot is a full-featured command line tool for converting the e-mails of one or more users from Cyrus format to Dovecot Maildir++ folders. It allows for performing a server transition which is fully transparent to both POP and IMAP users.

And other migration solutions in the Dovecot wiki.

Related Solutions

MacOS – Access Lion SMB shares from Linux

Samba no more, for Lion Server mount.cifs needs extra options, "nounix,sec=ntlmssp"

  [root@50centos ~]# 
  [root@50centos ~]# yum install samba-client samba-common cifs-utils
 ...
  [root@50centos ~]# mkdir /mnt/lion_smb
  [root@50centos ~]# mount -t cifs -o MikeCochran,trustno1,nounix,sec=ntlmssp //198.252.206.140/smb_share /mnt/lion_smb/

          =^..^=       `·.¸¸ ><((((º>.·´¯`·><((((º>   

MikeCochran@stack:~$ 
MikeCochran@stack:~$ sudo apt-get install cifs-utils
  ...
MikeCochran@stack:~$ mkdir /mnt/lion_smb
MikeCochran@stack:~$ mount.cifs //198.252.206.140/smb_share /mnt/lion_smb/ -o user=MikeCochran,password=trustno1,nounix,sec=ntlmssp
MikeCochran@stack:~$ 
MikeCochran@stack:~$ mkdir /mnt/lion_smb_dup
MikeCochran@stack:~$ mount -t cifs //198.252.206.140/smb_share /mnt/lion_smb-dup -o username=MikeCochran,password=trustno1,nounix,sec=ntlmssp

apologies for the delay!!

Internal IMAP server – Lion behind firewall

This is a very common setup. In general, never use .private and .local since you end up (eventually) in a world of hurt and doing it "right" isn't that hard.

Basically, you will tell the world that your mail server resides on the public IP address (or set up it's own real routable internet IP address and have the Proxy/Firewall forward traffic to the internal fixed IP 10.1.1.20)

Then, you will add two zones to your internal DNS so that all queries for mail.whatever.com resolve to 10.1.1.20 and a reverse zone resolves the IP to the name.

This way your clients will get the right address when on the local LAN or VPN in, but can still access the server from the public internet when DNS gives the public address.

Also look out for your server certificates. Most people issue certificates for the public IP address and have a profile to allow internal clients to trust a self-signed cert for when they hit the server locally.

There are no silver bullets here - the choice you make to have a more complicated routing will complicate your SSL and other server setup steps, but this is a common situation for people deploying lion server so I've seen it work well in most cases.

Best Answer

Related Solutions

MacOS – Access Lion SMB shares from Linux

Internal IMAP server – Lion behind firewall

Related Question