Migrating Email Repositories (aka Certified Email Servers)

To replicate the SMTP routing functionality that fe3.lbl.gov and fe4.lbl.gov provide for Email repositories, the DNS contacts of repositories and/or domain owners with MX records to mailgate.lbl.gov need to take steps in order to ensure SMTP traffic for their domain(s) continues to route to their repositories once MX records change to use Google's MX servers: https://support.google.com/a/answer/174125

Domain Owner actions:

1. Confirm that your domain(s) has active recipients that should still be receiving email
2. Verify the Email repository (IP address or hostname) that your domain's SMTP traffic routes to is accurate

Email Repository Owner actions:

1. Verify that the domain(s) which route email to them are still in-use so that we do not unnecessarily migrate the domain(s) to Google
2. Confirm that the Email repository (host name or IP address) for each domain is accurate
3. Make sure that any host, and other, firewall rules allow SMTP directly from Gmail's IP addresses instead of just the ESAs (fe3.lbl.gov and fe4.lbl.gov)
   • The border firewall will be opened to allow port 25 (SMTP) from Gmail's IP addresses to all confirmed Email repository IP addresses

Once the above actions are confirmed, the Email team will:

1. Configure routes at Google from each in-use domain to its corresponding, confirmed Email repository IP address
2. Change MX records for Email repositories from mailgate.lbl.gov to Gmail's MX records: https://support.google.com/a/answer/174125