Mail Validation Troubleshooting

This page is accessed via Business Process Automation > Power Data > Mail Management > Mail Validation.

When validating your ability send email, you may encounter different error codes. Use this page to research what the errors mean, and how to fix them.

Note: Make a note of the Mail Log ID, and the From and To emails, and be prepared to share that information with Support. Log IDs may be reused after 2 days.

Diagnosing Mail Validation Errors

The following tables describe each mail validation error, its causes and recommended resolution steps.

Many of the resolutions include preparing a mail log for request for Oracle Support. To do this:

Take note of the validation inputs. I.e., collect the From address (if running from Mail Senders) and the To address and Subject (if running from Mail Validation).
Take note of the Mail Log ID listed on the Mail Validation results frame.
Go to the Collect Diagnostic Logs screen. Select the Mail log in the additional Logs selection. Submit.
Take note of the archive name.
Open a support ticket including the validation inputs from #1, the Mail Log ID from #2 and the archive name from #4.

This will enable the mail log for your validation test to be correctly uploaded for Support review. It should contain all Oracle Cloud, DNS and Oracle Transportation Management information needed to proceed with issue analysis.

Valid Sender

Error Code	Summary	Error Description	Resolution Steps
VS-001	The sender is not a common sender made available for use by Oracle. It, or its domain, must be explicitly registered as a Mail Sender.	The mail sender is not a Common Mail Sender. Each mail senders must either be a common mail sender, explicitly registered as a valid Mail Sender, or belong to an Approved Domain (i.e. a Mail Sender of the form @<domain>).	If you had intended to use a Common Sender, check your From address to make sure it matches a published Common Mail Sender for your region. The list of Common Senders can be found in the Using a Common Approved Sender Email Address section of the Oracle Fusion Cloud Transportation and Global Trade Management Administration Guide. If you’ve confirmed the from address is the correct Common Mail Sender, prepare a mail log request for Oracle support and open a Service Request to diagnose the issue.
VS-011	Neither the sender not its domain have been registered as a Mail Sender. Please navigate to Mail Senders and add it.	The mail sender has not been registered as a Mail Sender with Oracle Mail, nor has its domain been registered as an Approved Domain (i.e. a Mail Sender of the form @<domain>). All outbound emails with this sender will be blocked.	Go to the Mail Senders screen and add the From address. Alternatively, register the from addresses as an Approved Domain by adding a mail sender of the form @<domain>. This permits all from parties in that domain to act as mail senders in Oracle Mail. Note that the Approved Domain registration will fail unless all DKIM checks below pass. If this fails, it is likely another division or a partner organization is already using the From address or Approved Domain. Only one organization may use a Mail Sender at a time, excluding Common Senders. Please prepare a mail log request for Oracle support and open a Service Request to resolve proper usage of the From address.
VS-012	The Mail Sender for this sender exists but is not active. Please work with support to resolve this issue.	The mail sender or domain has been registered as a Mail Sender with Oracle Mail but is not in an active state.	Wait a few minutes and retry mail validation. If the problem persists, prepare a mail log request for Oracle support and open a Service Request to determine why the mail sender state is invalid.
VS-013	The sender address or domain cannot be used. Please contact Oracle support for resolution.	The mail sender or domain has already been registered for use by another organization.	Mail senders and Approved Domains cannot be shared across organizations. Please use another mail sender or domain. If you believe the mail sender assignment is incorrect, please open a Service Request to resolve the conflict.
VS-014	This sender belongs to a public domain and cannot be registered as a mail sender for Mail Delivery.	The mail sender or domain cannot be from a public domain such as gmail.com, hotmail.com, or yahoo.com.	Use a domain local to your organization for mail senders.

SPF

