Email Infrastructure

OIT is making changes to our email infrastructure to better serve NC State. These changes will require action on the part of many IT staff on campus.

Beginning in 2016 and continuing until completed, OIT is making changes to its email infrastructure to better serve our campus. These changes include:

  • Implement SPF and DKIM protocols
  • Phase out the use of the smtp.ncsu.edu mail relay
  • Require people, machines, and devices to begin using Google SMTP services

UPDATE 12/4/2017: Due to some changes in Google’s mail options for very large mail senders, we have unlinked the flow chart and matrix of options while we review these changes and the impact to our email infrastructure. Please continue to send questions regarding your setup to help@ncsu.edu. 

To better understand the changes occurring, the Google Service Team (GST) has prepared a flowchart and a comparable matrix of options that help explain these recommended changes.

These changes will provide significant protection to our users from phishing, while also improving our global mail reputation.

Learn more about why these changes are necessary

Project Phases

Each phase will require campus IT staff to make changes to targeted services and devices.

Phase 1 (Begins July 2017)

Action by campus IT staff is required for:

Web Apps

Web apps includes content management systems like WordPress or Drupal, and custom apps powered by PHP, ColdFusion, or other web based languages.

Web Servers

Web servers are computers that are primarily for the purpose of delivery apps and content via the web. If these computers generate email, they must send via Google SMTP.

Cloud Services

Cloud Services are hosted applications or services that’s primary function is NOT the sending of email (bulk mailers) but may send email as the course of normal operation. Examples include Eventbrite & Terra Dotta.

What's happening in Phase 1?
  • Target web-based use cases for transition to Google SMTP
  • Convert tx.ncsu.edu from an implicit to an explicit alias
  • Begin process of eliminating unity.ncsu.edu implicit aliases
  • Turn on DKIM for messages originating from Gmail
Learn more

 

Phase 2

Action by campus IT staff is required for:

Multi-Function Devices

Restricted networks, private IPs

What's happening in Phase 2?
  • Target restricted network and multi function devices for transition to Google SMTP
  • Convert eos.ncsu.edu from an implicit to an explicit alias
  • Turn on SPF in advisory mode
  • Turn on DKIM for messages originating from 3rd-party mailers
  • Turn on DMARC in advisory mode

 

Phase 3

Action by campus IT staff is required for:

3rd Party Bulk Mailers

Desktop Clients / Servers

What's happening in Phase 3?
  • Target 3rd Party Bulk Mailers and remaining computers for transition to Google SMTP
  • Finish eliminating unity.ncsu.edu implicit aliases
  • Turn on SPF in strict mode
  • Configure email infrastructure to meet ARC specifications
  • Launch campus Limited Functionality Relay for devices that cannot OAuth