SMTP Integration
The only supported Simple Mail Transfer Protocol (SMTP) service is the
Oracle Cloud Infrastructure Email Delivery Service, which is embedded within your cloud service with the following restriction:
• When used with Oracle Utilities cloud services, the OCI Email Delivery Service may only be used to send emails to Oracle, for example to tell them that their batch job failed. Any attempts to use this embedded instance of the OCI Email Delivery Service for other purposes are blocked.
Implementation Guidelines:
• Customer subscribed OCI Email delivery is supported in the same region where your cloud services are deployed. There is no support for Cross region email server domains. @SMPT_SERVER@ will always point to the region where your cloud services are hosted.
• In order to use the Customer subscribed OCI Email, the following are required configuration on the “EMAIL_SENDER” message sender:
• SMPT Host Name: @SMTP_SERVER@ (Default / Do NOT Change)
• SMTP From Address: your fromaddress (Required)
• SMTP Username: your username (Required)
• SMPT Password: your password (Required)
Note: Customers may use F1-EmailService (Business Service) to perform email configuration testing.
• OCI Email delivery determines the "From Address" as follows:
a. If the "From Address" is provided in the F1-EmailService business service payload, it will be used to send the email.
b. If no "From Address" is provided in the business service payload and the message sender is configured, the “SMTP From Address” configured in message sender will be used.
• If no "SMTP From Address" is defined on the provided message sender, the system raises an error.
c. If no message sender present in the payload, we will use the default message sender. If no "SMTP From Address" is defined on the default message sender, the system raises an error.
Note: If you are using the OCI default SMTP Server, you must provide the following values for the "SMTP From Address" based on the type of environment in which your cloud services are deployed:
If you are using subscribed OCI Email Delivery, then you should use your own "SMTP From Address" and it should be used along with the User Name and Password defined on the Message Sender configuration.
Batch Error / Completion Notification
Cloud service customers can use the OCI Email Delivery System to send batch error / completion notifications (based on Batch Control parameter configuration) to individuals or email groups. This functionality can be used for both online batch job submission and / or via batch scheduler batch control configuration.
This functionality does not include email notification on Batch Level of Service algorithms (BLOS). The Health Check portal within the cloud service should be used to view BLOS notifications. Customers can write external probes to pull the BLOS notifications via cloud web services.
Additional Options for Extracting and Sending Data via Email Delivery
Some options for extracting and sending data to external systems via email include the following:
• Create a plug-in driven batch control that writes a file to Oracle Cloud Object Storage, and then write or configure a process (outside of the cloud service) that looks for these files and sends emails based on the extracted data in the file. For example, a process might create a "mail merge" file containing data for a number of entities for external email server consumption.
• Deploy a web service outside of the subscribed Oracle cloud service network that is accessible by your cloud service. Create a plug-in driven batch process or online algorithm that calls the external web service via a Message Sender for each email notification you wish to send.