Known Issues for Email Delivery

Details: When sending email to multiple recipients with a client using the JavaMail library, if one or more of the email addresses is on the suppression list, the Email Delivery service returns a 254 SMTP status code. This error indicates an email was submitted with a recipient address that is suppressed.

The JavaMail library has the ability to accept a list of recipients and send only the valid ones by setting the sendPartial flag. However, this code is not able to detect the new server status code for suppression and drop just the suppressed addresses; instead, it aborts the entire send and returns an exception. Applications need to catch this exception and remove the suppressed recipient from the recipient list to send to the valid recipients from the set only. That is, the application code can catch com.sun.mail.smtp.SMTPAddressFailedException and call ex.getAddress() with the exception object to get the addresses to remove, and resubmit with those removed.

Workaround: Actively monitor your suppression lists and update your sending lists accordingly, so that suppressed addresses are not part of your email submission lists. For more information, see Managing the Suppression List.

Direct link to this issue: JavaMail issues occur when multiple recipients are set in an email and one or more of the email addresses are suppressed

Details: In the Console, if you choose a compartment other than root and then navigate to the Email Suppression list, the following error will occur when you attempt to add a suppression:

Error: The required compartmentId ocid1.compartment.oc1..aaaaaaaacq3ztcbrxvgfb35zj6wztdpwlkmzfh4rnsq63sugge624qr5cdla must be the root compartment for suppressions

Workaround: Navigate to the Approved Senders page, choose the root compartment, and then return to the Email Suppression list.

Direct link to this issue: Error occurs when attempting to add a suppression from a compartment other than root

Details: Federated users are supported for Email Delivery with the exception of older tenancies that do not use System for Cross-domain Identity Management (SCIM). SCIM will be the standard for all identity information access. All tenancies after Dec 2018 are SCIM.

Workaround: Ask an administrator in your Oracle Cloud Infrastructure tenancy to create a new user in the Console to be used with the Email Delivery service. Logging into the Console directly (not federated) will allow access to User Settings and SMTP Credentials.

Direct link to this issue:Unable to access SMTP credentials for older federated tenancies