Error Code	Summary	Error Description	Resolution Steps
SPF-001	No SPF records have been found for domain <D>. Please work with your DNS administrator to properly configure SPF for Oracle Mail.	Sender Policy Framework (SPF) has not been set up for the sender’s email domain. This occurs because a query for DNS TXT records in the sender domain found no records matching Section 3 in the RFC 7208 specification for SPF. I.e., no TXT record has a string value beginning with ‘v=spf1’.	Review the Configuring SPF section of the Oracle Fusion Cloud Transportation and Global Trade Management Administration Guide. While SPF may not be required in your or a partner’s organization, Oracle recommends it be added to reduce the chance of spamming and fraudulent emails. SPF is not always needed for successful sending of email message but specific mail accounts or receiving systems may require it. After adding an SPF record for the email domain, you must wait for it to propagate across DNS. This may take up to 72 hours for worldwide notification of your TXT addition to be available to Oracle validation. Once this time has passed, repeat the mail validation. If there is a valid SPF record for the email sender domain in DNS, or the mail validation continues to fail after SPF addition, prepare a mail log request for Oracle support and open a Service Request to investigate further.
SPF-011	The SPF check for the domain of this sender failed due to a possible gateway issue. Please contact support.	A gateway failure occurred while trying to validate SPF setup for this mail sender.	Prepare a mail log request for Oracle support and open a Service Request to resolve communication issues to the outbound gateway.
SPF-012	Oracle Mail is not approved to send out emails from the domain of this sender, but is not being blocked. Please work with your DNS administrator to add the proper Oracle Mail Server to your SPF configuration.	The SPF record for this sender domain in DNS is likely: Missing an include directive for the Oracle Cloud public outbound email servers; or Explicitly marking the Oracle Cloud public outbound email servers with a soft bounce instruction (~) A soft bounce may also indicate a temporary issue in the forwarding of Oracle Cloud emails to mailbox providers.	Review the Configuring SPF section of the Oracle Fusion Cloud Transportation and Global Trade Management Administration Guide to determine the proper outbound email servers for your region. Work with your (or your partner’s) DNS administrator to add the email server to the SPF TXT record as an authorized sender (e.g. +include:<oracle server>). Take care not to remove other approved servers outside of Oracle. Ask your DNS administrator for the Time To Live (TTL) on the DNS TXT record. You should not retry the validation until the time to live has expired and all publicly cached records are updated. This is typically 12 or 24 hours. Note that outbound e-mails are often successfully received even if SPF directs mailbox providers to soft bounce emails from this sender. It is the decision of each mailbox provider how to handle SPF instructions. Soft bounces, however, may result in the mailbox provider blocking or quarantining emails. It is good practice to correctly set up the SPF record of each sender domain to accept emails from Oracle Mail servers without bounce. If the problem persists after TTL, prepare a mail log request for Oracle support and open a Service Request to analyze the source of the soft bounce.
SPF-013	Oracle Mail is not approved to send out emails from the domain of this sender. Please work with your DNS administrator to add the proper Oracle Mail Server to your SPF configuration.	The SPF record for this sender domain is likely: Missing an include directive for the Oracle Cloud public outbound email servers; or Explicitly marking the Oracle Cloud public outbound email servers with a hard bounce instruction (-) A hard bounce reflects a permanent issue in validating sender domains from the Oracle Mail servers. It may result in undelivered emails and recipients being suppressed by Oracle Mail due to receipt of hard bounce from mailbox providers.	Review the Configuring SPF section of the Oracle Fusion Cloud Transportation and Global Trade Management Administration Guide to determine the proper outbound email servers for your region. Work with your (or your partner’s) DNS administrator to add the email server to the SPF TXT record as an authorized sender (e.g. +include:<oracle server>). Take care not to remove other approved servers outside of Oracle. Ask your DNS administrator for the Time To Live (TTL) on the DNS TXT record. You cannot retry the validation until the time to live has expired and all publicly cached records are updated. This is typically 12 or 24 hours. Note that outbound e-mails may be temporarily successful even if SPF directs mailbox providers to hard bounce emails from this sender. Rules within Oracle Mail determine when a sufficient volume of hard bounce responses force a suppression of mail to a particular recipient. If hard bounces are not resolved, it is likely that recipients will not receive their emails and end up on the Mail Suppression list. If the problem persists after TTL, prepare a mail log request for Oracle support and open a Service Request to analyze the source of the hard bounce.
SPF-014	Oracle Mail is not approved to send out emails from the domain of this sender based on incorrect SPF configuration. Please work with your DNS administrator to add the proper Oracle Mail Server to your SPF configuration.	The SPF check for this sender domain is failing due to incorrect mail server specifications in DNS.	Prepare a mail log request for Oracle support and open a Service Request to analyze the failure.
SPF-015	DNS lookups for domain {domain} have timed out after {timeout} seconds. SPF setup cannot be validated at this time. This is likely due to Time to Live (TTL) timeouts on cached DNS information, followed by a slow refresh from your DNS provider. Depending on recipient mailboxes, this may cause mail quarantine, rejection and/or Oracle Mail suppression. Please work with your DNS administrator to determine the underlying cause of DNS query delays.	Internet mail servers cache DNS information for your domain, including SPF details, on local servers. This can include application servers, mail servers and mailbox hosts. When the SPF Time-To-Live (TTL) value expires, these caches must be flushed. This forces these servers to retrieve DNS information directly from your DNS provider, adding network latency to the data retrieval. Mailbox providers may react in different ways to such a timeout, as they cannot validate the SPF information. Emails may be quarantined Emails may be rejected with a hardbounce. This may result in Mail Suppressions in Oracle Mail for the recipient addresses that were bounced. Emails may be accepted but marked as spam. Any such behavior may seem intermittent.	The default timeout for DNS checks in Mail Validation is 10 seconds. This can be configured with the property: glog.dns.timeout=<timeout in milliseconds> While this error can be resolved by increasing this timeout, there are three cases to consider: OTM timeout < mail box timeouts. Mail Validation errors may be a false negatives. Mail boxes may have given themselves sufficient time to wait for a slow DNS provider. OTM Timeout = mail box timeouts. Here, Mail Validation errors reflect true errors likely to occur with mail box providers. When the provider hits a DNS timeout, emails may be lost and/or suppressed. OTM Timeout > max box timeouts. Mail Validation success may be a false positive. While OTM is waiting sufficiently long for DNS provider response, mail box providers may not. Emails may be lost and/or suppressed. For cases #2 or #3, please work with DNS administrators to determine why DNS retrieval is too slow for the timeouts. Reconfiguring the Mail Validation timeout in Oracle Transportation Management has no impact on DNS timeouts in Oracle Mail or various mailbox providers.
SPF-016	During SPF verification, lookups on domain {domain} timed out. This is the likely cause of any PERMERROR or TEMPERROR reports from this domain and due to a TTL timeout with a slow DNS provider. Please work with your DNS administrator to determine the underlying cause of DNS query delays.	One or more mail servers checked for SPF validation has timed out on a DNS lookup. This is likely due to Time-To-Live TTL expiration on these servers, resulting in a need to retrieve DNS information from the domain’s DNS provider. While some domains may have been successfully verified, failure in any particular domain can result in intermittent errors where Emails are quarantined Emails are rejected with a hardbounce, possibly leading to Mail Suppression in Oracle Mail for the recipient address. Emails are accepted but marked as spam.	The default timeout for DNS checks in Mail Validation is 10 seconds. This can be configured with the property: glog.dns.timeout=<timeout in milliseconds> While this error can be resolved by increasing this timeout, there are three cases to consider: OTM timeout < mail box timeouts. Mail Validation errors may be a false negatives. Mail boxes may have given themselves sufficient time to wait for a slow DNS provider. OTM Timeout = mail box timeouts. Here, Mail Validation errors reflect true errors likely to occur with mail box providers. When the provider hits a DNS timeout, emails may be lost and/or suppressed. OTM Timeout > max box timeouts. Mail Validation success may be a false positive. While OTM is waiting sufficiently long for DNS provider response, mail box providers may not. Emails may be lost and/or suppressed. For cases #2 or #3, please work with DNS administrators to determine why DNS retrieval is too slow for the timeouts. Reconfiguring the Mail Validation timeout in Oracle Transportation Management has no impact on DNS timeouts in Oracle Mail or various mailbox providers.

