Mail Domain and Firewall Configuration

Account administrators need to take the following steps to ensure that emails sent from SuiteProjects Pro are delivered successfully and to allow communication between SuiteProjects Pro and add-on service applications.

• Create a Sender Policy Framework (SPF) record to provide a list of servers that are authorized to send mail on behalf of your domain and include emails sent from SuiteProjects Pro - SPF is a Simple Mail Transfer Protocol (SMTP) validation system that verifies the host names or IP addresses emails can originate from for a domain name. An SPF record is a TXT record using the SPF format with your DNS provider. An SMTP server on the receiving end determines (based on the content of the DNS TXT record) whether the nameserver / IP address the email message is sent from is approved for that domain. Setting up a DNS TXT record for SPF might be required by the email infrastructure or services (as presented by email domains) that you send email to. For more information, see Sender Policy Framework (SPF) Record.

  Note:

  SuiteProjects Pro email does not comply with DMARC alignment rules by default. Additional action may be required to ensure that SuiteProjects Pro email pass either DKIM or SPF checks if you use DMARC for email authentication. Depending on your DMARC policy, SuiteProjects Pro email may be marked as junk mail or not be delivered at all if both DKIM and SPF sets of checks fail. For more information, see DMARC Alignment and SuiteProjects Pro Email.

• Allow the relevant SuiteProjects Pro domains in the firewall settings of the servers and machines running add-on services or accepting communication with SuiteProjects Pro. For example, this may be needed to allow SuiteProjects Pro Automatic Backup Service files to be transferred to your SCP/SFTP server, or to allow the secure transfer of data between your SuiteProjects Pro account and the SuiteProjects Pro Integration Manager application.

If your organization uses firewall, proxy, or security appliance rules for SuiteProjects Pro, configure those rules by domain name. Do not configure access by using SuiteProjects Pro IP addresses.

Ensure the following domains are allowed:

• netsuitesuiteprojectspro.com

• openair.com

• outbound1.netsuitesuiteprojectspro.com

• outbound1.openair.com

• outbound2.netsuitesuiteprojectspro.com

• outbound2.openair.com

• relay.openair.com

• system.openair.com

• Your account-specific domains with the netsuitesuiteprojectspro.com and openair.com domain names.

  • <company-id>.app.netsuitesuiteprojectspro.com

  • <company-id>.app.openair.com

  Where <company-id> is a unique account identifier that is typically based on the Company ID for your account. For more information about your account-specific domain and URLs for SuiteProjects Pro services, see Your Account URLs.

Important:

OpenAir is now SuiteProjects Pro. As of February 15, 2025, service URLs with the netsuitesuiteprojectspro.com domain name replace URLs with the openair.com domain name for all accounts.

To ensure a seamless transition, you should update any domain allowlist to include the domains netsuitesuiteprojectspro.com, outbound1.netsuitesuiteprojectspro.com, outbound2.netsuitesuiteprojectspro.com and your new account-specific domain <company-id>.app.netsuitesuiteprojectspro.com, among other actions.

The existing outbound and relay domains outbound1.openair.com, outbound2.openair.com and relay.openair.com are not changing and should still be included in any domain allowlist. Outbound domains with the openair.com domain name may be removed at a future date.

The use of SuiteProjects Pro IP addresses to access or manage access to SuiteProjects Pro services is not supported. You should allow the SuiteProjects Pro domains listed in this topic instead of IP addresses. IP addresses for SuiteProjects Pro services may change at any time without notice, including when SuiteProjects Pro traffic is routed through updated delivery and security infrastructure.