IT Development/Email Migration: Difference between revisions
(start) |
(→Migration scheme: add) |
||
| Line 16: | Line 16: | ||
==Migration scheme== | ==Migration scheme== | ||
* Install Qmail/Courier/Mailman onto Services & perform basic configuration | |||
* For each domain: | |||
** Copy configuration settings & data for the above using rsync | |||
** Test delivery to new server | |||
** Add a new MX record pointing to the new server | |||
** Remove the old MX record (24 hours later) | |||
* Once all domains are migrated: | |||
** Perform a final sync on mail from old server, to ensure everything is captured | |||
I plan for this to take around 4-5 days work over the Christmas period, it may take a little longer if problems occur. Because of the monolithic nature of the email/mailing list setup (unavoidable) it has to all go at once (per domain) meaning a lot of potential risk points - however by migrating, testing *then* failing over I believe we can remove any possibility of down-time or data loss. | |||
I plan to start with the Wikiconferences domain/email before moving onto the others. | |||
===Notification== | |||
I plan to notify everyone affected at least 48 hours before their domain is changed - they may need to update some settings to continue to receive email (i.e. via imap or pop3) or view webmail. I also plan to make public announcements to the mailing lists warning of the migrations in plenty of time. Please let me know what other notifications are needed. | |||
Revision as of 12:16, 18 December 2012
This page will document the process for migrating email and mailing list services for WMUK to the new server infrastructure.
Mail servers work as follows; an SMTP server acts as the core Mail Transfer Agent (MTA) receiving and sending mail for users. This mail is then stored on disk, either in Maildir or Mbox format. A second server will provide POP3 & IMAP (i.e. mailbox) access to users by reading those delivered files.
In practice migrating the archives is relatively simple, however locating all the configuration settings and mail and ensuring it is adequately migrated will take a little time.
Current setup
Software:
- Qmail (SMTP)
- Courier (POP3 & IMAP)
- SpamAssassin (anti-spam)
- Mailman (mailing list)
Mail is stored in Maildir format & accounts are configured using Plesk Panel.
Migration scheme
- Install Qmail/Courier/Mailman onto Services & perform basic configuration
- For each domain:
- Copy configuration settings & data for the above using rsync
- Test delivery to new server
- Add a new MX record pointing to the new server
- Remove the old MX record (24 hours later)
- Once all domains are migrated:
- Perform a final sync on mail from old server, to ensure everything is captured
I plan for this to take around 4-5 days work over the Christmas period, it may take a little longer if problems occur. Because of the monolithic nature of the email/mailing list setup (unavoidable) it has to all go at once (per domain) meaning a lot of potential risk points - however by migrating, testing *then* failing over I believe we can remove any possibility of down-time or data loss.
I plan to start with the Wikiconferences domain/email before moving onto the others.
=Notification
I plan to notify everyone affected at least 48 hours before their domain is changed - they may need to update some settings to continue to receive email (i.e. via imap or pop3) or view webmail. I also plan to make public announcements to the mailing lists warning of the migrations in plenty of time. Please let me know what other notifications are needed.