Email Domain

Error Code	Summary	Error Description	Resolution Steps
ED-001	No Email Domain is configured for domain <D>. This is required for DKIM checks. Please work with support to request an Email Domain for this sender if DKIM is necessary.	An Oracle Cloud Email Domain has not been configured for the domain of the sender email. This is a prerequisite for configuration of Domain Keys Identified Mail (DKIM).	Review the Configuring DKIM section of the Oracle Fusion Cloud Transportation and Global Trade Management Administration Guide to understand the use and configuration of DKIM for the sender domain. While DKIM may not be required in your or a partner’s organization, Oracle recommends it be enabled to ensure reliable delivery of your email and guarantee proper validation of generated email messages. To begin DKIM configuration, go to the Mail Domains screen and add the email domain. This will prompt you for a unique organization name and build a DKIM selector based on the cloud region, organization and date. Up to two DKIM entries are automatically added for use with your DNS (this depends on whether you opt into AUTOMATIC DKIM ROTATION). This allows Mail Delivery to automatically rotate DKIM keys without additional configuration required in your DNS domain. Work with your DNS administrator to add CNAME records based on the values in the DNS subscreen.
ED-002	No Email Domain configured for domain <D> is active. Please work with support to resolve this issue.	The Oracle Cloud Email Domain configured for this sender email is not in a usable state.	Please wait a few minutes and retry mail validation. If the problem persists, prepare a mail log request for Oracle support1 and open a Service Request to determine why the email domain state is invalid.
ED-003	The Email Domain {domain} should have a valid A, AAAA or MX record; or a CNAME record that eventually evaluates to a valid A, AAAA or MX record. Please see best practices in the Administration Guide for more information.	The Email Domain for this sender should map to a mail server accepting mail for postmaster@domain and abuse@domain without bouncing. For more details, see MAAWG Best Practices for Sending Domains. This requires the domain have a valid DNS A, AAAA or MX record, or indirectly resolve to a valid mail server via a CNAME alias.	Please work with your DNS administrator to map your domain to a valid server.
ED-004	DNS lookups for domain {domain} have timed out after {timeout} seconds. The Email Domain cannot be fully validated at this time. This is likely due to Time to Live (TTL) timeouts on cached DNS information, followed by a slow refresh from your DNS provider. Depending on recipient mailboxes, this may cause mail quarantine, rejection and/or Oracle Mail suppression. Please work with your DNS administrator to determine the underlying cause of DNS query delays.	Internet mail servers cache information for your domain, including server references, on local servers. This can include application servers, mail servers and mailbox hosts. When the Time-To-Live (TTL) value expires, these caches must be flushed. This forces these servers to retrieve DNS information directly from your DNS provider, adding network latency to the data retrieval. Mailbox providers may react in different ways to such a timeout, as they cannot validate the information. Emails may be quarantined Emails may be rejected with a hard bounce. This may result in Mail Suppressions in Oracle Mail for the recipient addresses that were bounced. Emails may be accepted but marked as spam. Any such behavior may seem intermittent.	The default timeout for DNS checks in Mail Validation is 10 seconds. This can be configured with the property: glog.dns.timeout=<timeout in milliseconds> While this error can be resolved by increasing this timeout, there are three cases to consider: OTM timeout < mail box timeouts. Mail Validation errors may be a false negatives. Mail boxes may have given themselves sufficient time to wait for a slow DNS provider. OTM Timeout = mail box timeouts. Here, Mail Validation errors reflect true errors likely to occur with mail box providers. When the provider hits a DNS timeout, emails may be lost and/or suppressed. OTM Timeout > max box timeouts. Mail Validation success may be a false positive. While OTM is waiting sufficiently long for DNS provider response, mail box providers may not. Emails may be lost and/or suppressed. For cases #2 or #3, please work with DNS administrators to determine why DNS retrieval is too slow for the timeouts. Reconfiguring the Mail Validation timeout in Oracle Transportation Management has no impact on DNS timeouts in Oracle Mail or various mailbox providers.
ED-005	The Email Domain {domain} is not common, nor in use by your organization. Please contact support.	The Email Domain for this sender has been registered but is either used for Common Mail Senders or has not been assigned to your organization.	Please work with support to assign the Email Domain to your account or overall organization.
ED-006	The Email Domain {domain} cannot be used. Please contact support.	The Email Domain for this sender is not available for self-service.	Please work with support to resolve rights to this domain. This may require assigning a common organization name across multiple Oracle Transportation accounts.

