Oracle understands that e-mail is a real-time service, and we work hard to ensure that the right e-mail reaches the right user at the right time. It is also important, however, to ensure our users are protected from unwanted e-mail, viruses, and malware. To that end we have implemented several layers of protection utilizing market-leading technology. If there is a delivery issue, it is important to understand that the sending party remains solely and fully responsible for e-mail until it is accepted by the Oracle relays for delivery.
This site provides information to technology professionals who administer systems that send/receive e-mail from Oracle.com. It also provides information for external users and users with Oracle.com accounts to help resolve issues with delivery or receipt of e-mail. When investigating issues it is important that IT personnel from your organisation are directed to this page. Please select from the links below.
Oracle requires that all e-mail sent through its servers follows Oracle E-Mail Guidelines as well as any applicable laws. Following the e-mail guidelines does not guarantee that your e-mail will be delivered; however it should decrease the chances of your e-mail being misidentified and blocked as unsolicited e-mail or spam.
Technical Requirements
Policy Requirements
Authentication
Reputation
5.0.0—Requested action not taken: mailbox unavailable
Indicates a mispelled address or an address that is no longer in use. Check the spelling and ensure the address is still valid. If you are sure that the account is valid and correctly spelled, check with the recipient to ensure that the account is not temporarily unavailable.
5.7.0—Local Policy Violation
Indicates a hard coded block. Contact your IT department and refer them to E-Mail Good Practices and How to Report an Issue.
5.7.0—Exceeded message acceptance limits.
Indicates that your message is too big. Oracle will not accept mail greater than 50MB in size and additional restrictions apply when container or compressed files attached to the message are uncompressed. Be aware that message text, headers, attachments and embedded images will all contribute to overall message size. In the event you need to discuss an issue further please contact your IT department and refer them to Postmaster E-Mail Good Practices and How to Report an Issue.
5.7.0—Message Processing Timeout
Indicates that the message has taken too long to process for delivery. Please resend the message. If the error occurs again, contact your IT department and refer them to E-Mail Good Practices and How to Report an Issue.
5.7.0—Rejected by Oracle.com Spam Policies
Message has been flagged as a possible phishing attack address. Contact your IT department and refer them to E-Mail Good Practices and How to Report an Issue.
5.7.0—Message Rejected for Containing a Virus
Message has been flagged as infected with a known virus. Please contact your IT department providing details of the error message. Additionally your IT department may need to follow up with Oracle.com, so please refer them to E-Mail Good Practices and How to Report an Issue.
5.7.0—Message Rejected for SPAM Content
Message has been flagged as containing spam content. Contact your IT department and refer them to E-Mail Good Practices and How to Report an Issue.
5.1.1—User Unknown
Recipient validation is unable to verify the e-mail address. Check and verify the address before attempting to send again. If you are still unable to deliver contact your IT department and refer them to E-Mail Good Practices and How to Report an Issue.
The following recipient(s) could not be reached:
-----------@oracle.com
Error Type: SMTP
Remote server (W.X.Y.Z) issued an error.
hMailServer sent:
Remote server replied: 554 Blocked - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=W.X.Y.Z//
Proofpoint carries out IP reputation validation for Oracle. In this instance the sending IP and domain have been classified as having a bad reputation and the e-mail in question has not been delivered to Oracle.com. It is up to the sending domain to contact Proofpoint to discuss their reputation. Contact your IT department and use the URL in the error message to contact Proofpoint. Oracle cannot discuss the IP reputation of an external company with Proofpoint.
Status : Deferred
Delivery temporarily suspended - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=W.X.Y.Z//
Proofpoint is unable to deliver e-mail from a particular sender/email address at the current time. Contact your IT department and use the URL in the error message to contact Proofpoint. Oracle cannot contact Proofpoint on behalf of an external company.
4.4.0—Local Policy Violation, try again later.
The sending IP address is requesting too many connections. Please review E-Mail Good Practices to ensure that you are following Oracle guidelines for e-mail delivery. Contact your IT department and refer them to How to Report an Issue.
4.1.1—User Unknown, try again later.
Not possible to verify the e-mail address. Check and verify before sending again. If delivery is still not possible, contact your IT department and refer them to How to Report an Issue
Alert your IT department, provide them with the error message you have received and request that they review our E-Mail Good Practices and E-Mail Error Messages. In many cases this will provide an explanation for why the e-mail was not delivered. If further assistance is required refer to How to Report an Issue for more information on engaging with the Postmaster team at Oracle.com and alert your contact at Oracle.com so they can log an internal service request.
Check with the recipient by alternative means to ensure the mailbox is not temporarily unavailable. Alert your IT department and request that they review our E-Mail Good Practices and E-Mail Error Messages. If further assistance is required your IT department should refer to How to Report an Issue and alert your contact at Oracle.com so they can log an internal service request.
Whitelisting reduces Oracle’s ability to leverage our message protection services, so we do not accept whitelisting requests from external companies. Any issues are instead investigated to find a resolution and whitelisting is only ever carried out in exceptional circumstances. Oracle.com evaluates all inbound e-mail for malicious content. If you have adhered to industry and Oracle guidelines you maximize the chances of your e-mail being delivered. Review E-Mail Good Practices and E-Mail Error Messages. Oracle cannot speak to Proofpoint on behalf of any external company, so any errors received from Proofpoint will need to be followed up directly with them. If further assistance is required, please refer your IT department to How to Report an Issue and alert your contact at Oracle.com so they can log an internal service request.
Review E-Mail Good Practices and E-Mail Error Messages and speak to your IT department. Any errors received from Proofpoint need to be followed up directly with them, as Oracle cannot speak to Proofpoint on behalf of any external company. If further assistance is required your IT department should refer to How to Report an Issue and alert your contact at Oracle.com so they can log a service request.
50MB is the maximum size of e-mail message that Oracle.com will accept from the Internet or deliver from Oracle.com. This includes the message text, headers, attachments and any embedded images. In addition to this there is another restriction in place which applies when any container or compressed files attached to an email are uncompressed. For further information and to contact Oracle Postmaster refer to E-Mail Good Practices and How to Report an Issue. Please also alert your contact at Oracle.com as they may be able to discuss an alternative means of information transfer with you.
Refer to the IP reputation section of E-Mail Good Practices. Any errors received from Proofpoint need to be followed up directly with them since Oracle cannot speak to Proofpoint on behalf of any external company. If further assistance is required, please refer to How to Report an Issue and alert your contact at Oracle.com so they can log a service request.
Oracle uses opportunistic TLS. If forced TLS is a requirement, please speak directly to your contact at Oracle.
Review and adhere to E-Mail Good Practices.
Please refer to How to Report an Issue and alert your contact at Oracle.com.
Oracle has e-mail relays in multiple locations for redundancy. The list below includes the primary corporate e-mail relays.
Inbound Servers
mxa-00069f01.gslb.pphosted.com - 205.220.165.26
mxb-00069f01.gslb.pphosted.com - 205.220.177.26
Outbound Servers
mx0b-00069f02.pphosted.com - 205.220.177.32
mx0a-00069f02.pphosted.com - 205.220.165.32
Oracle blocks attachments using two different sets of criteria:
Therefore renaming a blocked attachment extension will not allow delivery. Please discuss an alternative method of data transfer with your contact at Oracle.com.
The table below lists blocked attachments:
386 | crt | lnk | sct | dmg |
3gr | dbx | mdb | shb | ws |
add | dll | mde | shs | ps1 |
ade | exe | mim | url | ps1xml |
asp | fon | msc | uu | ps2 |
b64 | hlp | msi | vb | ps2xml |
bas | hqx | msp | vbe | psc1 |
bat | hta | mst | vbs | psc2 |
bhx | inf | ocx | vxd | msh |
chm | ins | pcd | wsc | msh1 |
cmd | isp | pif | wsf | msh2 |
com | js | reg | wsh | mshxml |
cpl | jse | scr | xxe | msh2xml |
scf | class | jar | iso |
Process to Follow When Reporting an Issue
Customers Sending System Alerts to Oracle Service Teams or Individuals
These measures will ensure that incoming messages adhere to Oracle anti-spoofing policy.
For Oracle Employees