Note: These are old notes about a previous migration. They might be useful to somebody.

Tasks to be Completed

Phase 1: Basic local mail on cube [DONE!]

  1. Create bug #2451 and wiki pages. [DONE]
  2. Set up a trivial postfix instance on [Already installed previously - DONE]
  3. Test that cube postfix can receive and route email to local accounts, and from local accounts out (mutt). [DONE]
    • cube seems to have a global alias to forward email to pyramid already in place...
      • /etc/mailname was wrong. [FIXED]
  4. Set up forwards from cube to pyramid. [DONE]
    • Done, did these things:
      1. Appended /etc/aliases@pyr into /etc/aliases@cube
      2. Copied all home directories on pyr to a line like "username: username@…" in /etc/aliases@cube
    • Still need to make mail to twisted-bugs list from trac user work [DONE]
      1. Added twisted-bugs@… alias to /etc/aliases@cube. This was necessary because those emails originate on cube, and cube thinks it's handling
  5. Test that email sent to a local account on cube gets forwarded to an appropriate local account on pyramid. [DONE]
  6. Notify twisted-admin list about bug, wiki pages, and status. [DONE]

Phase 2: Prepare for Mailman migration

  1. Through mailman, set up a fake mailing list on pyramid
  2. Copy the necessary aliases as forwards on cube
  3. Send an email to the list address (which is pyramid -- MX hasn't changed yet)
  4. Send an email to the list address to test postfix forwards to pyramid
  5. Compare the source of the two emails. Email should be received with the same headers, except the SMTP server hostname.
  6. Install mailman on cube, copying config from pyramid (but not data).
    • Currently blocked--installation requires libapr0, which conflicts with custom subversion deb installed.
  7. Test mailman on cube:
    1. Temporarily disable the cube->pyramid forwards for mailman aliases
    2. Connect directly to SMTP on cube and send an email formatted as if cube is
    3. Verify that mailman sends the email to the list users correctly
  8. Clean up mailman test data on cube.
  9. Restore the cube->pyramid mailman aliases.
  10. Notify the admins list of status.

Phase 3: POP and IMAP mail

  1. Install necessary POP and IMAP services on cube.
  2. Remove the forward on my account and test IMAP and POP access to cube, including authentication methods currently supported [list here..]
  3. Status update to admin list - at this point we are not committed to anything

Phase 4: Live on cube with Aliases

  1. Change MX record to point to cube.
  2. (Wait for MX TTL to expire?)
  3. For each local account on
    1. copy entire /home/account to cube
    2. disable the forward to pyramid, for that account.
    3. send that account an email, letting them know that their email is now being stored on cube, and they should archive or otherwise disregard any email files they have on pyramid.
    4. On pyramid, set up a pyramid->cube alias (the reverse direction) for that account, to respect DNS lag.
  4. Migrate mailman data to cube with rsync. Turn off cube->pyramid aliases for mailman.
  5. On pyramid, set up a pyramid->cube alias (the reverse direction) for mailman aliases.
  6. Notify twisted-admin list about status.


  1. (Optional) Adapt some kind of simple spam-filtering ruleset to postfix and apply it.
Last modified 8 years ago Last modified on 05/27/2013 07:58:24 PM