DKIM

Error Code	Summary	Error Description	Resolution Steps
DKIM-001	DKIM is not configured for domain <D>. Please work with support to enable DKIM for this domain within OCI.	No DKIM records are associated with this senders Oracle Cloud Email Domain. When the service request to create an Email Domain was received, a DKIM record should have been associated with the domain. This DKIM record contains information needed to properly link the public DNS records for the email domain to the DKIM public key for proper email signing. The DKIM record is missing.	See steps under ED-001 to add a Mail Domain to your organization. Note that Mail Delivery is not blocked while DKIM is not correctly configured. Oracle Mail determines whether DKIM is fully available for a given outbound mail. Only when both Oracle Cloud and DNS are correctly configured for DKIM are outbound emails signed for DKIM. If the problem persists, prepare a mail log request for Oracle support and open a Service Request to resolve the issue.
DKIM-002	No DKIM configured for domain <D> is active. Please work with support to resolve this issue.	The DKIM record associated with the Oracle Cloud Email Domain is not active.	Please wait a few minutes and retry mail validation. Note that Mail Delivery is not blocked while DKIM is not correctly configured. Oracle Mail determines whether DKIM is fully available for a given outbound mail. Only when both Oracle Cloud and DNS are correctly configured for DKIM are outbound emails signed for DKIM. If the problem persists, prepare a mail log request for Oracle support and open a Service Request to determine why the DKIM state is inactive.
DKIM-003	The primary DKIM configured for domain <D> requires attention. Please review the DNS Configuration for this DKIM.	Though a primary DKIM has been configured in Oracle Cloud for the email sender domain, it is failing validation. This is likely due to misconfiguration of public DNS records required by DKIM.	Review the subsequent DKIM-01x or DKIM-02x error messages for the primary DKIM record and resolve the DNS issues accordingly. For Oracle Mail to support DKIM, the DNS administrator for the email sender domain must create one of two records using information provided by Oracle in your DKIM Configuration Service Request: A CNAME record, redirecting the Oracle subdomain name for the public key back to the Oracle CNAME value. Both the subdomain name and CNAME value are supplied by Oracle Support when the Email Domain is provisioned in Oracle Cloud. Mailbox providers use this CNAME record to retrieve the public key for email signing. A TXT record, mapping the Oracle subdomain name to a DKIM TXT record (i.e. one whose text value include ‘v=dkim1’ along with public key details). This is an alternative, older approach for mailbox providers that need a direct public key for email signing. The public key for this TXT record can be obtained when the Email Domain is provisioned in Oracle Cloud. DKIM will fail if: Neither the CNAME or TXT record can be found for the Oracle subdomain provisioned with the Email Domain. The CNAME value does not match the string provided by Oracle Support during Email Domain provisioning. The TXT value does not match the string provided by Oracle Support during Email Domain provisioning. Note that Mail Delivery is not blocked while DKIM is not correctly configured. Oracle Mail determines whether DKIM is fully available for a given outbound mail. Only when both Oracle Cloud and DNS are correctly configured for DKIM are outbound emails signed for DKIM. If no DKIM-01x or DKIM -02x errors are displayed, prepare a mail log request for Oracle support and open a Service Request to determine why the DKIM setup needs attention.
DKIM-004	The email domain {domain} is missing a DKIM for automatic key rotation. Emails can be sent out without it but key rotation requires manual intervention.	Automatic DKIM rotation has been opted in (SUPPORT DKIM ROTATION) but two DKIM records have not been configured in the email sender domain.	Navigate to the Mail Domain screen for this domain and check the DNS records. Use Add All to ensure all necessary DKIM records have been created. Work with your DNS administrator to add a CNAME record for any new DKIM records added by this function.
DKIM-005	The secondary DKIM configured for domain <D> requires attention. Please review the DNS Configuration step and work with support to resolve any issues.	Though a secondary DKIM has been configured in Oracle Cloud for the email sender domain, it is failing validation. This is likely due to misconfiguration of public DNS records required by DKIM.	Review the subsequent DKIM-01x or DKIM-02x error messages for the secondary DKIM record and resolve the DNS issues accordingly. For Oracle Mail to support DKIM, the DNS administrator for the email sender domain must create one of two records using information provided by Oracle in your DKIM Configuration Service Request: A CNAME record, redirecting the Oracle subdomain name for the public key back to the Oracle CNAME value. Both the subdomain name and CNAME value are supplied by Oracle Support when the Email Domain is provisioned in Oracle Cloud. Mailbox providers use this CNAME record to retrieve the public key for email signing. A TXT record, mapping the Oracle subdomain name to a DKIM TXT record (i.e. one whose text value include ‘v=dkim1’ along with public key details). This is an alternative, older approach for mailbox providers that need a direct public key for email signing. The public key for this TXT record can be obtained when the Email Domain is provisioned in Oracle Cloud. DKIM will fail if: Neither the CNAME or TXT record can be found for the Oracle subdomain provisioned with the Email Domain. The CNAME value does not match the string provided by Oracle Support during Email Domain provisioning. The TXT value does not match the string provided by Oracle Support during Email Domain provisioning. Note that Mail Delivery is not blocked while DKIM is not correctly configured. Oracle Mail determines whether DKIM is fully available for a given outbound mail. Only when both Oracle Cloud and DNS are correctly configured for DKIM are outbound emails signed for DKIM. If no DKIM-01x or DKIM -02x errors are displayed, prepare a mail log request for Oracle support and open a Service Request to determine why the DKIM setup needs attention.
DKIM-011	No CNAME record was found for the DNS subdomain <S>. Please work with your DNS administrator to register the proper CNAME record value supplied by OCI Email Delivery.	No CNAME record was found in DNS for one of the Email Sender subdomains needed for DKIM signing. This error can be ignored if you are old-style TXT records to hold the public DKIM key.	Check the DNS values from the Mail Domains screen to ensure you have the correct subdomain keys and CNAME values for your DNS CNAME records supporting DKIM. Work with your (or your partner’s) DNS administrator to add the CNAME record to the subdomain. Ensure the value on this record matches the value provided by Oracle. Wait for the new record to propagate across DNS. This may take up to 72 hours for worldwide notification of your CNAME addition to be available to Oracle validation. Note that Mail Delivery is not blocked when DKIM is not correctly configured. Oracle Mail determines whether DKIM is fully available for a given outbound mail. Only when both Oracle Cloud and DNS are correctly configured for DKIM are outbound emails signed for DKIM. If the problem persists after TTL, prepare a mail log request for Oracle support and open a Service Request to determine why the CNAME record is not in agreement with DKIM assumptions.
DKIM-012	The CNAME record value specified in the DNS subdomain <S> does not properly map back to the OCI Email Delivery DKIM record for your domain. Please work with your DNS administrator to map the CNAME record value supplied by OCI Email Delivery.	The CNAME record found in DNS for one of the Email Sender subdomains has a value that does not match the one supplied by Oracle during Email Domain provisioning. This value allows mailbox providers to retrieve DKIM public keys from Oracle DNS.	Check the DNS values from the Mail Domain screen to ensure you have the correct subdomain keys and CNAME values for your DNS CNAME records supporting DKIM. Work with your (or your partner’s) DNS administrator to ensure the CNAME value in the email subdomain matches the provided value. If not, correct it. Ask your DNS administrator for the Time To Live (TTL) on the DNS TXT record. You should not retry the validation until the time to live has expired and all publicly cached records are updated. This is typically 12 or 24 hours. Note that Mail Delivery is not blocked when DKIM is not correctly configured. Oracle Mail determines whether DKIM is fully available for a given outbound mail. Only when both Oracle Cloud and DNS are correctly configured for DKIM are outbound emails signed for DKIM. If the problem persists after TTL, prepare a mail log request for Oracle support and open a Service Request to analyze the disagreement in CNAME expectations.
DKIM-021	No TXT record was found for DKIM or the DKIM public key does not match the one expected by the DNS subdomain <S>. Either revert to CNAME-based DKIM or work with your DNS administrator to map the Text record value supplied by OCI Email delivery to a DNS TXT record for DKIM	The DKIM TXT record found in DNS for the Email Sender subdomain has a value that does not match the public key value supplied by Oracle during Email Domain provisioning. This value is needed to properly decrypt signed email messages.	Check the DNS values from the Mail Domain screen to ensure you have the correct subdomain keys and CNAME values for your DNS CNAME records supporting DKIM. Work with your (or your partner’s) DNS administrator to ensure the DKIM TXT record (i.e. a TXT record with a ‘v=dkim1’ value) matches the provided TXT value. If not, correct it. Ask your DNS administrator for the Time To Live (TTL) on the DNS TXT record. You should not retry the validation until the time to live has expired and all publicly cached records are updated. This is typically 12 or 24 hours. Note that Mail Delivery is not blocked when DKIM is not correctly configured. Oracle Mail determines whether DKIM is fully available for a given outbound mail. Only when both Oracle Cloud and DNS are correctly configured for DKIM are outbound emails signed for DKIM. If the problem persists after TTL, prepare a mail log request for Oracle support and open a Service Request to analyze the disagreement in TXT expectations.
DKIM-031	DNS lookups for domain {domain} have timed out after {timeout} seconds. DKIM setup cannot be validated at this time. This is likely due to Time to Live (TTL) timeouts on cached DNS information, followed by a slow refresh from your DNS provider. If Oracle Mail sees a similar timeout, outbound messages won't be signed. Depending on recipient mailboxes, this may cause mail quarantine, rejection and/or Oracle Mail suppression. Please work with your DNS administrator to determine the underlying cause of DNS query delays.	Internet mail servers cache DNS information for your domain, including DKIM details, on local servers. This can include application servers, mail servers and mailbox hosts. When the DKIM Time-To-Live (TTL) value expires, these caches must be flushed. This forces these servers to retrieve DNS information directly from your DNS provider, adding network latency to the data retrieval. Mailbox providers may react in different ways to such a timeout, as emails may not be properly signed. Emails may be quarantined Emails may be rejected with a hardbounce. This may result in Mail Suppressions in Oracle Mail to the recipient addresses that were bounced. Emails may be accepted but marked as spam. Any such behavior may seem intermittent.	The default timeout for DNS checks in Mail Validation is 10 seconds. This can be configured with the property: glog.dns.timeout=<timeout in milliseconds> While this error can be resolved by increasing this timeout, there are three cases to consider: OTM timeout < mail box timeouts. Mail Validation errors may be a false negatives. Mail boxes may have given themselves sufficient time to wait for a slow DNS provider. OTM Timeout = mail box timeouts. Here, Mail Validation errors reflect true errors likely to occur with mail box providers. When the provider hits a DNS timeout, emails may be lost and/or suppressed. OTM Timeout > max box timeouts. Mail Validation success may be a false positive. While OTM is waiting sufficiently long for DNS provider response, mail box providers may not. Emails may be lost and/or suppressed. For cases #2 or #3, please work with DNS administrators to determine why DNS retrieval is too slow for the timeouts. Reconfiguring the Mail Validation timeout in Oracle Transportation Management has no impact on DNS timeouts in Oracle Mail or various mailbox providers.

