Oracle Cloud Infrastructure Documentation

Getting Started with Email Delivery

Email Delivery provides a highly scalable, cost effective, and reliable way to send email from your applications. Email Delivery includes developer-friendly tools to quickly send application-generated email for mission-critical communications such as receipts, programmatic notifications, or password reset emails.

Email Delivery Basics

This diagram shows the architectural flow of the Email Delivery service.

When you use Email Delivery, we become your outbound email server. If you have an existing email server, you can keep it and configure it to send through Email Delivery. The Email Delivery service will take care of the feedback loops and platform reputation automatically.

Getting Started

This topic gives guidance on how to get started with Email Delivery. For complete details about the service and its components, see Overview of the Email Delivery Service.

Email Configuration Options

You can configure Oracle Cloud Infrastructure using the Console (a browser-based interface), REST API, SDKs, CLI or Terraform.

The following information describes how you can configure third-party applications to send email through Email Delivery:

Sending Email

To begin sending email with Email Delivery, complete the following steps:

Generate SMTP credentials for a user.
Set up permissions.
Create an approved sender.
Configure SPF on the approved sender domain.
Configure the SMTP connection.
Begin sending email.

Using the API

You can access Oracle Cloud Infrastructure using the REST API. Instructions for the API are included in topics throughout this guide. For a list of available SDKs, see SDKs and Other Tools.

Regions

See Regions and Availability Domains for information on regions Email Delivery is available in.

Limits

See Email Delivery Service Capabilities and Limits for information on new account and enterprise account limits.

Best Practices

This section describes best practices for using Email Delivery.

Volume Testing - In order to maintain our sender reputation and yours, testing at volume needs to be done using the following best practice.

  • Use a recipient address at the email-blackhole.com domain, such as example@email-blackhole.com. Email Delivery will accept the mail but will not deliver it to an inbox.
  • If large volume emails are sent to valid email addresses, these will get rejected by receivers and will result in a large amount of hard bounces. This will negatively affect IP reputation. For testing bounce processing, send small amounts of emails to a domain that does not have an MX record, in other words, the domain does not exist.

Deliverability - To help you learn and manage the habits that affect your sending reputation, see Deliverability Best Practices.

Sending to Email Aliases - When sending email to an alias, the alias is considered one recipient. When sending email to a distribution group or list set up in an email client such as Apple Mail or Outlook, a separate email is sent for each recipient in the group.