Support Central
Steps that your email service provider or IT department can take to improve the receivability of emails to and from the Aconex platform.
Emails to and from Aconex are verified in two ways. Once, within the Aconex platform and, also, by your company's email server. If an email fails your email server's checks, it'll mark it as spam and you might not receive the email.
By knowing the security Aconex uses and adding some settings to your email server, you can help ensure the email receivability and reduce the chance of Aconex emails being marked as spam.
You might need your IT Manager or email service provider to add these settings for you.
Emails from Aconex are sent with the following security features:
All emails sent by Aconex will be FROM an email address ending with @aconex.com, @us.aconex.com, @au.aconex.com, @eu.aconex.com, @me.aconex.com, or @ksa.aconex.com.
All emails from the Lobby will be FROM an address ending with @scp-lobby.us.construction.ocs.oraclecloud.com or @identity.oci.oraclecloud.com.
All emails from IDCS will be FROM an address ending with oracle.com. Note: If your organization manages their own IDCS stripe this email address can be changed.
All emails will also have a valid DKIM record and SPF record attached to them.
Ask your email service provider or IT department to allow or bypass filtering for any email that matches the following criteria:
Further information about DKIM records can be found at: https://help.dyn.com/articles/dkim/
Further information about SPF records can be found at: https://help.dyn.com/articles/spf/
Your email server may temporarily block or delay incoming emails from Aconex if there are a large number of emails arriving at the same time. This is called throttling.
In this case, please ask your email service provider or IT department to disable throttling for emails received from an email address ending with @aconex.com, @us.aconex.com, @au.aconex.com, @eu.aconex.com, @me.aconex.com.
We recommend email services and spam filters are configured to allow incoming emails based on server names, and not IP addresses.
Our email servers use the following naming patterns, which can be used for filtering/throttling:
We are not able to guarantee which IP addresses are used to send email notifications, as these can change at any time.
Your email service provider or IT department can get the latest list of our email server internet addresses by checking our SPF records, which are:
Please use URL based rules if required for your firewall/allowlists. See the links for each Aconex instance
Your email service must have valid SPF and DKIM records otherwise if you reply to an Aconex email notification (or send an email to an @oracle or @aconex address) it may not be received.
Your organization does not have to implement DMARC but ensure you have valid SPF and DKIM records, to be compliant with our DMARC policy.
If you are still not receiving email notifications from Aconex after following the above steps, please see our troubleshooting guide.
