|
|
Project Overview
Over a decade ago, IT-supported Sun mail (MX) servers and their email inboxes that were had been hosted on-premises were migrated to Gmail.
After that migration, some hardware in the mail pipeline remained for security and mail routing reasons.
Google has since improved Gmail's security features (previously known as Postini), so we no longer require the use of on-promises email security appliances (ESAs) .is no longer required.
By eliminating SMTP routing to on-premises hardware (load-balancer and ESAs), we will increase our email delivery's resiliency during events, such as PSPS, which could cause LBL data center power outages.
Current Incoming SMTP configuration
Current Outgoing SMTP configuration
Former SMTP routing configuration
Previous to 7/11/20, emails sent to lbl.gov, along with a number of other domains, recipients routed to As shown below, current SMTP traffic to lbl.gov (and some other domains) recipients routes to mailgate.lbl.gov ( an on-premises load-balancerbalancer (mailgate.lbl.gov) before arriving at the ESAs to be checked for spam, viruses and Cisco ESAs/Ironports (fe3.lbl.gov or fe4.lbl.gov), which drop connections from mail servers with poor reputations before being further routed and check remaining messages for spam, viruses before routing messages to their final destination at Gmail or to LBNL Certified Mail Servers (aka Email Repositories).
Existing (soon-to-be-former) SMTP routing configuration
By eliminating the routing of email to these on-premises load-balancer and appliances, we gain the added benefit of increasing email resiliency during events such as PSPS.
New SMTP routing configurations
More details for Email Repository owners Actions required by Email Repository owners