Support resources

Postmaster information page

OX Cloud EU and India and India platforms (standard AVAS)

https://postmaster-oxseu.vadesecure.com/

OX Cloud US platforms (standard AVAS)

https://postmaster-oxsus.vadesecure.com/

Set up domain records for OX Cloud

OX Cloud is available as a whitelabel solution where all public endpoints appear under the partner's brand. This table lists the different entrypoints.

The hostnames listed here are examples. The specific ones managed by OX will be communicated as part of the onboarding process. The partner names are already required to be given by the partner during the onboarding request together with matching certificates (wildcard preferred).

The DNS records are supposed to be CNAME records pointing to the A records on the right side of the table.

"partner" in the table is always a placeholder. Your own domain and for the oxcs.net entries it is an identifier you will get during the onboarding phase from us.

"partner" in the table is always a placeholder. Your own domain and for the oxcs.net entries it is an identifier you will get during the onboarding phase from us.

Set up MX records for OX Cloud

These MX records are to be used for mail domains which are accessed under the whitelabel domain either in EU or in US.

Please note: In case you will be using custom endpoints with your own domain you will get a different set of MX records during onboarding compared to the example below. The SPF records typically stay identical though unless stated otherwise. MX records must NOT be CNAME

Service discovery records for DAV (optional) (to be set up in mail domains)

_caldavs._tcp.MYDOMAIN.TLD.

_carddavs._tcp.MYDOMAIN.TLD.

Configure SPF for OX Cloud

SPF records are in the responsibility of the domain owner. OX provides records which can be included in the own policy and include the IP address ranges which are used for sending mail.

How to include those is outlined below. Those are valid for the primary Cloud platforms. In case of doubt please align with an OX representative if those are the right ones to use.

OX Cloud EU

OX Cloud US

TLS certificates

To set up your service on OX Cloud we need certificates for your custom hostnames. Currently we support two options as described below. One of both options can be selected during onboarding.

Upload certificate and key

This option requires you to provide your own certificate and matching private key for the custom hostnames listed above.

• The certificate must cover all endpoints listed in the table above (Web UI, guest sharing, DAV, IMAP, POP3, SMTP) — either as individual SAN entries or, preferably, as a single wildcard certificate (e.g. *.partner.com).
• Key algorithm: RSA, 2048-bit minimum, for broad client compatibility (browsers, mail clients).
• Certificate and private key need to be provided together during onboarding; renewals must be delivered before the current certificate expires, as OX does not manage renewal for this option.

LetsEncrypt

Right now this can be supported if all endpoints (see above) can be covered by one single wildcard certificate.

To obtain a wildcard certificate from LetsEncrypt it is required to perform a DNS challenge which at the same time means that we need a hook into the used TLD DNS zone by a CNAME like the following:

_acme-challenge.partner.com. CNAME _acme-challenge.partner.xion.oxcs.net.