Suppression

Error Code	Summary	Error Description	Resolution Steps
ES-001	Mail for this recipient has been suppressed by Oracle Mail due to <reason>. Please correct the underlying reason for the suppression. Then navigate to Mail Suppressions and Unsuppress the recipient.	The email recipient is currently blocked by Oracle Mail Suppression. The reasons a mail recipient may be added to the suppression list include: Complaints Hard bounces Repetitive soft bounces Manual entry List-unsubscribe requests Note that bounces may be due to explicit rejections by rules at mailbox providers (e.g. Reject all e-mails from ‘adomain’) or from incorrect SPF set up.	Go to the Mail Failures screen and reset the blocked email address. Note this may be a temporary fix. If the reason a mail recipient was added to the suppression list is not addressed, future emails to that recipient are likely to lead to renewed suppression.
ES-011	Mail for this recipient is suppressed. The Oracle Transportation Management quota for <group> has been exceeded.	A mail quota enforced by Oracle Transportation Management has been exceeded. The email is blocked until sufficient time has passed and the quota no longer applies.	Please review the Managing Mail Quota section of the Oracle Fusion Cloud Transportation and Global Trade Management Administration Guide. Validating mail may need to be delayed until your mail quotas do not exceed the staged maximums. Also, go to the Mail Quota Groups screen and check for any custom mail quotas you may have entered.

