UCF uses a third-party SMTP relay service for sending both transactional and marketing emails.
Transactional email is an email that is sent to an individual or small recipient groups. Examples of transactional email include: NID password resets, enterprise remote & heartbeat monitoring, notification emails, feedback, service-now tickets, ePAF forms, LEAP requests etc.
Marketing email is an email that is sent to multiple recipients. Examples of marketing emails include: email newsletters, promotional email campaigns, student grades, outage communication etc.
Instructions for using this are provided below.
UCF's SMTP relay service can be accessed using authenticated account credentials for either Transactional (1:1) or Marketing (1:MANY) outgoing email.
Before you can start using the SMTP Relay, you need to do the following:
To configure your application to send email through UCF's SMTP service, use the settings below.
USERNAME
is going to always be "apikey"
while the password is the value of the API key generated.)
Here’s an example of configuring WordPress to use SendGrid:
Alternatively UCF's SMTP relay server supports the use of API Keys. API Keys allow you to use another method of authentication separate from your account username and password. To use keys, you must set a plain text header named “Authorization” with the contents of the header being “Bearer XXX” where XXX is your API Secret Key.
Before you can start using the API, you need to do the following:
Your API call must have the following components:
https://api.sendgrid.com/v3/
GET https://api.sendgrid.com/v3/resource HTTP/1.1
Authorization: Bearer Your.API.Key-HERE
curl -X "GET" "https://api.sendgrid.com/v3/templates" -H "Authorization: Bearer Your.API.Key-HERE" -H "Content-Type: application/json"
------------------------------
curl --request POST \
--url https://api.sendgrid.com/v3/mail/send \
--header 'Authorization: Bearer <<YOUR_API_KEY>>' \
--header 'Content-Type: application/json' \
--data '{"personalizations":[{"to":[{"email":"john.doe@example.com","name":"John Doe"}],"subject":"Hello, World!"}],"content": [{"type": "text/plain", "value": "Heya!"}],"from":{"email":"sam.smith@example.com","name":"Sam Smith"},"reply_to":{"email":"sam.smith@example.com","name":"Sam Smith"}}'\
-----------------------------
All responses are returned in JSON format. We specify this by sending the Content-Type
header. The Web API v3 provides a selection of response codes, content-type headers, and pagination options to help you interpret the responses to your API requests.
You may need to install Telnet on your machine. Telnet comes natively on some operating systems; However, recent releases of MacOS no longer include Telnet, and Telnet must be enabled manually on Windows 10 and Windows 11.
To enable Telnet on Windows 10, navigate to Windows Features > Turn Windows Features on or off from the Windows Control Panel. Check the box next to Telnet Client, and select OK.
Before you can start using the SMTP Relay, you need to do the following:
TELNET smtp.sendgrid.net 25
SendGrid accepts unencrypted and TLS connections on ports 25, 587, & 2525. You can also connect via SSL on port 465. Many hosting providers and ISPs block port 25 as a default practice. If your Telent session continually times out or will not connect using port 25, it is likely that your ISP or hosting provider is blocking the port. You can contact your host/ISP to find out which ports are open for outgoing SMTP relay. We recommend using port 587 to avoid any rate limiting that your server host may apply.
AUTH LOGIN
The mail server will respond with 334 VXNlcm5hbWU6
, which is a Base64 encoded request for your username.
YXBpa2V5
and press Enter on your keyboard. Twilio SendGrid requires you to authenticate using an API key. When using Basic Authentication and an API key, you must use the string apikey
in place of your account username. The string apikey
is YXBpa2V5
when Base64 encoded, which is why we use it in this step.The mail server will respond with 334 UGFzc3dvcmQ6
. This response is a Base64 encoded request for your password (your API Key).
The mail server will respond with 235 Authentication successful
. Getting this far indicates that your connection to smtp.sendgrid.net
over the chosen port is open and that your API key is valid.
MAIL FROM: <SENDER_EMAIL>
The mail server will respond with 250 Sender address accepted
.
RCPT TO: <RECIPIENT_ADDRESS>
Note that you can add more RCPT TO addresses during this step. Repeat the process by adding another RCPT TO command and pressing Enter for each recipient you intend to deliver the message to.
The mail server will respond with 250 Recipient address accepted
after each recipient is added.
DATA
and press Enter.The mail server will respond with 354 Continue
. Unlike the MAIL FROM and RCPT TO commands, which are part of the email envelope, the DATA command is not meant to contain information that routes your email from a sender to a recipient. Instead, DATA allows you to modify the content of your message.
To: "<RecipientName>" <<RecipientEmailAddress>>
From: "<SenderName>" <<SenderEmail>>
Subject: <EMAIL_SUBJECT>
"<MESSAGE>"
For example:
“This is a test for the SMTP relay."
.
, and then pressing Enter.The mail server will return 250 Ok: queued as <examplestring1234>
. This means the email has been queued to send. The queue moves very quickly, and you should see mail delivered to the designated recipients shortly.
quit
and pressing Enter.The full command should look like the following example.
235 Authentication successful
MAIL FROM:tiramisu@example.com
250 Sender address accepted
RCPT TO:person1@sendgrid.com
250 Recipient address accepted
DATA
354 Continue
From: "Tira Misu" <tiramisu@example.com>
To: "Person 1" <person1@sendgrid.com>
Subject: Test message subject
"This is the test message body."
.
250 Ok: queued as Yo60h6C5ScGPeP5fUWU3K
The University provides a legacy method to relay outgoing email. This service (ucfsmtp.mail.ucf.edu) is used in the case where a server, device or application needs to send email but is unable to authenticate.
This service is used by:
Use these parameters:
Server name: ucfsmtp.mail.ucf.edu
Port: 25
Connection security: none
Authentication method: No authentication required
Server name: ucfsmtp1.mail.ucf.edu
Port: 465 for SSL-encrypted email
Connection security: none
Authentication method: No authentication required