Close Search
No results found

Your search did not match any results.

We suggest you try the following to help find what you’re looking for:

  • Check the spelling of your keyword search.
  • Use synonyms for the keyword you typed, for example, try “application” instead of “software.”
  • Try one of the popular searches shown below.
  • Start a new search.
Trending Questions
 

Oracle Hardware, Software, and Services

Welcome to Oracle Postmaster

 

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.

E-Mail Best Practices

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
    • E-mail sent to Oracle must adhere to the CAN-SPAM regulations and where appropriate Article 13 of the European Union Directive on Privacy and Electronic Communications 2002/58/EC.
    • All e-mail must be RFC compliant(Refer to RFC 5321 & RFC 5322).
    • The Internet Society's Internet Engineering Task Force (IETF) publishes technical documents detailing internet standards for the transmission of internet mail. For more information on these technical guidelines, please view the following:
    • Mail servers should have valid reverse DNS records. See the following Wikipedia entry for further information. Sending address should be valid with reverse lookup, resolvable in DNS, and able to accept bounce-backs.
    • Mail servers should not act as open relays/proxies and they should be secured to prevent unauthorized or anonymous use.
    • Avoid sending from dynamic IP spaces or where the identity of the host changes frequently as Oracle.com may not be able to accept these connections.
  • Policy Requirements
    • Do not attempt to discover e-mail accounts by sending messages to the Oracle mail server(E-Mail Address Harvesting). Servers making this attempt will be blocked by Oracle.
    • Non-authorized use of an Oracle.com e-mail address by a non-Oracle-owned IP address space is not permitted.
    • Oracle imposes a maximum mail size limitation of 50MB when receiving mail from the internet or delivering mail from Oracle.com. This includes the message text, headers, attachments and any embedded images. Please also be aware that in addition to the maximum mail size there is an additional restriction that applies when container or compressed files attached to the mail are uncompressed.
    • Oracle strips executable attachments (including compressed attachments) from e-mail in line with industry standards. For further information and to view a complete list, see Blocked Attachments
    • Oracle makes use of rate control technology to slow down the acceptance of high flows of e-mail. This may delay receipt of e-mail and may result in the IP reputation of the sender being downgraded.
  • Authentication
    • Oracle employs industry standard anti-virus technologies to protect the Oracle.com domain from malware, phishing and targeted attacks.
    • Oracle publishes an SPF record listing the IP addresses that are authorized to send e-mail. We recommend you publish an SPF record and ensure your sending domains are listed in your record.
    • We recommend that you sign your E-Mail using DomainKeys Identified Mail (DKIM). Oracle employs DKIM for outgoing mail to enable receivers to validate the content of our e-mail.
    • Oracle employs DMARC to ensure that mail is properly authenticated against SPF and DKIM. The DMARC framework defines our actions in the event that mail fails our SPF and DKIM checks.
  • Reputation
    • Oracle recommends that anyone sending e-mail to Oracle.com should actively manage the reputation of outbound IPs.
    • Segregate IPs according to function thereby ensuring that bulk e-mail is not sent from the same IPs as user or transactional e-mail.
    • Recipient validation should be carried out to ensure that hard or soft bounces are investigated and inactive recipients removed.
    • Employ opt-in/out subscription.
    • Outgoing hosts should employ rate control technology.
    • Oracle recommends the use of SPF management. Ensure that your SPF record is up to date with any new sending IPs.
    • Ensure links within e-mail are to domains and not IP addresses.
    • Ensure that "from" and "to" addresses are the same. Sending address should be valid with reverse lookup, fully resolvable in DNS, and able to accept bounce-backs.
    • Avoid sending e-mail containing a single graphic or image. Likewise avoid sending HTML forms, JavaScript, or embedded objects.

E-Mail Error Messages

550 SMTP Error Code
  • 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.
More
554 SMTP Error Code

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.

More
421 SMTP Error Code

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.

More
440 SMTP Error Code

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

More

FAQs

IPV4Host—Primary Oracle Corporate / Oracle Public Cloud E-Mail Relays

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

Blocked Attachments

Oracle blocks attachments using two different sets of criteria:

  • specific extension name
  • MIME type

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

How to Report an Issue

We’re here to help

Engage a Sales Expert

Sign up by topic

Resources for
Why Oracle
Learn
What’s New
Contact Us