App Suite Cloud

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

OX Cloud creates private and public key pairs, enables DKIM signing, and then configures the OX Cloud default policy for the whole of your tenant.


Anchor

...

Per-domain
Per-domain
Per-domain (currently just one key per brand)

DKIM signing and the used mode can only be enabled for a whole brand. OX will prepare two keys (for easier rollover) a key and hand over the public key to the customer to allow domain owners to set the required DNS records.

An easier approach is to point to our CNAMEs within the respective DNS zones for the maildomain:

Example:

mail1._domainkey CNAME mail1._domainkey.cloudeu.xion.oxcs.net.
mail2._domainkey CNAME mail2._domainkey.cloudeu.xion.oxcs.net.

This variant allows for aligned DKIM validation and therefore also supports DMARC policy validation but at the same time every single domain being provisioned better has to have the DKIM DNS records set. This needs to be handled by the Cloud service provider or delegated to the domain owner. DKIM signatures w/o a matching DNS records are not expected and it's unclear how those are treated from receivers. They might even fail validation or getting a negative score because of that. Given the type of business you as service provider are running this might still be a valid scenario.

...

  • One keypair for the whole brand
  • the signing domain is always set to the mail sender domain → supports DMARC as signing domain and mail from domain match
  • ALL domains managed within the brand SHOULD have DKIM DNS configured correctly. To be managed by respective domain owner.
    DNS entries required look like:
    mail1._domainkey CNAME mail1._domainkey.cloudeu.xion.oxcs.net.
    mail2._domainkey CNAME mail2._domainkey.cloudeu.xion.oxcs.net.
    Especially those entries point directly to the correct public keys and all those records will look the same for all domains.


Anchor

...

Per-brand
Per-brand
Per-brand

OX by default uses DKIM keypairs with its own domains. OX Cloud uses a default signing configuration for domains that do not have a policy in place.

...

  • One keypair for the whole brand
  • signing key and signing domain are generic and managed by OX
  • NO customer domain DNS modifications/maintenance required
  • does NOT support DMARC as signing domain and mail from domain do not match
  • Microsoft 365 also implements this as default
  • Mailbox service providers are getting more strict to accept non-aligned DKIM signatures while the RFCs do not enforce it