Error Code

Summary

Error Description

Resolution Steps

ES-001

Mail for this recipient has been suppressed by Oracle Mail due to <reason>. Please correct the underlying reason for the suppression. Then navigate to Mail Suppressions and Unsuppress the recipient.

The email recipient is currently blocked by Oracle Mail Suppression.

The reasons a mail recipient may be added to the suppression list include:

Complaints
Hard bounces
Repetitive soft bounces
Manual entry
List-unsubscribe requests

Note that bounces may be due to explicit rejections by rules at mailbox providers (e.g. Reject all e-mails from ‘adomain’) or from incorrect SPF set up.

Go to the Mail Failures screen and reset the blocked email address.

Note this may be a temporary fix. If the reason a mail recipient was added to the suppression list is not addressed, future emails to that recipient are likely to lead to renewed suppression.

ES-011

Mail for this recipient is suppressed. The Oracle Transportation Management quota for <group> has been exceeded.

A mail quota enforced by Oracle Transportation Management has been exceeded. The email is blocked until sufficient time has passed and the quota no longer applies.

Please review the Managing Mail Quota section of the Oracle Fusion Cloud Transportation and Global Trade Management Administration Guide. Validating mail may need to be delayed until your mail quotas do not exceed the staged maximums.

Also, go to the Mail Quota Groups screen and check for any custom mail quotas you may have entered.

