Email Infrastructure: Phase 2

Overview of Phase 2

  • Target restricted network and multi function devices for transition to Google SMTP
  • Turn on SPF in advisory mode
  • Turn on DKIM for messages originating from 3rd-party mailers

Targeted Services & Devices

Use the information provided below to help you decide how best to configure your server, application, or other email sending agent to send email on behalf of NC State university.

As always, feel free to consult with the Google Service Team for guidance or assistance with configuring your sending agent.

 

For a more visual approach to the information below:

Server Email Sending Decision Tree

 

Device on Non-NAT'd Private IP

Includes multifunction printers/devices as well as servers that can’t talk to the public internet without using proxy

  • Use OIT’s smtp-tunnel.oit.ncsu.edu along with a Google Generic Account to send emails via Google
  • Device must be able to do Authenticated SMTP
  • Limited to sending less than 10,000 messages per day
  • See Emailing via Google using smtp-tunnel.oit.ncsu.edu

Device on Public IP or NAT'd Private IP
  • Connect directly to Google and leverage a Generic Account to send emails
  • Device must be able to do Authenticated SMTP
  • Limited to sending less than 10,000 messages per day
  • See Google SMTP Settings for options for sending via Google

Sending > 10,000 messages per day
  • For large volume transactional sending, OIT has outsourced SMTP sending to SendGrid via a combined volume purchase option
  • Sending can be done via SMTP or via HTTP API calls depending on sending agent
  • Contact the Google Service Team for information on pricing and access

Device cannot use Authenticated SMTP