James Cort skrev, on 16-05-2007 15:00:

> I'm looking to migrate an existing courier-imap installation from one 
> server to another.  My concern is that if I get something wrong, it may 
> not be apparent until rather late in the process and there's a risk of 
> data loss.  I can't seem to find anything in Google which suggests I 
> might hit a problem, however I'd like to get a second opinion from the 
> list before I go charging in.
> 
> Current scenario:
> 
> 1 x Gentoo server.
> 
> Emails are received through sendmail, processed through procmail and 
> picked up by users using courier-imap.  The mail storage is in maildirs 
> - some 60GB of them - all rooted in /home/<USERNAME>/.maildir.
> 
> Desired scenario:
> 
> 1 x Debian Etch server
> 
> I'm not sure what I'll end up using as the MTA (but it must support 
> Sendmail-style aliases files, and I've got Postfix in a number of places 
> so that's a strong possibility), processed through procmail and picked 
> up using courier-imap.  Maildirs will remain housed in 
> /home/<USERNAME>/.maildir
> 
> There will be no hardware similarities between the two servers, and very 
> few configuration similarities.  They will have different hostnames, IP 
> addresses.  My plan is to shutdown courier-imap and rsync -a the 
> maildirs from the source to the destination server. 
> 
> Once complete, I'll CNAME the old IMAP hostname to the new one, users 
> will connect to the new IMAP server.  With any luck, I'm hoping that the 
> end result will be a transparent migration.
> 
> Have I got the right idea?

It looks basically what I have to do this summer, though switching to 
Red Hat 5 from RHAS4 and from 3-year old IBM hardware to new. That's how 
I'll be doing things; people won't have access to their mail for a day 
or so during school vacation.

I've other production machines running CentOS 5 and Fedora FC6, so I've 
enough experience with them.

In the mean time I've updated Courier maildrop and IMAP several times to 
the latest authlib, maildrop and IMAP, Postfix to 2.4 and the OpenLDAP 
delta syncrepl backend to 2.3.35; the site has both DLT and rsync 
disk-based backup methods for the IMAP mail hierarchy (the latter for 
people who suddenly find they've deleted something they didn't mean to 
and want it back immediately).

However, we use a dedicated machine for mail, with virtual mail accounts 
owned by a single user, in a single hierarchy  - which is possible with 
maildrop but not with procmail. Users have no shell access to the mail 
server, their $HOME data directories are om different servers for 
different services.

One thing though, using a CNAME for an MTA with MX records is generally 
deprecated though I can't find any rfc that forbids it; it can lead to 
nasty things happening (think of reverse PTR records), google for '"mx 
record" cname' if in doubt.

Good luck (to both of us :)),

--Tonni

-- 
Tony Earnshaw
Email: tonni at hetnet dot nl

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap

Reply via email to