Troubleshoot Notification Email Configuration
Follow these recommendations to correctly configure and use the default from address and suppression list. These recommendations help you to avoid notification email delivery issues.
Note:
You can use the notification email metrics on the Monitoring page to monitor email throughput and delivery health, including successful, failed, and suppressed email events. See troubleshoot-oracle-cloud-infrastructure-email-configuration.html and troubleshoot-oracle-cloud-infrastructure-email-configuration.html.Default From Address
For Oracle Integration:
- Don't use
no-reply@oracle.comas thefromaddress. - Don't use the
oracledomain. - Change the default
fromaddress fromno-reply@oracle.comtono-reply@mail.integration.region.ocp.oraclecloud.com.The
regionattribute is provided by Oracle Integration. - Change the
fromaddress in your integrations fromno-reply@oracle.comtono-reply@mail.integration.region.ocp.oraclecloud.com.The
regionattribute is provided by Oracle Integration.
Note:
Theno-reply@mail.integration.<region>.ocp.oraclecloud.com address is for Oracle Integration only. Don't use this address as the from address for Process Automation notifications. Process Automation uses a separate default from address. Using the Oracle Integration from address for Process Automation may result in email delivery issues.
For Process Automation:
If you don't configure a from address on the Process Automation Notification page, Process Automation automatically uses noreply@process.<region>.oraclecloud.com as the default approved sender. For example, if your region is Ashburn, the default address is: noreply@process.us-ashburn-1.oraclecloud.com.
- Open the navigation menu in Workspace, expand Administration, and select Notification.
- Click Approved Sender.
- In the Register Approved Sender pane, enter the email address in the From Recipient field. The registered address is used as the default sender for Process Automation email notifications.
- Click Register.
You can't use certain reserved domains, such as @oracle.com, @gmail.com, @hotmail.com, and @yahoo.com, as approved senders. To learn more, see Managing Approved Senders in Oracle Cloud Infrastructure documentation.
If you use your own from address, configure Sender Policy Framework (SPF) and DomainKeys Identified Mail (DKIM) on the sender domain. To configure DKIM for Process Automation, submit a service request (SR) on My Oracle Support. Incorrect SPF or DKIM configuration on the sender's domain server (DNS) can result in email delivery failures and may cause email addresses to be added to the suppression list.
Suppression List
- Add
Toaddresses to the suppression list for a number of reasons:- As of now, the
recipientaddress when a hard bounce occurs (emails go undelivered for permanent reasons), when a soft bounce occurs (emails go undelivered for temporary reasons), and when a large number of emails are received are some of the reasons to add theToaddress to the suppression list.
- As of now, the
- If DomainKeys Identified Mail (DKIM) and Sender Policy Framework
(SPF) are not configured for the
fromaddress domain, the likelihood of having a bounce or messages being silently dropped by the receiving infrastructure is higher. - You can remove email addresses from the suppression list. See Remove Email Addresses from the Suppression List.
Invalid Email Addresses in Distribution Lists (DL)
If an email DL includes an invalid email address, all email addresses in the list are impacted. When a notification alert is sent, none of the recipients in the DL receive the alert.