SMTP

Error Code	Summary	Error Description	Resolution Steps
SMTP-001	Email for this recipient has not been sent. The size of the email, <size>, exceeds your maximum allotment in Oracle Transportation Management.	Oracle Transportation Management maintains a maximum mail size typically less than Oracle Mail constraints. This avoids suppressions in Oracle Mail. The maximum mail size has been exceeded.	Please submit a smaller attachment test for Mail Validation.
SMTP-011	Mail for this recipient has been refused due to <code>. The recipient is suppressed in Oracle Mail. Please correct the underlying reason for the suppression. Then navigate to Mail Suppressions and Unsuppress the recipient.	The email was rejected by Oracle Mail due to the recipient suppression. The reasons a mail recipient may be added to the suppression list include: Complaints Hard bounces Repetitive soft bounces Manual entry List-unsubscribe requests Note that bounces may be due to explicit rejections by rules at mailbox providers (e.g. Reject all e-mails from ‘adomain’) or from incorrect SPF set up.	Go to the Mail Failures screen and reset the blocked email address. Note this may be a temporary fix. If the reason a mail recipient was added to the suppression list is not addressed, future emails to that recipient are likely to lead to renewed suppression.
SMTP-012	Email for this recipient has been refused due to <code>. The maximum message rate has been exceeded. Please wait and try again.	The email was rejected by Oracle Mail due to exceeding the maximum message rate across the entire tenancy.	Prepare a mail log request for Oracle support and open a Service Request to analyze the tenancy message limits.
SMTP-013	Email for this recipient has been refused due to <code>. The size of the email exceeds your maximum quota in Oracle Mail.	The email was rejected by Oracle Mail due to exceeding the maximum message size for the tenancy.	Generally, Oracle Transportation Management mail limits are more strict than Oracle Mail. If this error occurs, prepare a mail log request for Oracle support and open a Service Request to analyze the tenancy message size limits.
SMTP-014	A transport error <code> occurred while sending email to this recipient. Please work with support to retrieve detail mail logs for analysis.	The transport of the email message failed.	Review the details of the error message in the EXCEPTION log. If the cause of the error cannot be easily ascertained, prepare a mail log request for Oracle support and open a Service Request to analyze the failure.
SMTP-015	A non-transport error occurred while sending email to this recipient. Please work with support to retrieve detail mail logs for analysis.	The email message could not be sent.	Review the details of the error message in the EXCEPTION log. If the cause of the error cannot be easily ascertained, prepare a mail log request for Oracle support and open a Service Request to analyze the failure.

SMTP Validation Passes but Email Not Received

There are many reasons why the above SMTP check may pass but e-mails are not received:

Mailbox providers may be configured to reject certain senders or recipients, sending the mail to Spam folders, quarantining the messages or rejecting the messages with a bounce.
Mailbox providers may be configured to reject certain sender domains, similarly sending mail to spam, quarantine or bounce.
Mailbox providers or domains may require SPF or DKIM. The failure of SPF or DKIM below may not stop Oracle Mail from distributing mail. But receiving systems or domains may reject these messages due to the lack mail protection.
If the SMTP check below passes, it means Oracle Transportation Management successfully sent out an e-mail to Oracle Mail. However, the system has no way to confirm the e-mail was received by the ultimate mailbox provider, nor that it can be viewed by the email user.

To determine if the mail message was correctly forwarded and accepted by the mailbox provider (e.g. Gmail), Oracle Mail supports a new feature: Email Logging. This provides additional detail as to:

the relaying of emails to the mailbox provider
notification if the email was delivered or bounced
notification if the email was marked as spam

Work with Oracle Mail support to enable these logs if such detail is required.