Article
Managing Suppressions
docs.oracle.com
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Outbound Email Delivery may fail at various points in the delivery process and for various reasons: “Mailboxes may reject email with hard or repetitively soft bounces.” Email Delivery may reject emails due to complaints, manual entry or list-unsubscribe requests.
Incorrect SPF configuration can often lead to Email Delivery suppression. It’s important to correctly configure your SPF with respect to your e-mail domains and any downstream servers. Use the Mail Sender or Mail Validation screens to verify that your sender is properly configured for SPF verification. “See the Mail Quota section below for guidelines on monitoring your overall, per content and per recipient email use.” Monitoring Transportation and Global Trade Management Email Blocking
Monitoring Transportation and Global Trade Management Email Blocking “Unless using a pre-authorized sender address for outbound emails, customers must register all from addresses to Email Delivery via the Mail Sender screen.” Resolving Transportation and Global Trade Management Email Blocking
Logging: The MailError log ID shows the From and To address of each failed email. By setting up an ad-hoc log that enables this logging, all such email can be tracked as they fail. “whether the sender has been correctly registered as a valid Email Delivery Mail Sender” Historical Diagnostics: As part of Historical Metrics, the following metric types can be used to track mail suppression over the preceding hours, days and weeks: MAIL – FAILED shows a count of general mail failures due to addressing issues MAIL – SUPPRESSED sshows a count of mail failures due explicitly to Oracle Mail recipient suppression Note that these metrics are collected for three subcomponents: Total, Common Addresses and User Addresses. Common Addresses refer to valid senders pre-authorized for use for all Transportation and Global Trade Management customers. User Addresses refer to senders configured on the Mail Sender screen for your installation and domains.
If emails are failing due to Email Delivery recipient suppression, the underlying cause of Email Delivery Suppression should be determined and resolved (which may be due to an aberrant failure like a hard bounce due to temporary communication issues) Once resolved, you can request Email Delivery remove the mail suppression by clicking Unsuppress on the Mail Failures screen. Note that while this will remove the suppression, the removal may be temporary if the underlying cause is not resolved. Email Delivery may simply suppress the recipient address again. If this happens, Transportation and Global Trade Management needs to work with Oracle Cloud Email Operations to determine the cause. “It’s important to correctly configure your SPF with respect to your e-mail domains and any downstream servers.” Email Delivery suppression may also be due to excessive mail use. See the Mail Quota section below for guidelines on monitoring your overall, per content and per recipient email use.
In SPF records
Logging: The MailError log ID shows the From and To address of each failed email. By setting up an ad-hoc log that enables this logging, all such email can be tracked as they fail. “whether the sender has been correctly registered as a valid Email Delivery Mail Sender” Historical Diagnostics: As part of Historical Metrics, the following metric types can be used to track mail suppression over the preceding hours, days and weeks: MAIL – FAILED shows a count of general mail failures due to addressing issues MAIL – SUPPRESSED sshows a count of mail failures due explicitly to Oracle Mail recipient suppression Note that these metrics are collected for three subcomponents: Total, Common Addresses and User Addresses. Common Addresses refer to valid senders pre-authorized for use for all Transportation and Global Trade Management customers. User Addresses refer to senders configured on the Mail Sender screen for your installation and domains.